Commands are now installed as commands/gsd/<name>.md and invoked as /gsd:<name> in Claude Code. The old hyphen form /gsd-<name> was still hardcoded in hundreds of places across workflows, references, templates, lib modules, and command files — causing "Unknown command" errors whenever GSD suggested a command to the user. Replace all /gsd-<cmd> occurrences where <cmd> is a known command name (derived at runtime from commands/gsd/*.md) using a targeted Node.js script. Agent names, tool names (gsd-sdk, gsd-tools), directory names, and path fragments are not touched. Adds regression test tests/bug-2543-gsd-slash-namespace.test.cjs that enforces zero legacy occurrences going forward. Removes inverted tests/stale-colon-refs.test.cjs (bug #1748) which enforced the now-obsolete hyphen form; the new bug-2543 test supersedes it. Updates 5 assertion tests that hardcoded the old hyphen form to accept the new colon form. Closes #2543 Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
45 lines
1.7 KiB
Markdown
45 lines
1.7 KiB
Markdown
---
|
|
name: gsd:new-milestone
|
|
description: Start a new milestone cycle — update PROJECT.md and route to requirements
|
|
argument-hint: "[milestone name, e.g., 'v1.1 Notifications']"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Task
|
|
- AskUserQuestion
|
|
---
|
|
<objective>
|
|
Start a new milestone: questioning → research (optional) → requirements → roadmap.
|
|
|
|
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.
|
|
</objective>
|
|
|
|
<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>
|
|
|
|
<context>
|
|
Milestone name: $ARGUMENTS (optional - will prompt if not provided)
|
|
|
|
Project and milestone context files are resolved inside the workflow (`init new-milestone`) and delegated via `<files_to_read>` blocks where subagents are used.
|
|
</context>
|
|
|
|
<process>
|
|
Execute the new-milestone workflow from @~/.claude/get-shit-done/workflows/new-milestone.md end-to-end.
|
|
Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
|
|
</process>
|