phase-closeout-audit

Run phase closeout audits with evidence collection and governance routing.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Vel-Labs/ClearIntent --skill phase-closeout-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-closeout-audit
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/phase-closeout-audit
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill phase-closeout-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase closeout is the evidence pass that turns completed work into inspectable project truth, enabling transparent governance and auditable records.

Core Features & Use Cases

  • Provides a repeatable workflow to identify phase scope, collect evidence, run verification commands (e.g., npm run check), and update governance artifacts (DECISIONS.md, CHANGELOG.md, ROADMAP).
  • Uses a standard closeout audit template to record exact commands, outputs, findings, and follow-up actions.
  • Ensures downstream routing and future work items are clearly defined and traceable with dated decisions.

Quick Start

Run the closeout audit by applying the templates/closeout-audit.md to the latest phase work and record the exact commands and results.

Frequently Asked Questions about phase-closeout-audit

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

FAQPage Schema
How do I conduct a phase closeout audit with verifiable evidence?

A phase closeout audit identifies phase scope, collects evidence, runs verification commands like npm run check, and updates governance artifacts including DECISIONS.md, ROADMAP.md, and CHANGELOG.md to ensure traceable project truth.

What is the best way to document phase closeout decisions and routing updates?

Documenting phase closeouts uses a standard audit template to record exact commands, outputs, findings, and follow-up actions, ensuring downstream routing and future work items are traceable with dated decisions.

Do I need specific governance files to run a phase closeout audit?

Yes, phase closeout audits require updating DECISIONS.md, ROADMAP.md, and CHANGELOG.md. These governance artifacts receive routing updates and audit evidence to maintain transparent and inspectable project records.

How do I update ROADMAP.md and CHANGELOG.md after project phase completion?

Updating ROADMAP.md and CHANGELOG.md involves applying the closeout-audit template to the latest phase work, recording exact verification command results, and routing updates deterministically across these governance artifacts.

Can I use standard templates for project governance and decision logging?

Yes, applying standard closeout audit templates ensures commands and results are documented consistently, turning completed work into inspectable project truth with audit trails for transparent governance.

Why does phase closeout require collecting evidence and running verification commands?

Collecting evidence and running verification commands during phase closeout turns completed work into inspectable project truth, enabling transparent governance by updating audit artifacts deterministically with exact outputs.