← ClaudeAtlas

reconcilelisted

Close out a completed Drydock plan — consolidate the Deviation Log, diff the plan's assumptions against what execution actually revealed, and produce proposed (never auto-applied) updates to project docs like CLAUDE.md, ADRs, and architecture notes so the next plan starts from reality instead of stale context. Invoke after the final wave passes wavecheck.
SandeepTakasi/drydock · ★ 0 · DevOps & Infrastructure · score 72
Install: claude install-skill SandeepTakasi/drydock
# Reconcile Plans die; what they learned shouldn't. You turn one executed plan into durable corrections to the project's authoritative context. You NEVER edit any doc — you propose diffs a human applies or rejects. Contract: `${CLAUDE_PLUGIN_ROOT}/skills/planwright/reference/plan-format.md`. Allowed proposal targets come from plugin config `docs_targets` (default: `CLAUDE.md,docs/decisions,docs/architecture.md`). Propose nothing outside those paths. ## Inputs A plan with all waves PASS. If any wave lacks a PASS report, refuse — reconcile on an unverified plan launders unaudited changes into the docs. **Human-gate refusal.** Read every `**Phase gate:**` line in the plan. Any phase whose gate declares a human approval must show it recorded — `CLOSED, approved by <name> — <date>`, per the format contract. An open gate, or a closed one with no name and date, is a refusal: closing the plan would record a sign-off nobody gave. Do not infer approval from a passing wave, from an APPROVED quality review, or from the fact that someone asked you to run reconcile — those are different claims, and a human gate exists precisely because none of them substitute for it. Say which phase is unsigned and stop. This refusal was added after a plan reached reconcile with all waves PASS, a properly attributed verdict sheet, and an unsigned Phase 2 gate: nothing in this skill would have stopped the close, and only the orchestrating session holding back by hand prevented it. The gate a closer ca