- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add dzhng/skills --skill close-spec -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add dzhng/skills --skill close-spec -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add dzhng/skills --skill close-spec -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add dzhng/skills --skill close-spec -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/dzhng/skills/tree/HEAD/skills/engineering/close-spec게시자 제공
A spec is a build plan while you're building and a rationale record once you've shipped. Closing flips it from one to the other. The plan was a ladder of slices and predictions; the record is the layer of meaning the code can't hold — why this exists, what it must never break, what you tried that failed. The code is the single source of truth for how; the closed spec is the source of truth for why, and a map into the code.
Do not summarize the implementation. Anyone can read the code. If a paragraph restates what a function does, cut it and point at the function instead.
Confirm it shipped. The feature is merged or working in-tree and its tests/screenshot gates are green. If slices remain unverified, it isn't done — finish or review first.
Diff plan against reality. Read the spec's README and slices, then read what actually landed. Note every place the build diverged from the plan: dropped slices, renamed seams, a mechanic that turned out different, an assumption that broke. The divergences are the most valuable thing to record — they're exactly what a future reader would otherwise re-derive.
Move it. specs/<feature>/ → specs/done/<feature>/ (use git mv).
Single-file specs: specs/<feature>.md → specs/done/<feature>.md.
Rewrite the README as a record, not a plan. Keep:
Cut: slice-by-slice build order, "next we will…", scaffolding instructions, per-slice verification checklists, and any prose that re-narrates code.
Collapse the slices, preserve the imagery. The slices were the build
ladder; once shipped they're sediment. Fold anything durable (a divergence,
a dead end, an invariant a slice established) into the README, then delete
slices/. But keep the baseline, comparison, and inspiration images —
the references the work was measured against — and the visualizations/ or
assets/ that still help a reader judge the result. These are provenance,
not scaffolding: discard a build instruction, never the picture that
defined what the build was aiming at. Wire each one into the README's
visual-provenance trail so the story of where the requirement came from
survives the close.
Fix references. Update links that pointed at the old path. If [[memory]]
notes or other skills referenced the spec, repoint them.
Audit every statement, unbiased. Spawn sub-agents that did not write the spec and lack the conversation, and have them check the final document claim by claim against the actual code and tests. Fan out — one agent per section, or split the claim list across agents — so no single biased pass waves it through. Each agent returns a verdict per statement:
Treat unsupported, contradicted, or stale statements as defects: fix the spec (or the pointer) and re-audit the changed claims. The spec is not closed while any statement is unverified.
The spec lives under specs/done/, reads as why-and-what-must-hold rather than
how, names the code that implements it, preserves the baseline and inspiration
imagery the work was measured against, and every statement has survived an
unbiased audit against the code. A fresh reader gets the intent, the
invariants, and the visual standard without the code — the story of why it's
done and how the decisions were made — and the mechanics by following the
pointers into it.
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
---name: close-specdescription: When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a…---# skills/engineering/close-spec/SKILL.md개요
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](../review/SKILL.md) (run before closing).
FAQ
게시자에게서 skills/engineering/close-spec/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/dzhng/skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.