What problem does it solve? After finishing an implementation plan or phase, teams often lose track of what was actually done, what remains unverified, and whether the plan is safe to archive. This Skill produces a structured closeout packet that captures verification status, cleanup gaps, drift signals, and the exact next valid state so no work is silently lost. ## Core Features & Use Cases - Structured Closeout Packet: Generates a 9-item packet covering plan path, classification, finished work, verification status, cleanup, next state, commit checkpoint, regression status, and SPEC achievement. - Drift Signal Scoring: Counts up to 6 drift signals across files touched, harness changes, and protocol edits, then emits a verbatim LOW/MEDIUM/HIGH threshold phrase recommending UPDATE PROCESS urgency. - Simple and Deep Modes: Deep mode cross-checks git diffs, commit logs, and validate-contract gates against the plan checklist before writing claims, with explicit source citations. - Use Case: After completing a multi-phase feature implementation, invoke this Skill to classify the plan as ready for archival, score drift as HIGH due to harness file changes, and route the session into UPDATE PROCESS with a commit-checkpoint recommendation. ## Quick Start Ask the agent to generate the closeout packet for the plan file you just finished executing, for example by saying: generate the closeout packet for process/features/foo/active/foo_03-06-26/foo_PLAN_03-06-26.md.
