How do I install the Spec Close skill?

Run npx skillmds@latest add ainova-systems/spec-close in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Close safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Close?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Close free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Close?

ainova-systems (@ainova-systems) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Close by ainova-systems — Agent Skill

Name: Spec Close
Author: ainova-systems

File contents

Close a Spec

Post-merge bookkeeping: confirm a shipped spec is really done and retire it, so the queue and the docs reflect reality. Runs after the owner accepts and git-merge-pr lands the change. spec-execute-next invokes this in its reset for merged specs; it also runs standalone.

Steps

Resolve the spec. Confirm it actually shipped: its PR is MERGED (gh pr view <pr> --json state,mergedAt) and the plan's ## Work steps are fully ticked. Not merged or steps unticked - STOP and report; it is not done.
Ensure the docs reconciliation landed in the merged change (spec-execute Phase D): the feature doc reflects the new behavior, durable rules and decisions were extracted. If anything is missing, apply it now (via spec-document) - the feature doc is the durable record, the spec is not; never close on stale docs.
autonomous mode: set status: completed with the date. supervised mode: write nothing - fully ticked steps plus the merged PR already read as completed (spec-discipline).
Archive per the project convention (learn from shipped specs): keep the numbered folder (default), move to specs/_archive/, or delete the plan file if the project deletes shipped plans. Never lose the record silently.
Report: spec closed, where it was archived, the feature doc(s) it updated.

Verify

PR merged and work steps ticked confirmed; the durable feature doc carries the shipped behavior; autonomous - status: completed written.

Scope / hand-off

Merging the PR - git-merge-pr (owner accept first). Resuming an unfinished spec - spec-continue.

Constraints

Never close without a merged PR and fully-ticked work steps - that is the definition of done.
The feature doc, not the spec, is the durable record; closing confirms the behavior moved there.

---name: spec-closedescription: Confirms a merged spec actually shipped - PR merged, steps ticked, docs reconciled - then archives it per the project's convention.---# Close a SpecPost-merge bookkeeping: confirm a shipped spec is really done and retire it, so the queue and the docs reflect reality. Runs after the owner accepts and `git-merge-pr` lands the change. `spec-execute-next` invokes this in its reset for merged specs; it also runs standalone.## Steps1. Resolve the spec. Confirm it actually shipped: its PR is `MERGED` (`gh pr view <pr> --json state,mergedAt`) and the plan's `## Work steps` are fully ticked. Not merged or steps unticked - STOP and report; it is not done.2. Ensure the docs reconciliation landed in the merged change (`spec-execute` Phase D): the feature doc reflects the new behavior, durable rules and decisions were extracted. If anything is missing, **apply it now** (via `spec-document`) - the feature doc is the durable record, the spec is not; never close on stale docs.3. `autonomous` mode: set `status: completed` with the date. `supervised` mode: write nothing - fully ticked steps plus the merged PR already read as `completed` (`spec-discipline`).4. Archive per the project convention (learn from shipped specs): keep the numbered folder (default), move to `specs/_archive/`, or delete the plan file if the project deletes shipped plans. Never lose the record silently.5. Report: spec closed, where it was archived, the feature doc(s) it updated.## Verify- PR merged and work steps ticked confirmed; the durable feature doc carries the shipped behavior; autonomous - `status: completed` written.## Scope / hand-off- Merging the PR - `git-merge-pr` (owner accept first). Resuming an unfinished spec - `spec-continue`.## Constraints- Never close without a merged PR and fully-ticked work steps - that is the definition of done.- The feature doc, not the spec, is the durable record; closing confirms the behavior moved there.

Frequently asked questions

Spec Close