/create-roadmap

Create project roadmap with phase breakdown.

Roadmaps define what work happens in what order. Run after /gsd:new-project.

<execution_context> @/.claude/get-shit-done/workflows/create-roadmap.md @/.claude/get-shit-done/templates/roadmap.md @~/.claude/get-shit-done/templates/state.md </execution_context>

@.planning/PROJECT.md @.planning/config.json ```bash # Verify project exists [ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; } ``` Check if roadmap already exists:

[ -f .planning/ROADMAP.md ] && echo "ROADMAP_EXISTS" || echo "NO_ROADMAP"

If ROADMAP_EXISTS: Use AskUserQuestion:

• header: "Roadmap exists"
• question: "A roadmap already exists. What would you like to do?"
• options:
  • "View existing" - Show current roadmap
  • "Replace" - Create new roadmap (will overwrite)
  • "Cancel" - Keep existing roadmap

If "View existing": cat .planning/ROADMAP.md and exit If "Cancel": Exit If "Replace": Continue with workflow

Follow the create-roadmap.md workflow starting from detect_domain step.

The workflow handles:

• Domain expertise detection
• Phase identification
• Research flags for each phase
• Confirmation gates (respecting config mode)
• ROADMAP.md creation
• STATE.md initialization
• Phase directory creation
• Git commit

``` Roadmap created: - Roadmap: .planning/ROADMAP.md - State: .planning/STATE.md - [N] phases defined

---

▶ Next Up

Phase 1: [Name] — [Goal from ROADMAP.md]

/gsd:plan-phase 1

<sub>/clear first → fresh context window</sub>

---

Also available:

• /gsd:discuss-phase 1 — gather context first
• /gsd:research-phase 1 — investigate unknowns
• Review roadmap

---

</step>

</process>

<output>
- `.planning/ROADMAP.md`
- `.planning/STATE.md`
- `.planning/phases/XX-name/` directories
</output>

<success_criteria>
- [ ] PROJECT.md validated
- [ ] ROADMAP.md created with phases
- [ ] STATE.md initialized
- [ ] Phase directories created
- [ ] Changes committed
</success_criteria>