vc-generate-closeout

Generate a 9-item post-EXECUTE closeout packet with drift signals and next-state suggestions.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-generate-closeout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-generate-closeout
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-closeout
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-generate-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate the post-EXECUTE closeout packet for a completed plan or phase. This includes archive-readiness classification, drift signal scoring, commit checkpoint recommendation, and the next-state suggestion.

Core Features & Use Cases

  • Produces a standardized 9-item closeout packet with all required fields.
  • Enforces drift-threshold phrases and archive-readiness checks for governance.
  • Supports integration with VALIDATE/REGRESSION artifacts and UPDATE PROCESS workflows.

Quick Start

Invoke the vc-generate-closeout skill at the end of a completed EXECUTE phase to generate the closeout packet.

Frequently Asked Questions about vc-generate-closeout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured closeout packet for a completed plan phase?

To generate a structured closeout packet, invoke the skill at the end of a completed EXECUTE phase. It produces a 9-item summary that includes archive-readiness classification, drift signals, commit checkpoints, and recommended next states for phase transitions.

What is plan drift scoring and when is it needed in the closeout process?

Plan drift scoring is a process governance mechanism needed during phase transitions to measure execution deviation. The closeout process enforces a required drift-threshold phrase within the packet to formally signal whether the execution stayed within acceptable variance limits.

How do I classify archive-readiness for completed validation and regression cycles?

Classifying archive-readiness involves assessing validation and regression artifacts against governance checks. The closeout packet integrates these statuses to determine if the completed plan meets the required criteria for formal archival and subsequent state transitions.

Can I integrate commit checkpoints and update process workflows into a phase transition summary?

Yes, you can integrate commit checkpoints into the phase transition summary. The generated closeout packet enforces a 9-item schema that ties directly into validation status, regression artifacts, and update process workflows to recommend the next state.

What are the limitations of using a standardized closeout schema for process governance?

The closeout schema is strictly limited to post-EXECUTE cycles and phase transitions, requiring a completed plan. It cannot be invoked mid-execution and mandates a specific 9-item structure with enforced drift-threshold phrases, limiting flexibility for non-standard archival processes.