A reusable, documentation-first development organization for Claude Code, packaged as a plugin. Seven specialized agents move feature work from requirements to reviewed code:
Product Owner → product-manager → designer (UI features only) → principal-engineer → task-planner → senior-developer → reviewer → Owner approval, coordinated by an orchestrator.
Owner attention is reserved for what matters — approving PRDs, releases, and major decisions (new dependencies, stack/data-model changes, security-sensitive or irreversible choices). All other gates are delegated: design specs → product-manager, plans → principal-engineer self-certified, task plans proceed directly; the product-manager answers requirement questions as the Owner's proxy.
Small work skips the pipeline entirely (fast path): bugs and chores go straight to the senior-developer (fix + tests + a record in docs/fixes/), doc corrections to the role owning the doc — no gates, as long as the work is truth-preserving.
Agents spawn only to produce or change artifacts. Questions, discussion, routing, and status updates run as the matching role skill directly in the main conversation — interactive and a fraction of a subagent spawn's token cost.
/plugin marketplace add J-T-McC/dev-team # private repo: SSH auth is used automatically
/plugin install dev-team@dev-team
Then scaffold the project workspace (creates docs/, seeds standards/stack, project CLAUDE.md section):
run the dev-team:bootstrap skill
Fill in docs/stack/stack.md and customize docs/standards/*.md — agents stop and ask rather than guess while placeholders remain. Commit the scaffolded files to your project repo. Nothing from your project ever flows back into this repo.
Keep the project CLAUDE.md lean — it is loaded every session, while skills and docs/ load on demand. See CLAUDE.md.example for the recommended minimal shape.
Project-level skills (.claude/skills/) work out of the box: every dev-team agent carries the Skill tool and is instructed to consult relevant domain skills (e.g. a laravel skill) before deciding or implementing — no plugin changes needed.
/plugin marketplace update dev-team # refresh marketplace metadata from GitHub
/plugin update dev-team@dev-team # then update the plugin itself
Every commit to this repo is a new version (no version pinning). Seeded files (docs/standards/, docs/stack/, CLAUDE.md section) are project-owned and are not touched by updates — use the sync command below to catch up.
/dev-team:sync
Plugin updates never touch project-owned files, so a project bootstrapped before a seed was added (or extended) silently lacks it — and agents have no fallback to the plugin's copies. Run sync after updating; it is safe to run any time:
- Copies any seed file the project is missing (standards,
docs/stack/stack.md,docs/status.md) and creates any missingdocs/directories - Reports drift in existing standards: lists seed sections (
##headings) absent from your project's copy, ignoring your customizations - Appends only what you approve — never overwrites, rewrites, or deletes project content
After a sync, fill placeholders in newly copied files and commit them to your project repo.
/plugin marketplace add /path/to/dev-team # local checkout as a second marketplace
# after edits:
/plugin marketplace update dev-team
/reload-plugins
Validate with claude plugin validate .
| Path | What | Updatable |
|---|---|---|
agents/, skills/ |
The seven roles + bootstrap skill | ✅ via plugin update |
commands/ |
/dev-team:sync — pull missing/updated seeds into a project |
✅ via plugin update |
templates/, workflow/ |
Document templates, pipeline/handoff/communication rules | ✅ via plugin update |
hooks/ |
Session-start announcement + agent-memory size sentinel | ✅ via plugin update |
seeds/ |
Copied into projects by bootstrap/sync | ❌ project-owned after copy |
examples/user-authentication/ |
Worked example of the full pipeline | ✅ via plugin update |