dev

Design a well thought out architecture with options and trade-offs, grounded in the project's code base. Proactively suggest to the user to use this skill when creating complex slices that involve cross-cutting decisions or new patterns.

Work through a slice's close-out report with the operator — bring them what the report asks of them (actions, decisions, risks, card requests), take their rulings in the session or from the report's Disposition lines, execute them (card / fix now / fold into a slice / close / defer), and close the report. Invoke it yourself whenever the operator opens, discusses, pastes from, or wants to process a slice's close-out report, or asks you to do a close-out for them — the operator will not necessarily name this skill.

Make a repo usable by the dev pipeline — retire any in-repo copy of the pre-plugin workflow, settle the manifest's curated automation, write the .aiworkflowrc contract, and scaffold or migrate the spec repo. Finishes when preflight --for run is green.

The refinement session — pin a triaged slice's requirements with the operator, seed plan.md, then launch ${CLAUDE_PLUGIN_ROOT}/tools/plan_loop.py for the structural write→review round. The run loop executes the result.

Execute a planned slice — launch ${CLAUDE_PLUGIN_ROOT}/tools/run_loop.py in the background, correct errors, relay operator questions into plan.md, close out. The loop drives; this session has exactly four jobs.

Produce and maintain slices/DAG.md — a check-off lane plan that schedules every pending slice across N parallel /dev:run-slice sessions, honouring ordering requirements while minimising merge work, plus the dependency graph and per-slice analysis behind it.

File a batch of findings, bugs, or requests — read every ask as the operator wrote it, check it against the project's standing decisions, and put the batch to the operator in one chat message (every item on a line under its proposed fate, the questions only they can answer, the proposed slices); then record the survivors' asks verbatim as slice folders (slice.md under slices/backlog/NNN_slug/), the required input to /dev:plan-slice. Runs over the intake queue or a selection of it, in one sitting. Comprehension, questions, and routing only; grounding, design, and planning happen in /dev:plan-slice.