harness/plugins/work-manager/common/skills/code/SKILL.md
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
npx skillsauth add popoffvg/dotfiles codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read first: @workflow — pipeline, agents contract, notes structure, hard rules.
/code <subcommand>. Pick the operation, read its reference, follow it. Default is new.
| /code … | You need to… | Reference |
|---|---|---|
| new (default) | Full spec pipeline: write spec.md (if missing) → grill loop (ask→answer→note) → produce spec-notes/ → auto-write TODO bodies. One command, end to end. | references/new.md · references/note-format.md · references/flow.md · references/todo.md |
| verify | Audit spec before implementation — completeness, per-TODO files, execution readiness, scope discipline, test honesty. Returns READY / NEEDS REVISION. | references/verify.md |
| revise | Rewrite spec.md + todos/TODO-N.md to match what the last commit for TODO-N actually shipped. No source edits. | references/revise.md |
| prototype | Settle an OPEN design decision by spawning the implementer to make small, visible code changes. | references/prototype.md |
| code-map | Produce a D2 + SVG architecture map (package or component/type map) as visual aid. | references/code-map.md |
| impl | Execute one TODO — read context, replan guard, implement, autotest, commit, report. Delegates to impl skill for work/squash routing. | ../impl/SKILL.md |
| fix | Fix behavior — analyze root cause, mark wrong notes, write corrected thoughts, fix code. | references/fix.md |
| help | This page — list all subcommands with descriptions. | (self) |
Internal reference: references/flow.md — TS pseudocode patterns for ## Changes. Used by new.
research → new → verify → impl → revise (iterate)
spec.md (if missing), runs the grill loop to empty
Open Questions, produces spec-notes/ thought graph, and auto-writes TODO bodies. One command
replaces the old write → new → todo sequence.new again if the audit fails.impl skill.new and revise edit <notes-dir>/spec.md and todos/TODO-N.md.
new produces <notes-dir>/spec-notes/NNN-{decision,fact,impl-decision}-slug.md
(format: references/note-format.md).
verify writes <notes-dir>/spec-verify.md.
fix writes <notes-dir>/spec-notes/NNN-*-slug.md (corrected thoughts).
All write only under <notes-dir>/ — never touch source code.
tools
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
testing
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
development
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
tools
One entry point for all testing work. Use when the user wants to design a test strategy (pairwise tiering across unit/integration/manual), enumerate scenarios + a coverage matrix before implementation, audit/score an existing test set for missed cases, apply black-box techniques (equivalence partitioning, boundary values, decision tables, state transition, state-combination), write BDD Given/When/Then scenarios, drive a feature/bug-fix spec-before-code (TDD), test a harness plugin in isolation, or run the verify phase where the user reviews an implementation. Invoke as `/test-suite <subcommand>`.