gsd-plan-milestone-gaps

To turn milestone audit findings into roadmap phases, this Skill reads the latest .planning/v*-MILESTONE-AUDIT.md file, groups related gaps logically, and proposes phase entries for your ROADMAP.md. It applies prioritization gates and requests user confirmation before appending any confirmed phases to prevent accidental edits.

The best way to update a project roadmap after a milestone audit is to group identified gaps into logical fix phases and append them to ROADMAP.md. This Skill preserves existing workflow gates and requires user confirmation before modifying the roadmap to ensure accurate project planning.

Yes, you can automatically group security, QA, and delivery gaps from an audit file into project phases. The Skill ingests the most recent MILESTONE-AUDIT.md, logically clusters related issues, and proposes structured roadmap entries to close those gaps without manually adding each phase.

Yes, the roadmap update process requires manual confirmation before editing. The Skill applies prioritization gates to grouped gaps and asks for user confirmation to avoid accidental edits, ensuring you maintain control over the phases added to your ROADMAP.md file.

You need to generate fix phases from a milestone audit file when your audit identifies security, QA, or delivery gaps that require tracked remediation. This Skill reads the v*-MILESTONE-AUDIT.md output and translates those gaps into structured entries for your project planning workflow.

Yes, this Skill will preserve existing workflow gates when appending new phases to the roadmap. It reads the MILESTONE-AUDIT.md, groups the gaps, and carefully updates ROADMAP.md with confirmed phase entries while maintaining all previously established project planning gates.