spec-closeout

Verify and close OpenSpec changes with documentation updates.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/paradox123/shared-ai-docs --skill spec-closeout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-closeout
Source: https://github.com/paradox123/shared-ai-docs/tree/main/skills-repo/skills/spec-closeout
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill spec-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill ensures that accepted spec changes are closed with full traceability, mandatory verification, and updated project documentation to prevent drift.

Core Features & Use Cases

  • Verification-driven closeout: Execute all required verification commands and report results to ensure change readiness.
  • OpenSpec lifecycle management: Close or archive OpenSpec changes when verification is green and document the outcomes.
  • Documentation synchronization: Update spec status and related project docs to reflect the closed state.

Quick Start

Initiate the closeout by supplying the repository path, the spec file path, and the OpenSpec change id (if applicable), and let the skill verify all steps and update documentation.

Frequently Asked Questions about spec-closeout

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

FAQPage Schema
How do I close accepted spec changes with verification and documentation sync?

Close accepted spec changes by executing mandatory verification commands, archiving the OpenSpec change, and synchronizing project documentation to ensure full traceability and prevent drift.

What is OpenSpec lifecycle management and when do I need to archive changes?

OpenSpec lifecycle management closes or archives spec changes when verification outcomes are green, ensuring updated project documentation reflects the closed state and prevents configuration drift.

How do I provide evidence of change readiness during project closeout?

Provide change readiness evidence by running all required verification commands, capturing the outcomes, and reporting a final status of READY or NOT READY based on the verification results.

Do I need a specific repository path and spec file to start the closeout process?

You need to supply the repository path, the spec file path, and the OpenSpec change id if applicable to initiate the closeout, verify all steps, and update documentation accurately.

Why does documentation synchronization matter when closing spec changes?

Documentation synchronization matters because it updates spec status and related project docs to reflect the closed state, preventing drift and ensuring accepted changes maintain full traceability.

What happens if verification outcomes are NOT READY during spec closeout?

If verification outcomes are NOT READY, the spec change is not closed or archived, ensuring accepted changes only finalize when all required verification commands pass and evidence is captured.