Cds new milestone
Skill Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/cds-new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirementsFrom its SKILL.md
npx -y skills add Enakoneschniy/claude-dev-stack --skill cds-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
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
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: /cds-plan-phase [N] to start execution.
</objective>
<execution_context> @$HOME/.claude/cds-workflow/workflows/new-milestone.md @$HOME/.claude/cds-workflow/references/questioning.md @$HOME/.claude/cds-workflow/references/ui-brand.md @$HOME/.claude/cds-workflow/templates/project.md @$HOME/.claude/cds-workflow/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.