Verified:GitHub

gsd-new-milestone

Create a new milestone cycle by updating planning documents and resetting state.

Updated May 21, 2026

Search Tags:#workflow orchestration #roadmap generation #project documentation #milestone planning #brownfield projects #requirements scoping

Ready to run

npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-new-milestone-jedmamosto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-new-milestone
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-new-milestone
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-new-milestone-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you reliably start a new milestone in a brownfield project by turning “what’s next” into scoped requirements, an updated roadmap, and a reset state for execution.

Core Features & Use Cases

Milestone kickoff with structured gates: Runs the full questioning → research (optional) → requirements → roadmap flow while preserving workflow validations and approvals.
Project history-aware updates: Updates existing planning artifacts rather than starting from scratch, keeping continuity with prior work.
Brownfield equivalent of a new-project cycle: Uses PROJECT.md history to gather direction and produces the “what to do next” documentation set.

Quick Start

Run gsd-new-milestone and provide the milestone name like v1.1 Notifications to update PROJECT.md and generate REQUIREMENTS.md and ROADMAP.md for execution.

Frequently Asked Questions about gsd-new-milestone

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

FAQPage Schema

How do I start milestone planning for an existing brownfield project?▼

You start milestone planning for a brownfield project by running the milestone cycle, which reads existing PROJECT.md history, asks scoping questions, and generates updated REQUIREMENTS.md and ROADMAP.md files.

Can I generate a roadmap without losing existing project documentation?▼

Yes, roadmap generation preserves existing project documentation by updating planning artifacts like PROJECT.md rather than starting from scratch, ensuring continuity with prior project history while adding the new milestone roadmap.

What is the process for requirements scoping when starting a new project milestone?▼

Requirements scoping for a new project milestone involves an orchestrated questioning flow with optional domain research, which translates the next objectives into a structured REQUIREMENTS.md document for execution.

Does milestone planning work if my project has no prior state or history?▼

No, this milestone planning workflow requires a brownfield project where PROJECT.md already contains history, meaning it is designed to update existing artifacts rather than initialize a new project from scratch.

What happens to the project state file after generating a new milestone roadmap?▼

After generating the new milestone roadmap, the workflow resets STATE.md to clear prior execution progress and then hands off to the phase execution cycle for the newly planned milestone.

Best way to turn project objectives into a continued numbered roadmap?▼

The best way to turn project objectives into a continued numbered roadmap is to run a structured questioning and optional research flow that scopes requirements and appends the next milestone to your existing project roadmap.