closeout

Name: closeout
Availability: InStock
Author: lapagayo

Verify governance artifacts and ledger consistency before sealing a run.

1|Updated Mar 31, 2026

Search Tags:#verification #audit #governance #archive #lifecycle #artifact #closeout

Ready to run

npx skills add https://github.com/LaPaGaYo/nexus --skill closeout-lapagayo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: closeout
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/closeout
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill closeout-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures a run is closed only when all required governance checks and artifacts are present and consistent, preventing incomplete archives and future ambiguity.

Core Features & Use Cases

Verifies presence of /review, /qa, and /ship artifacts and that they meet acceptance criteria.
Enforces ledger consistency and verifies that frame/build/run artifacts align with the archive.
Provides a safe, auditable closure path and gates the next run to maintain continuity.

Quick Start

Run the closeout command after finishing a run to archive and seal the lifecycle.

Frequently Asked Questions about closeout

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

FAQPage Schema

How do I verify run lifecycle completeness before archiving and sealing?▼

Run lifecycle completeness is verified by checking that all required governance artifacts, such as review, QA, and ship records, are present and meet acceptance criteria before sealing. This ensures artifact integrity and ledger consistency for the closure.

How do I close out a project run after completing major milestones?▼

To close out a project run after major milestones, execute the closeout command to verify lifecycle completion, enforce ledger consistency, create CLOSEOUT records, and gate the next run while archiving governance artifacts.

Does closeout work with existing review, QA, and ship artifacts to enforce governance?▼

Yes, closeout works with existing review, QA, and ship artifacts by verifying their presence and acceptance criteria. It enforces governance by ensuring these artifacts align with the archive before sealing the lifecycle.

What's the best way to prevent incomplete archives during project closure?▼

The best way to prevent incomplete archives is to enforce artifact integrity and ledger consistency checks before sealing. This verifies that frame, build, and run artifacts align with the archive, providing a safe and auditable closure path.

Why does a run need CLOSEOUT records to gate the next run?▼

A run needs CLOSEOUT records to gate the next run because they enforce continuity by verifying that the current lifecycle is fully complete, archived, and consistent with governance requirements before starting a new run.