planner-gap-closure

Create gap-closure plans from VERIFICATION and UAT failures into PLAN.md.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-gap-closure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-gap-closure
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/planner-gap-closure
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-gap-closure

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about planner-gap-closure

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

FAQPage Schema
How do I create an executable plan from UAT failures?

To create a gap-closure plan from UAT failures, you parse diagnosed UAT gaps, extract missing items and artifacts, then group them by dependency order into an executable PLAN.md with wave planning and autonomous execution flags.

What is gap-closure planning in software verification?

Gap-closure planning is the process of turning verification or UAT failures into targeted, executable plans that address observed deficiencies by clustering gaps by artifact and dependency order.

How do I group verification gaps by artifact and dependency order?

You group verification gaps by clustering extracted gap details such as truth, reason, and artifacts, prioritizing the fixing of stubs and sequencing dependencies to generate coherent, runnable plans.

Does generating a gap-closure PLAN.md require existing SUMMARIES?

Loading existing SUMMARIES is supported to avoid duplication when parsing gaps, while the plan generation itself leverages phase_dir context alongside VERIFICATION and UAT artifacts.

What's the best way to structure a PLAN.md for autonomous execution?

The best way to structure a PLAN.md for autonomous execution is using a YAML frontmatter block that includes phase, plan, type, wave, depends_on, files_modified, autonomous, and gap_closure flags.

Can I use gap-closure planning without phase identifiers?

No, gap-closure planning enforces phase identifiers within the PLAN.md and uses explicit template placeholders like {{phase}} to standardize plan generation across phases.