gsd:new-milestone

Create a project milestone document with scope, acceptance criteria, and metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-new-milestone-tdalile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:new-milestone
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/commands/new-milestone
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-new-milestone-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and documents clear project milestones to align teams on scope, acceptance criteria, and delivery goals, reducing ambiguity and missed deadlines.

Core Features & Use Cases

  • Milestone Definition: Capture scope, objectives, and timeline for a delivery.
  • Acceptance Criteria: Record clear pass/fail conditions for completion and verification.
  • Documentation & Handoff: Produce a concise milestone document for stakeholders and launch planning.
  • Use Case: Planning a feature release or client deliverable where formal milestone tracking and acceptance conditions are required.

Quick Start

Create a new milestone named 'MVP Release' for project Alpha with scope, acceptance criteria, and a target delivery date.

Frequently Asked Questions about gsd:new-milestone

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

FAQPage Schema
What is a project milestone document and when do I need one?

A project milestone document formalizes scope, acceptance criteria, and delivery goals for a specific release. You need it during project planning and release management to align teams, reduce ambiguity, and establish clear pass/fail conditions for stakeholder handoff.

How do I create a milestone with acceptance criteria for a feature release?

To create a milestone, define the project name, scope, target delivery date, and specific pass/fail acceptance criteria. This generates a concise milestone record suitable for tracking progress and handing off to stakeholders for launch planning.

Does this work for client deliverables that require formal milestone tracking?

Yes, it is designed for planning client deliverables where formal milestone tracking is required. It captures the necessary scope, objectives, timeline, and acceptance conditions to verify completion and ensure stakeholder alignment.

What is the best way to document project scope and delivery goals for stakeholders?

The best way is to generate a formalized milestone record capturing scope, acceptance criteria, and metadata. This produces a concise document that explicitly defines delivery goals and pass/fail conditions for stakeholder handoff.

Can I use this for release planning across multiple project milestones?

Yes, you can use this for release planning by creating a new milestone document for each delivery phase. It captures the specific scope, objectives, and timeline needed to manage multiple milestones within a broader project plan.