What problem does it solve? Implementation plans produced by multi-agent critique loops often contain broken file:line references — line numbers that drifted, ambiguous basenames matching multiple files, or paths that no longer exist. Manually auditing every reference in a large plan is slow and error-prone. ## Core Features & Use Cases - Pointed reference repair: Fixes three validator finding kinds — stale_lines (line beyond file length), ambiguous (basename matching multiple workspace files), and unresolved (nonexistent paths) — without rewriting the plan. - Two operating modes: Propose mode suggests fixes from plan plus findings; Apply mode incorporates reviewer concerns (blocker/major/minor/nit) and emits the final plan. - Structure preservation: Keeps YAML frontmatter, per-phase Work Plan structure, convergence coverage IDs, and System Coverage rows verbatim so downstream orchestrators can slice the plan into phase packages. - Use Case: After a bounded plan-critique loop finishes with needs-review status and a findings.json listing 12 stale line references, run this Skill to read each referenced file, correct the line numbers, and output the repaired final plan. ## Quick Start Apply the plan-fixer to the canonical plan using the validator findings to repair all broken file references and output the corrected markdown plan.
