gsd-new-milestone

Transform next-step ambiguity into scoped requirements and an execution roadmap.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-new-milestone-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-milestone
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-new-milestone
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-new-milestone-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you start a new project milestone in a brownfield repository by turning ambiguity about “what’s next” into scoped requirements and a clear roadmap, while keeping the project’s existing history intact.

Core Features & Use Cases

  • Milestone kickoff with guided questioning: prompts for a milestone name and performs validation and gatekeeping through the workflow.
  • Project planning updates: updates milestone goals in .planning/PROJECT.md and resets milestone state in .planning/STATE.md.
  • Requirements and roadmap generation: produces .planning/REQUIREMENTS.md and extends .planning/ROADMAP.md with phase structure.
  • Optional research for new features: adds domain research under .planning/research/ when applicable.

Use Case: You already have PROJECT.md history and want to define and plan the next release (e.g., v1.1) with requirements and an execution-ready roadmap without starting from scratch.

Quick Start

Run the Skill with your milestone name: openforce /gsd-new-milestone "v1.1 Notifications".

Frequently Asked Questions about gsd-new-milestone

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

FAQPage Schema
How do I plan the next milestone in a brownfield project?

Milestone planning in a brownfield project transforms ambiguous next steps into scoped requirements and an execution roadmap while preserving existing project history. It updates planning artifacts like PROJECT.md and ROADMAP.md to reflect new release goals.

What project documentation do I need to update for milestone planning?

Milestone planning requires updating project documentation including .planning/PROJECT.md for goals, REQUIREMENTS.md for scoped features, ROADMAP.md for phase structure, and resetting STATE.md for the new cycle.

Can I add domain research when defining new release requirements?

You can add domain research when defining new release requirements. The workflow optionally generates domain research files under a .planning/research/ directory to support new features introduced in the milestone.

What is the best way to kick off a new release cycle without losing existing history?

The best way to kick off a new release cycle without losing existing history is using a brownfield planning workflow that validates gates, updates milestone goals, and extends the roadmap while keeping all prior project artifacts intact.

Do I need an existing PROJECT.md to start milestone planning?

You need an existing PROJECT.md containing project history to start this milestone planning. The workflow is designed for brownfield environments where prior planning artifacts already exist and need to be updated.