virtual-team

Claude Code Virtual Team

A Claude Code plugin that turns Claude Code into a virtual development team. It provides a deliberate pipeline from idea to shipped code — with agents, commands, and skills that enforce TDD, contract-first development, and quality gates at every step.

Getting Started

1. Install the plugin

In a Claude Code session, run:

/plugin marketplace add ovargas/virtual-team
/plugin install virtual-team@virtual-team-marketplace

2. Initialize your project

Start a Claude Code session and run:

/virtual-team:start

This walks you through an interactive interview to define your tech stack, project structure, and conventions. It creates stack.md (the source of truth for your project) and sets up the docs/ directory structure.

Anything you haven't decided yet gets marked as TBD — the architect agent will catch it later when a feature actually needs it.

Working on multiple repositories? You can create a hub repo to coordinate across services — shared decisions, epics, and API contracts in one place. Run /virtual-team:start --hub in a new repo to set it up. See the command reference for details.

3. Start building

You only need 5 commands for daily work:

Command	What it does
/virtual-team:status	Start your day — shows what's in progress, what's next
/virtual-team:flow <description>	Build a feature end-to-end (spec → plan → code → review → PR)
/virtual-team:flow --fix <description>	Fix a bug end-to-end (report → investigate → fix → review → PR)
/virtual-team:commit	Create a clean, atomic commit
/virtual-team:handoff	End a session — captures state for the next one

That's it. Everything else is optional.

Working with an existing codebase?

If your project has been around for years and you're adopting this plugin retroactively, the workflow is the same — but you'll spend the first few sessions documenting what already exists rather than deciding fresh. Nothing in your code changes during onboarding. The plugin only adds documentation (stack.md, docs/) alongside your existing code.

Run this sequence the first time you open the repo:

#	Command	Why
1	/virtual-team:start	Generates stack.md from what already exists. It reads go.mod / package.json / pyproject.toml / etc. and pre-fills the interview — you confirm what's there instead of deciding from scratch. Anything genuinely inconsistent across the codebase gets marked TBD and resolved later when a feature touches it.
2	/virtual-team:doctor	Audits stack.md against available skills. Surfaces which technologies in your stack have no coding-convention skill yet — so you know where the LLM will be working without guardrails. Read-only, never blocks. (Runs once automatically at the end of /start; re-run after editing stack.md.)
3	/virtual-team:tech-review	Baseline health reading — architecture drift, technical debt, dependency health, test coverage and security gaps. Output goes to docs/reviews/ and becomes your first backlog candidates. Skip if you don't need an audit.
4	/virtual-team:docs	Captures the tribal knowledge — setup guide, deploy guide, config reference — that's lived in people's heads. Years-old projects rarely have current docs.
5	/virtual-team:flow <new feature>	Resume normal workflow. From here, every new feature uses the full pipeline; old code stays as-is until you touch it.

A few tips specific to legacy code:

• Don't retrofit conventions everywhere. The plugin grows consistency at the edges where work happens. Trying to make the entire codebase match stack.md before any feature work is a death march.
• Set tdd: recommended, not strict. Legacy code often can't be test-driven without large refactors. recommended mode (in stack.md Workflow section) lets the TDD skill adapt instead of blocking.
• Capture decisions just-in-time. When you hit a "why on earth did we do X" moment during feature work, write an ADR in docs/decisions/ then. Don't backfill every historical decision upfront — only record ones that are hard to reverse, surprising without context, AND a real trade-off.

Daily Workflow

Start your day

/virtual-team:status

Shows what's in progress, what's blocked, and suggests the right command to run next.

Build a feature

/virtual-team:flow Add password reset via email

This runs the full pipeline in one session:

/feature → /contracts → /plan → /implement → /review + /validate → /pr

Interactive gates between each step resolve decisions and TBDs without leaving the session. If the session is interrupted, just run /virtual-team:flow again — it auto-detects where you left off.

Fix a bug

/virtual-team:flow --fix "users can't log in after password reset"