Gsd new milestone
Skill coco-research/coco/systems/gsd/skills/gsd-new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirementsFrom its SKILL.md
npx -y skills add coco-research/coco --skill gsd-new-milestoneAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.7 KB, 344 tokens by cl100k_base, as published. Nobody here has run it
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/.claude/get-shit-done/workflows/new-milestone.md @$HOME/.claude/get-shit-done/references/questioning.md @$HOME/.claude/get-shit-done/references/ui-brand.md @$HOME/.claude/get-shit-done/templates/project.md @$HOME/.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>
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.