planner-gap-closure

What problem does it solve?

Gap-closure planning methodology — creating targeted plans from verification or UAT failures to address observed deficiencies with surgical precision.

Core Features & Use Cases

• Finding Gap Sources: Triggered by --gaps; uses init context (phase_dir) to locate VERIFICATION.md gap reports and UAT.md diagnoses, identifying failing artifacts.
• Parsing Gaps: Extracts gap details including truth, reason, artifacts, and missing items; loads existing SUMMARIES to avoid duplication.
• Grouping into Plans: Clusters gaps by artifact, concern, and dependency order to generate coherent, runnable plans; prioritizes fixing stubs and sequencing dependencies.
• Writing Gap Closure PLAN.md: Produces a YAML-frontmatter PLAN.md with phase, plan, type, wave, depends_on, files_modified, autonomous, and gap_closure flags to drive autonomous execution.
• Cross-References: Integrates with planner-task-breakdown and summarizes context for traceability.
• Template-Driven Execution: Uses explicit sections and placeholders (e.g., {{phase}}) to standardize plan generation across phases.

Quick Start

Provide a new gap-closure PLAN.md for the current phase by analyzing VERIFICATION.md and the diagnosed UAT gaps, then write the plan using the provided template.