Name: gsd-new-milestone
Author: Zeustakeshi

Prompt file imported from Zeustakeshi/multi_agent_engnieer (.claude/commands/gsd-new-milestone.md). Fill in {{arguments}} before use. Copyright stays with the author.

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> @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/workflows/new-milestone.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/questioning.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/ui-brand.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/templates/project.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/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.

<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> @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/workflows/new-milestone.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/questioning.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/ui-brand.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/templates/project.md @/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/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 end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits). </process>

Install gsd-new-milestone and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "<objective>\nStart a new milestone: questioning → research (optional) → requirements → roadmap.\n\nBrownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers \"what's next\", updates PROJECT.md, then runs requirements → roadmap cycle.\n\n**Creates/Updates:**\n- `.planning/PROJECT.md` — updated with new milestone goals\n- `.planning/research/` — domain research (optional, NEW features only)\n- `.planning/REQUIREMENTS.md` — scoped requirements for this milestone\n- `.planning/ROADMAP.md` — phase structure (continues numbering)\n- `.planning/STATE.md` — reset for new milestone\n\n**After:** `/gsd-plan-phase [N]` to start execution.\n</objective>\n\n<execution_context>\n@/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/workflows/new-milestone.md\n@/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/questioning.md\n@/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/references/ui-brand.md\n@/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/templates/project.md\n@/home/minhhieuano/2222/workspace/multi_agent_web_seo/.claude/gsd-core/templates/requirements.md\n</execution_context>\n\n<context>\nMilestone name: {{arguments}} (optional - will prompt if not provided)\n\nProject and milestone context files are resolved inside the workflow (`init new-milestone`) and delegated via `<files_to_read>` blocks where subagents are used.\n</context>\n\n<process>\nExecute end-to-end.\nPreserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).\n</process>", "variables": [ "arguments" ], "notes": "Start a new milestone cycle — update PROJECT.md and route to requirements Tools: Read, Write, Bash, Agent, AskUserQuestion. Arguments: [milestone name, e.g., 'v1.1 Notifications'] [--ws <name>].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/Zeustakeshi/multi_agent_engnieer", "path": ".claude/commands/gsd-new-milestone.md", "ref": "34d0c2cca8e77e01b37f47cc66e88a6463b98b26", "url": "https://github.com/Zeustakeshi/multi_agent_engnieer/blob/34d0c2cca8e77e01b37f47cc66e88a6463b98b26/.claude/commands/gsd-new-milestone.md", "key": "Zeustakeshi/multi_agent_engnieer/.claude/commands/gsd-new-milestone.md" } } }

gsd-new-milestone

About

Use it

Install gsd-new-milestone and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews