refactor: unify milestone flow, remove deprecated commands

Consolidate /gsd:new-milestone to mirror /gsd:new-project:
- questioning → research (optional) → requirements → roadmap

BREAKING CHANGES:
- Remove /gsd:discuss-milestone (consolidated into new-milestone)
- Remove /gsd:create-roadmap (integrated into project/milestone flows)
- Remove /gsd:define-requirements (integrated into project/milestone flows)
- Remove /gsd:research-project (integrated into project/milestone flows)

Deleted files:
- commands/gsd/{discuss-milestone,create-roadmap,define-requirements,research-project}.md
- get-shit-done/workflows/{discuss-milestone,create-roadmap,define-requirements}.md
- get-shit-done/templates/milestone-context.md

Updated references in:
- progress.md, complete-milestone.md, help.md
- complete-milestone workflow, continuation-format.md
- questioning.md, requirements.md template, SUMMARY.md template
- gsd-project-researcher.md, gsd-roadmapper.md
- README.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2026-01-17 00:28:41 -06:00
parent 54f2d5600b
commit c54071ccb8
21 changed files with 736 additions and 2199 deletions

View File

@@ -167,18 +167,12 @@ All 4 phases shipped
## ▶ Next Up
**Plan v1.1** — Enhanced features and optimizations
**Start v1.1** — questioning → research → requirements → roadmap
`/gsd:discuss-milestone`
`/gsd:new-milestone`
<sub>`/clear` first → fresh context window</sub>
---
**Also available:**
- `/gsd:new-milestone` — create directly if scope is clear
- Review accomplishments before moving on
---
```

View File

@@ -16,8 +16,9 @@ Don't interrogate. Collaborate. Don't follow a script. Follow the thread.
By the end of questioning, you need enough clarity to write a PROJECT.md that downstream phases can act on:
- **research-project** needs: what domain to research, what the user already knows, what unknowns exist
- **create-roadmap** needs: clear enough vision to decompose into phases, what "done" looks like
- **Research** needs: what domain to research, what the user already knows, what unknowns exist
- **Requirements** needs: clear enough vision to scope v1 features
- **Roadmap** needs: clear enough vision to decompose into phases, what "done" looks like
- **plan-phase** needs: specific requirements to break into tasks, context for implementation choices
- **execute-phase** needs: success criteria to verify against, the "why" behind requirements