gsd-plan-milestone-gaps

Audit requirements and phase plans to create a categorized GAPS-PLAN.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-plan-milestone-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan-milestone-gaps
Source: https://github.com/optivent/gsd-kimi-cli/tree/main/skills/gsd-plan-milestone-gaps
Command: npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-plan-milestone-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan work to fill gaps in milestone coverage, ensuring complete phase alignment and auditable traceability.

Core Features & Use Cases

  • Gap detection across milestones based on REQUIREMENTS.md and existing plans
  • Categorization of gaps into Critical, Important, and Nice-to-have
  • Generation of a formal GAPS-PLAN.md with detailed gaps, impacts, and proposed solutions
  • Integration guidance to add gaps to existing phases, create new phases, or defer to next milestones

Quick Start

Invoke the gsd-plan-milestone-gaps skill with /skill:gsd-plan-milestone-gaps to generate a structured gap plan for the milestone.

Frequently Asked Questions about gsd-plan-milestone-gaps

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

FAQPage Schema
How do I identify missing functionality in project phase plans?

Project phase plan gaps are identified by auditing requirements against existing plans. This gap analysis detects incomplete phase coverage and guides categorizing missing functionality into structured priority levels.

What is the best way to categorize milestone coverage gaps in project management?

Milestone coverage gaps are categorized into Critical, Important, and Nice-to-have tiers. This structured workflow ensures that missing requirements are prioritized effectively before generating a formal gap resolution plan.

How do I document new requirements discovered during a milestone audit?

New requirements discovered during a milestone audit are documented in a GAPS-PLAN.md file. This formal output details the identified gaps, their impacts, and proposed solutions for phase alignment.

Can I integrate deferred gap requirements into existing project phases?

Yes, gap requirements can be integrated by adding them to existing phases, creating new phases, or deferring them. This ensures complete phase alignment and auditable traceability for project planning.

When do I need a formal gap analysis for milestone planning?

A formal gap analysis for milestone planning is needed when audits reveal missing functionality, incomplete phase coverage, or new requirements. It ensures complete phase alignment and auditable traceability across the project.