feat: add requirements traceability to roadmap and plan-phase
- Roadmap template now includes Requirements: field for each phase - plan-phase loads REQUIREMENTS.md and extracts phase-specific requirements - define-requirements shows full list inline before commit (not just counts)
This commit is contained in:
@@ -39,6 +39,20 @@ Phase number: $ARGUMENTS (optional - auto-detects next unplanned phase if not pr
|
||||
**Load roadmap:**
|
||||
@.planning/ROADMAP.md
|
||||
|
||||
**Load requirements:**
|
||||
@.planning/REQUIREMENTS.md
|
||||
|
||||
After loading, extract the requirements for the current phase:
|
||||
1. Find the phase in ROADMAP.md, get its `Requirements:` list (e.g., "PROF-01, PROF-02, PROF-03")
|
||||
2. Look up each REQ-ID in REQUIREMENTS.md to get the full description
|
||||
3. Present the requirements this phase must satisfy:
|
||||
```
|
||||
Phase [N] Requirements:
|
||||
- PROF-01: User can create profile with display name
|
||||
- PROF-02: User can upload avatar image
|
||||
- PROF-03: User can write bio (max 500 chars)
|
||||
```
|
||||
|
||||
**Load phase context if exists (created by /gsd:discuss-phase):**
|
||||
Check for and read `.planning/phases/XX-name/{phase}-CONTEXT.md` - contains research findings, clarifications, and decisions from phase discussion.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user