| name | team-blueprints |
| description | Use when the user wants a pre-designed agent team configuration for a specific development phase. Triggers: "research team", "feature development team", "code review team", "debug team", "design team", "planning team", "roadmap team", "productivity team", "brainstorming team", "team blueprint", "team template", "spawn a team for [development phase]".
Provides 8 ready-to-use team blueprints across the application development lifecycle. Routes to the unified spawn commands (`/spawn-build`, `/spawn-think`, `/spawn-create`).
|
| version | 0.26.0 |
Agent Team Blueprints
Pre-designed team configurations for eight application development phases. Each blueprint defines team composition, teammate roles, task structure, and the unified command that spawns it.
Blueprints
| # | Blueprint | Command | Best For | Team Size |
|---|
| 1 | Research & Discovery | /spawn-think --mode research | Evaluating tech, landscape surveys, risk assessment | 3-5 |
| 2 | Feature Development | /spawn-build --mode feature | Multi-layer features (UI+API+DB) | 3-5 |
| 3 | Code Review & QA | /spawn-think --mode review | PR review, quality audit | 3-5 |
| 4 | Debugging | /spawn-build --mode debug | Hard bugs, production incidents | 3 |
| 5 | Frontend Design | /spawn-create --mode design | UI features needing design process | 4 |
| 6 | Adaptive Planning | /spawn-think --mode planning | Roadmaps, specs, ADRs, migrations, business cases, GTM, OKRs | 3-4 |
| 7 | Productivity Systems | /spawn-create --mode productivity | Workflow optimization (full 5-persona loop) | 5 |
| 8 | Brainstorming | /spawn-create --mode brainstorm | Creative ideation (tech, product, process, ops categories) | 3-5 |
For full team compositions, task structures, modes, and mechanisms, see references/blueprint-definitions.md.
Choosing the Right Blueprint
Is the task about understanding something? → Research & Discovery (3 modes)
Is the task about building something new? → Feature Development
Is the task about reviewing existing work? → Code Review & QA (3 modes)
Is the task about fixing something broken? → Debugging & Investigation
Is the task about designing a user interface? → Frontend Design (3 modes)
Is the task about sequencing what to build? → Planning & Roadmapping (7 modes)
Is the task about optimizing workflows? → Productivity Systems
Is the task about generating creative ideas? → Brainstorming & Ideation
Is it a mix? → Use team-architect agent for custom design
Pipeline Composition
When a task spans multiple phases, chain blueprints together (or wrap them in a /project pipeline for shared accumulating context):
Need to explore before building? → Research → Feature Dev
Need to plan before building? → Planning → Feature Dev
Need design before implementation? → Design → Feature Dev → Review
Need ideas before planning? → Brainstorming → Planning → Feature Dev
Found bugs during review? → Review → Debug → Feature Dev (fix)
Need to optimize an existing flow? → Productivity → Feature Dev (automation)
Full product cycle? → Business Case → Roadmap → Spec → Feature Dev → Review
Design Patterns
Five reusable patterns across all blueprints:
- Adaptive Mode — Single command supports multiple operational modes
- Cross-Team Pipeline — Chain teams for multi-phase workflows
- Discovery Interview — Rich shared context via structured intake (universal core in
shared/discovery-interview.md; mode-specific in shared/discovery-modes/<mode>.md)
- User Feedback Gate — Mid-course correction checkpoints
- Artifact Output — Persistent deliverables to
docs/teams/[team-name]/ (or docs/projects/<name>/<stage>/ when using project pipelines)
For pattern details and customization guidance, see references/design-patterns.md.
Reference Files
