* fix(claude): restore namespaced /gsd:<command> references * test(claude): align slash-command expectations to /gsd: form * test(claude): align generated command references to /gsd: * test(claude): finish /gsd: namespace expectation updates
1.6 KiB
1.6 KiB
name, description, argument-hint, allowed-tools
| name | description | argument-hint | allowed-tools | |||||
|---|---|---|---|---|---|---|---|---|
| gsd:new-milestone | Start a new milestone cycle — update PROJECT.md and route to requirements | [milestone name, e.g., 'v1.1 Notifications'] |
|
Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.
Creates/Updates:
.planning/PROJECT.md— updated with new milestone goals.planning/research/— domain research (optional, NEW features only).planning/REQUIREMENTS.md— scoped requirements for this milestone.planning/ROADMAP.md— phase structure (continues numbering).planning/STATE.md— reset for new milestone
After: /gsd:plan-phase [N] to start execution.
<execution_context>
@/.claude/get-shit-done/workflows/new-milestone.md
@/.claude/get-shit-done/references/questioning.md
@/.claude/get-shit-done/references/ui-brand.md
@/.claude/get-shit-done/templates/project.md
@~/.claude/get-shit-done/templates/requirements.md
</execution_context>
Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used.