fix: offer both define-requirements and create-roadmap as next steps

Requirements definition is recommended but not mandatory after research.
This commit is contained in:
Lex Christopherson
2026-01-14 23:53:41 -06:00
parent 9e092cd402
commit 1ccc66f16b
2 changed files with 18 additions and 4 deletions

View File

@@ -96,13 +96,19 @@ Research complete:
## ▶ Next Up
**Define requirements** — scope your v1 from research findings
Choose your path:
**Option A: Define requirements first** (recommended)
Scope your v1 from research findings. Transforms "what exists" into "what we're building" with checkable requirements.
`/gsd:define-requirements`
<sub>`/clear` first → fresh context window</sub>
**Option B: Create roadmap directly**
Skip requirements if scope is already clear from research.
**Flow:** research-project → **define-requirements** → create-roadmap
`/gsd:create-roadmap`
<sub>`/clear` first → fresh context window</sub>
---
```

View File

@@ -350,7 +350,15 @@ Research complete:
## ▶ Next Up
**Create roadmap** — using research findings
Choose your path:
**Option A: Define requirements first** (recommended)
Scope your v1 from research findings. Transforms "what exists" into "what we're building" with checkable requirements.
`/gsd:define-requirements`
**Option B: Create roadmap directly**
Skip requirements if scope is already clear from research.
`/gsd:create-roadmap`