vc-generate-closeout

vc-generate-closeout

Output style: closeout packet leads with the verdict/recommendation, tables for drift/readiness, one-line TL;DR — process/development-protocols/communication-standards.md.

Generate the post-EXECUTE closeout packet for a completed plan or phase. Produces a structured summary with archive-readiness classification, drift signal scoring, commit checkpoint recommendation, and the single best next valid state.

When To Invoke

Invoke this skill at the end of:

• Any non-trivial EXECUTE completion (the execute-agent's own closeout block)
• ENTER UPDATE PROCESS MODE flows before archiving a plan
• fast-mode-agent session end, after implementation and verification are complete
• Phase program closeout between phases (after validate + regression checkpoint, before inter-phase UPDATE PROCESS)

Do not invoke for trivial single-file fixes where the plan file is not involved.

Mode Selection

Choose one mode before generating the closeout packet.

Simple Mode (default)

Use when:

• The execute session just ended and all context is fresh in the conversation.
• The plan was a single-phase, straightforward implementation.
• No context compaction occurred during the session.

Behavior: write the 8-item closeout packet directly from the plan file and conversation context. No additional git or file scanning is required.

Deep Mode

Trigger conditions — use Deep Mode if any one of the following applies:

• The session was resumed after a context compaction (conversation context may be incomplete).
• The execute session was long — many sub-steps, multiple checklist sections, or multiple commits.
• The caller explicitly requests deep mode.
• The phase is part of a multi-phase program and accurate phase-completion status is required for the umbrella plan.

Behavior: gather evidence before writing the closeout packet. Run these steps in order: