openspec-change-closure

Archive completed OpenSpec changes by merging delta specs into living specifications.

67|11|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/bacoco/BMad-Skills --skill openspec-change-closure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-change-closure
Source: https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/openspec-change-closure
Command: npx skills add https://github.com/bacoco/BMad-Skills --skill openspec-change-closure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill archives completed OpenSpec changes, updates living specifications, and documents learnings and outcomes.

Core Features & Use Cases

  • Archive workflow: move deltas to living specs and archive summaries.
  • Spec merging: coalesces delta specs into canonical specs.
  • Closure reporting: archive-template with outcomes and learnings.

Quick Start

Run the closure process after a change is implemented and validated.

Frequently Asked Questions about openspec-change-closure

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

FAQPage Schema
How do I archive completed OpenSpec changes after deployment?

Archive completed OpenSpec changes by running the closure process after your deployment is live and validated. The Skill moves delta specs from the changes area into living specifications, merges validated files into canonical specs, and generates an archive document with outcomes and learnings.

What happens to delta specs when I archive an OpenSpec change?

Delta specs are coalesced into canonical specifications in openspec/specs. The Skill copies validated files from openspec/changes/<change-id>/specs to the canonical specs location and produces archival artifacts documenting the merge.

Can I document outcomes and learnings when closing an OpenSpec change?

Yes. The closure process generates a closure report using an archive template that captures outcomes, metrics, and learnings from your completed change, providing structured documentation of the implementation results.

When should I run the OpenSpec change closure workflow?

Run closure after a change is implemented, validated, and the deployment is live. This triggers the archive workflow to move deltas to living specs and generate closure summaries and archival artifacts.

What files does the archive process handle?

The archive process handles delta specs stored in openspec/changes/<change-id>/specs. It validates these files, merges them into openspec/specs, and produces archive documents and closure reports as outputs.