What problem does it solve? After a Work Block finishes, project documentation often drifts out of sync: progress logs, context files, tasklists, and engineering memory each tell a different story. This Skill enforces a consistent, evidence-based closeout that updates all single-source-of-truth documents without rewriting history. ## Core Features & Use Cases - Post-stage documentation sync: Updates memory_bank/context.md, memory_bank/progress.md, docs/tasklist/*, and docs/engineering-memory/* based on verified stage completion evidence. - Closeout classification: Distinguishes success-closeout (all gates READY) from reporting-only closeout for BLOCKED or UNVERIFIED work, preventing false completion claims. - Orchestrator Learning Review: For non-trivial Work Blocks, reviews Define/Execute/Assure/Close findings, applies a durable utility filter, and classifies lessons as promoted, operational-only, or not-applicable with deduplication against existing engineering memory. - Use Case: After an agent completes an implementation stage, invoke this Skill to verify acceptance evidence, update progress and context files, promote a reusable lesson about a recovered build failure into engineering memory, and confirm git-ignore status of updated files. ## Quick Start Close out the current stage by syncing the memory bank, tasklist, and engineering memory based on the completed Work Block evidence.
