forge-new-milestone

Plan the next milestone from ROADMAP.md and generate PLAN.md with tasks XML files.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/whatwecando/dagsmith --skill forge-new-milestone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-new-milestone
Source: https://github.com/whatwecando/dagsmith/tree/main/templates/skills/forge-new-milestone
Command: npx skills add https://github.com/whatwecando/dagsmith --skill forge-new-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start the next milestone after the current one is archived. Re-plans tasks without re-generating .claude/ files.

Core Features & Use Cases

  • Reads ROADMAP.md to identify the next milestone and validates prerequisites
  • Creates a concrete PLAN.md and per-milestone tasks/*.xml for execution
  • Updates architecture artifacts (ARCHITECTURE.md, DECISIONS.md, and rules) when scope changes
  • Verifies the plan with semantic checks and requires user confirmation before writing
  • Finalizes planning files and preserves existing .claude/ state unless stack or MCP changed

Quick Start

Invoke the forge agent in new-milestone mode to generate the next milestone plan from ROADMAP.

Frequently Asked Questions about forge-new-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan the next project milestone from a ROADMAP file without rework?

Plan the next project milestone by invoking the forge agent in new-milestone mode. It reads ROADMAP.md, validates prerequisites, and generates PLAN.md with per-milestone tasks XML files.

Does milestone planning regenerate the .claude directory configuration?

Milestone planning preserves the existing .claude directory state by default. It only regenerates .claude configurations if the technology stack or MCP setup changed during the planning process.

How do I update architecture artifacts when scoping a new milestone?

Update architecture artifacts by running the milestone planning process. It automatically updates ARCHITECTURE.md, DECISIONS.md, and project rules when scope changes are detected from the ROADMAP.

What files do I need before starting automated milestone planning?

You need a ROADMAP.md file defining the next milestone and its prerequisites. The planning process uses this roadmap to generate PLAN.md and task XML files.

Can I verify a project plan before writing files to the repository?

Yes, the milestone planning workflow runs semantic checks to verify the plan and requires explicit user confirmation before writing any planning artifacts to your project.

Why does milestone planning fail after archiving the current milestone?

Milestone planning fails if ROADMAP.md does not define the next milestone or if prerequisites are unmet. The process validates these conditions before generating the PLAN.md and tasks XML files.

Related Skills