Agent Skills › bacoco/BMad-Skills › openspec-change-closure

openspec-change-closure

GitHub

用于归档已完成且验证通过的 OpenSpec L0-1 变更。通过检查清单、收集指标与证据，生成归档摘要并同步规范文件，确保变更闭环。

.claude/skills/openspec-change-closure/SKILL.md bacoco/BMad-Skills

Trigger Scenarios

用户要求归档或关闭变更变更已实施完成需最终化

Install

npx skills add bacoco/BMad-Skills --skill openspec-change-closure -g -y

More Options

Non-standard path

npx skills add https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/openspec-change-closure -g -y

Use without installing

npx skills use bacoco/BMad-Skills@openspec-change-closure

指定 Agent (Claude Code)

npx skills add bacoco/BMad-Skills --skill openspec-change-closure -a claude-code -g -y

安装 repo 全部 skill

npx skills add bacoco/BMad-Skills --all -g -y

预览 repo 内 skill

npx skills add bacoco/BMad-Skills --list

SKILL.md

Frontmatter

{
    "name": "openspec-change-closure",
    "metadata": {
        "outputs": [
            "archive-doc",
            "merged-specs",
            "closure-report"
        ],
        "triggers": {
            "keywords": [
                "archive",
                "close",
                "document",
                "finalize",
                "complete"
            ],
            "patterns": [
                "archive this change",
                "close change",
                "document change",
                "finalize change",
                "archive"
            ]
        },
        "auto-invoke": true,
        "capabilities": [
            "change-archival",
            "documentation",
            "spec-merging",
            "closure"
        ],
        "prerequisites": [
            "implemented-code"
        ]
    },
    "description": "Archives completed L0-1 changes.",
    "allowed-tools": [
        "Read",
        "Write",
        "Grep",
        "Bash"
    ]
}

OpenSpec Archive Skill

When to Invoke

Automatically activate when user:

Says "Archive this change", "Close the change", "Finalize change"
Asks "Document this change", "Mark as complete", "Archive proposal [X]"
Has completed an OpenSpec change that needs closure
Mentions "archive", "close", "document", "finalize" with change context
Uses words like: archive, close, document, finalize, complete, wrap up

Specific trigger phrases:

"Archive this change"
"Close change [proposal-id]"
"Document the change"
"Finalize the implementation"
"Mark proposal [X] as complete"
"Wrap up this change"

Prerequisites:

OpenSpec change has been implemented
Tests pass and validation is complete
Deployment or rollout is done (or documented)

Do NOT invoke when:

Change not yet implemented (use openspec-change-implementation)
Tests failing or validation incomplete
Missing approvals or sign-offs
Change still in progress

Auto-document:

Learnings and deviations
Metrics (time, lines changed, tests added)
Follow-up tasks if any

Mission

Document the outcome of Level 0-1 work, ensuring artifacts, approvals, and follow-up actions are captured before closing the OpenSpec workflow.

Inputs Required

proposal: original proposal.md with approvals
implementation_log: execution notes or commits from implement skill
validation_evidence: test results or reviewer feedback

Outputs

Archive summary (archive.md) with outcomes, metrics, and learnings (template: assets/archive-template.md.template)
Updated proposal/tasks reflecting completion status
Deployment or rollback notes stored with project documentation
Canonical specs in openspec/specs/ synchronized with approved deltas

scripts/archive_change.py copies validated spec deltas from openspec/changes/<change-id>/specs/ into openspec/specs/.

Process

Verify closure conditions using CHECKLIST.md.
Gather final state: what shipped, what remains, and any deviations.
Record metrics, approvals, and validation evidence in archive.md.
Run scripts/archive_change.py <change-id> to merge spec deltas into openspec/specs/.
Capture learnings and recommended follow-up actions, then update artifacts and communicate closure.