What problem does it solve? Teams often report plan progress with vague claims like "basically complete" or "mostly done" that hide unfinished work and unverified results. This Skill inspects the actual project artifacts—code, tests, docs, configs, logs—and produces a factual implementation report with explicit completion percentages, verified engineering benefits, and honest gap analysis. ## Core Features & Use Cases - Evidence-Based Completion Scoring: Calculates overall, stage, and module completion percentages from explicit denominators using a 0/25/50/75/100 scoring scale tied to concrete evidence. - Goal Alignment & Engineering Benefit Matrices: Maps planned goals to actual work and requires concrete benefits with metrics, baselines, targets, observed results, and verification evidence. - Unfinished-Work Impact Analysis: Lists every incomplete item with a specific reason, supporting evidence, impact if left unresolved, and recommended next actions with priority and dependencies. - Use Case: After a refactor plan is executed, ask for a completion report and receive tables and Mermaid charts showing which modules are verified at 100%, which are partial, and exactly what remains blocked or deferred. ## Quick Start Use the plan-report skill to audit the current repository against our migration plan and produce a completion report with stage percentages, verified engineering benefits, and unfinished-work impact analysis.
