- 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).
常見問題
從發布者下載 skills/engineering/close-spec/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/dzhng/skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。