close-spec
100 / 100 · Low risk
Fine to try.
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](..…
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'close-spec' ] || [ -L ~/.agents/skills/'close-spec' ]; then echo 'A skill folder named close-spec already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/dzhng/skills' "$d" && git -C "$d" checkout --quiet '828e386301530b406b2fbd6d48136eae75720262' -- 'skills/engineering/close-spec' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/engineering/close-spec' ~/.agents/skills/'close-spec' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'close-spec' ~/.claude/skills/'close-spec' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/dzhng/skills/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-10 | 828e386 | 100 |
| 2026-11-08 | a4076b7 | 100 |
| 2026-11-07 | a4076b7 | 80 |