| name | planning-design |
| description | Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints. |
| allowed-tools | Read, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion |
| graph | {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]} |
- When evaluating technology stack options for a feature
- When designing system architecture for new components
- When assessing implementation risks and defining mitigations
Key Principle
Architecture decisions must be traceable to specification requirements. Technology choices must comply with constitution constraints. Trade-offs must be documented for every significant decision.
Process
- Assess technology stack - Evaluate options against constitution requirements
- Design architecture - Components, interfaces, data model, integration points
- Define strategy - Phases, milestones, testing strategy, deployment approach
- Assess risks - Identify risks and define mitigations
- Human review - Approve architecture and strategy before task breakdown
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-planning
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator
