mindforge-new-milestone
The mindforge-new-milestone skill initiates a new development cycle for an existing MindForge project by updating PROJECT.md with milestone goals, optionally conducting domain research for new features, and generating scoped requirements and phase roadmaps. Use this when starting a subsequent project milestone after completing previous phases, as it builds on existing project history rather than creating a new project from scratch.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-new-milestone && cp -r /tmp/mindforge-new-milestone/.agent/skills/mindforge-new-milestone ~/.claude/skills/mindforge-new-milestoneSKILL.md
<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:** `/mindforge-plan-phase [N]` to start execution. </objective> <execution_context> @.agent/workflows/mindforge-new-milestone.md @.agent/references/questioning.md @.agent/references/ui-brand.md @.agent/templates/project.md @.agent/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 @.agent/workflows/mindforge-new-milestone.md end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits). </process>
Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase