One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-new-milestone-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-milestone
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-new-milestone
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-new-milestone-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns an existing project into a new milestone by generating the scoped “what’s next” plan while preserving project history and workflow gates.

Core Features & Use Cases

  • Milestone planning for brownfield projects: Uses existing PROJECT.md history to start a new milestone cycle.
  • Optional domain research for new features: Creates research notes under .planning/research/ when needed.
  • Scoped outputs for execution: Updates .planning/PROJECT.md, creates milestone-scoped .planning/REQUIREMENTS.md, extends phase structure in .planning/ROADMAP.md, and resets .planning/STATE.md.
  • Use case: You have a mature project and want to define the next release milestone (e.g., v1.1) with requirements and roadmap phases ready to be planned for execution.

Quick Start

Start the skill by providing a milestone name like v1.1 Notifications so it can question, (optionally) research, then update the project planning files and prepare the next execution phase.

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 a new milestone for an existing brownfield project?

To plan a new milestone for a brownfield project, the skill derives the next cycle from existing PROJECT.md history, then generates scoped requirements, optional domain research notes, and roadmap phase continuation to preserve project history and workflow gates.

What is the best way to scope requirements for a new project release?

Scoping requirements for a new release involves creating a milestone-scoped REQUIREMENTS.md file and extending the phase structure in ROADMAP.md, ensuring orderly execution by defining what is next based on prior project history.

How do I start the next milestone cycle using existing project history?

Start the next milestone cycle by providing a milestone name like v1.1 Notifications, after which the skill questions, optionally researches domain context, updates .planning files including PROJECT.md and STATE.md, and prepares the next execution phase.

Can I include domain research when initializing a new project milestone?

Yes, domain research is optional during milestone initialization; when needed, the skill creates research notes under .planning/research/ to support new feature development before updating requirements and roadmap files.

What planning files need updating when defining a new project roadmap phase?

Defining a new roadmap phase requires updating .planning/PROJECT.md, .planning/REQUIREMENTS.md, .planning/ROADMAP.md, and resetting .planning/STATE.md, with research files under .planning/research/ also updated when applicable.

When should I not use milestone planning for brownfield projects?

Milestone planning for brownfield projects should not be used for greenfield projects lacking prior PROJECT.md history, as it requires an existing project state with established workflow gates to derive the next milestone accurately.