From dev
Survey a codebase and produce a reverse-spec backlog in specs/systems.yml. Use when you want a queue of stable system domains to reverse-engineer over time. Triggers on: "dev/systems", "what systems should we spec", "plan reverse specs"
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev:systemsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Consumes a repo or subtree, produces `specs/systems.yml`. This is the reverse-engineering planning phase: identify stable system domains worth speccing, then let the human run `/dev:reverse` on each item over time.
Consumes a repo or subtree, produces specs/systems.yml. This is the reverse-engineering planning phase: identify stable system domains worth speccing, then let the human run /dev:reverse on each item over time.
Interpret the argument as the survey scope. Default to the repo root if none is provided.
Valid scopes:
.)plugins/, src/auth/)the plugin layer, the build system)Prefer stable architectural seams. Do not generate backlog items for one-off files, tiny utilities, or transient feature work.
Read specs/README.md if it exists. Determine which domains are already covered.
For each discovered system, classify it:
Spawn a single Explore agent to map the scoped area:
Wait for this survey before deciding the backlog shape.
Convert the survey into candidate system domains. A backlog item should represent a stable boundary that could survive multiple rounds of work.
Good:
auth-systemplugin-marketplaceproject-hooksshared-libBad:
fix-readme-copyspec-003add-hooks-docsIf one area clearly contains multiple durable subsystems, split them now. If a candidate is too small to justify its own spec, mark it fold and name the neighboring domain it belongs to.
For each actionable item, write the exact target that /dev:reverse should consume later. Reuse the most natural form:
Each actionable item must be independently runnable in a future /dev:reverse invocation.
Walk the user through:
specs/systems.ymlGet explicit approval before saving.
specs/systems.ymlWrite the backlog to specs/systems.yml. See references/systems-schema.md for the format.
Guidelines:
candidate and update items in systems:covered:pendingtarget values that /dev:reverse can consume directlyStage and commit the backlog so the tree is clean for future reverse work:
docs: dev/systems — [short scope]
specs/systems.yml is a reverse backlog, not a second spec indexspecs/README.md, prefer update over creating a duplicatespecs/systems.yml before finishingnpx claudepluginhub codethread/claude-code-plugins --plugin devGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.