plan-milestone-gaps

Create project phases from milestone audit results and update ROADMAP.md and REQUIREMENTS.md.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/sidunrealde/ArchVis --skill plan-milestone-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-milestone-gaps
Source: https://github.com/sidunrealde/ArchVis/tree/main/.github/skills/plan-milestone-gaps
Command: npx skills add https://github.com/sidunrealde/ArchVis --skill plan-milestone-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of phases needed to close gaps identified in a milestone audit, streamlining the planning process and ensuring all necessary steps are accounted for.

Core Features & Use Cases

  • Automated Phase Creation: Generates all necessary phases to address identified gaps from a milestone audit.
  • Gap Prioritization & Grouping: Organizes and groups gaps into logical, actionable phases.
  • Roadmap & Requirements Update: Automatically updates the project roadmap and requirement traceability.
  • Use Case: After running a /gsd:audit-milestone command reveals several unsatisfied requirements and integration issues, this Skill can automatically create all the necessary "fix" phases, update the ROADMAP.md and REQUIREMENTS.md files, and prompt you to plan the first phase.

Quick Start

Use the plan-milestone-gaps skill to create all phases necessary to close gaps identified by /gsd:audit-milestone.

Frequently Asked Questions about plan-milestone-gaps

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

FAQPage Schema
How do I automate milestone gap planning in agile development?

You can automate the creation of project phases to close identified milestone gaps by parsing audit results, grouping requirements and E2E flows into phases, and automatically updating ROADMAP.md and REQUIREMENTS.md.

What is the best way to group technical debt into actionable phases after an audit?

The best way to group technical debt is by parsing audit files to organize unsatisfied requirements, integration points, and E2E flows into logical phases, which updates project roadmap traceability and closes milestone gaps.

How do I update ROADMAP.md and REQUIREMENTS.md based on audit findings?

To update ROADMAP.md and REQUIREMENTS.md, parse audit results to identify unsatisfied requirements and integration issues, group them into logical phases, and apply these updates directly to the project documentation.

Can I use audit files to generate fix phases for agile workflows?

Yes, audit files can be parsed to group unsatisfied requirements, integration points, and E2E flows into logical fix phases, which are then applied to update ROADMAP.md and REQUIREMENTS.md in agile workflows.

Does plan-milestone-gaps require specific audit file formats to parse gaps?

Yes, it requires parsing audit files from a milestone audit to group requirements, integration points, and E2E flows into logical phases for updating ROADMAP.md and REQUIREMENTS.md.