| name | ferrox-new-milestone |
| description | This project is done with its current goal and you want to start the next one |
| argument-hint | [milestone name, e.g., 'v1.1 Notifications'] |
| allowed-tools | ["Read","Write","Bash","Agent","AskUserQuestion"] |
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: /ferrox-plan-phase [N] to start execution.
<execution_context>
@/.claude/ferrox-core/workflows/new-milestone.md
@/.claude/ferrox-core/references/questioning.md
@/.claude/ferrox-core/references/ui-brand.md
@/.claude/ferrox-core/templates/project.md
@~/.claude/ferrox-core/templates/requirements.md
</execution_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.
Execute end-to-end.
Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
