Source: commands/dk-design.md · Lifecycle Stage: DESIGN
Produces technical and visual design including data models, API contracts, user flows, and design direction.
- A feature specification has been approved.
- Architecture or interface decisions need to be made explicit before implementation.
- No specification exists — use
/dk-specfirst. - The task is trivially simple with no design decisions.
- An approved feature specification exists.
- Repository Orientation:
repository-scout-agentinspects existing architecture and patterns. - Technical Design:
solution-architect-agentproduces implementation-oriented design usingtechnical-design.md. - Data Model: If persistent data changes are required,
data-model-designproduces schemas and migrations. - API Contracts: If APIs or module boundaries are changing,
api-contract-designdefines stable interfaces. - User Flow: For UI tasks,
user-flow-designmaps user journeys including edge cases. - Design Direction: For UI tasks,
design-directiondefines visual language and aesthetic choices.
| Skill | Role |
|---|---|
technical-design |
Primary — implementation-oriented design document |
data-model-design |
Conditional — only if persistent data changes required |
api-contract-design |
Conditional — only if APIs/module boundaries changing |
user-flow-design |
Conditional — only for UI/UX tasks |
design-direction |
Conditional — only for visual UI tasks |
solution-architect-agent(primary)repository-scout-agent(supporting)
- Technical design document
- Data model / schema (conditional)
- API contract (conditional)
- User flow diagram (conditional)
- Design direction document (conditional)
- Design is approved by the user before
/dk-tasksbegins. - All architecture decisions are documented.
/dk-spec— previous step/dk-tasks— next step after approval