Spec
Create, amend, or backprop bugs into SPEC.md at repo root.
Install
npx skills add JuliusBrussee/cavekit --skill spec -g -a claude-code -y- Repository
- JuliusBrussee/cavekit1.2k
- Category
- Writing
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 712 tokens
- Runs scripts
- No, instructions only
What it does
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
spec, spec mutator
Read FORMAT.md at repo root if not already loaded. Caveman skill applies to all writes here.
DISPATCH
Inspect user request and project state:
- No
SPEC.mdat repo root AND args describe idea → NEW - No
SPEC.mdANDfrom-codein args → DISTILL SPEC.mdexists AND args startbug:→ BACKPROPSPEC.mdexists AND args startamend→ AMENDSPEC.mdexists, no args → ask user which mode
INPUTS, spec is the sole mutator
The other verbs produce material; spec writes it. Ingest their handoff blocks into the right section, show a diff, write on OK:
- grill → sharpened §G + §C
- research → §R rows (add the §R section if absent)
- review → drafted §V lines + the risk verdict
- deepen → §I/§V/§T amendments
⊥ rewrite a section the handoff did not name. Sectioned ownership (see FORMAT.md).
NEW, idea → spec
Input: user idea. If it arrived fuzzy, prefer running grill first.
Steps:
- Extract goal (1 line, caveman). → §G.
- List constraints user stated or implied. → §C.
- List external surfaces user named. → §I.
- §R only if research ran, else omit the section (right-size).
- Propose initial invariants. → §V (numbered V1…).
- Break goal into ordered tasks. → §T pipe table, all status
., ids T1… - §B section with header row only (
id|date|cause|fix).
Write to SPEC.md. Show user full file. Ask: "spec OK? /review if high-blast-radius, else /build."
DISTILL, code → spec
Walk repo. Produce §G (infer from README/package.json/main entry), §C (infer from stack), §I (enumerate public APIs/CLIs/configs), §V (derive from tests and assertions), §T (one task per known TODO or missing test), §B (empty).
Caveman everywhere. Flag uncertain items with ? in text so user can confirm.
BACKPROP, bug → §B + §V
Input: bug: <description>.
