/review-plan should be invoked twice per reconciliation pass: first for discovery (finds the gaps), second for verification (confirms fixes + catches new drift the fix-pass introduced).
Why: Two data points on 2026-04-28: (1) code-inheritv2-www v3.0 reconciliation = 3 HIGH + 5 MEDIUM + 5 LOW findings (52 tool uses, 476s wall-clock); (2) code-inheritv2-test-suite v3.6 reconciliation = same 3-HIGH-5-MEDIUM-5-LOW shape (52 tool uses, 476s wall-clock). The same shape recurring across distinct repos suggests /review-plan reliably finds ~13 findings per repo regardless of how careful the original Session 2 author was. The crucial second insight: when I ran /review-plan again post-reconciliation on test-suite, the verifier confirmed 11 of 13 RESOLVED + 2 correctly DEFERRED — but caught 2 new minor issues introduced by the reconciliation itself (NEW-A: README L92 buried v1.0 paragraph that the top-of-file banner sweep missed; NEW-B: THIRD-PARTY-DEPENDENCIES.md L14 buried Session 1 of 2). The second pass took only 96s + 22 tool uses (~5x cheaper than the first) because it’s verifying specific claims, not re-discovering. Without the second pass, NEW-A + NEW-B would have shipped silently into Sprint S1.
How to apply:
- After every Session 2 + cross-pollination cycle, invoke
/review-plan(first pass — discovery) - Reconcile all surfaced findings in a single doc-reconciliation commit
- Immediately invoke
/review-planagain (second pass — verification) — do NOT skip this; the time cost is ~5x lower than the first pass and the issue-class it catches (fix-introduced drift) is otherwise invisible - Walk the previous findings list one-by-one: RESOLVED / PARTIAL / UNRESOLVED / DEFERRED per finding
- Surface any new issues introduced by the reconciliation itself (rate severity)
- 5-min follow-up commit clears the second-pass new issues
- Codify into the doc-reconciliation skill checklist + autopilot template’s standard closure procedure (forward action)