feature-design¶
Generates technical design specifications from requirements.
Synopsis¶
Description¶
The feature-design command transforms requirements into a technical design specification. It analyzes your requirements document, considers your codebase architecture (via KB), and produces detailed design documentation with architecture diagrams.
Parameters¶
| Parameter | Position | Required | Default | Description |
|---|---|---|---|---|
FEATURE_ID |
$1 |
Yes | - | Feature identifier |
EXTRA_CONTEXT |
$2 |
No | "" |
Additional design context |
Prerequisites¶
requirements.mdmust exist in.rp1/work/features/<feature-id>/- Knowledge base recommended for context-aware design
Output¶
| File | Contents |
|---|---|
design.md |
Technical design specification |
design-decisions.md |
Rationale for key decisions |
Location: .rp1/work/features/<feature-id>/
Design Document Sections¶
- Architecture overview with diagrams
- Component design
- Data models
- API specifications
- Integration points
- Technology choices with rationale
- Testing strategy
Examples¶
Basic Usage¶
With Additional Context¶
Related Commands¶
feature-requirements- Previous stepvalidate-hypothesis- Optional: test assumptionsfeature-tasks- Next step: task breakdown
See Also¶
- Knowledge-Aware Agents - How design respects your architecture