Which skill
Route the request to the fewest skills that do it, then follow those skills. This skill holds no rules of its own about the work. Why: a rule copied here drifts from the skill that owns it.
Scope
- One skill: when one fits, run it. A chain is for work that really has several stages, never to look thorough.
- Two fit equally: ask one question, then route.
- Before routing: ask every blocking question in one turn. Never invent a fact. Put an unknown under Open questions and say what it blocks. Replies are 1–2 lines; a paragraph only when the user asks.
Pick
| The request | Skill |
|---|---|
| Build a whole feature after one round of questions: ask, prototype, build, prove, review, PR | deliver |
| Write or change code, or a test that was asked for | coding |
| Write tests for a change, fix a flaky test, "what could break here" | testing |
| Manual test cases, QA coverage, how to test a flow by hand | test-cases |
| Find why something fails: a crash, wrong result, red CI, a production error | debug |
| Review a diff, a branch or a pull request, what a change could break, or a strict or thermo-nuclear quality review | review |
| Refactor, clean up, deduplicate, or standardize an area | refactor |
| Talk through an idea, a PRD, a spec, a system design, an architecture or scale review, a runbook, a README | design-docs |
| A throwaway prototype to answer one design question | prototype |
| Auth, input, uploads, secrets, a scanner finding, a threat model | security |
| Logs, metrics, traces, alerts, an SLO, a slow endpoint | observability |
| SQL, schema, migrations, transactions, pooling | database |
| Prove a change works in the real app, or set up verification for a repo | prove |
| Drive a real browser or app to check something | automation |
| Finish a change into a PR or MR, a rollback plan, a release checklist, a tag | ship |
| Write or update a PR or MR title or body, or draft review replies | writing-pr |
| Create or edit a skill | writing-skills |
Alongside, not instead:
- Load
go, where installed, with any skill that touches.gofiles. - Load
databasewhen the work reaches SQL. - Load
securitywhen it crosses a trust boundary. - Load
observabilitywhen it adds a path on-call must see.
Read the chosen skill and follow it.
Chains
Run the stages in order. Each skill's own stops still hold. Pause for the user's yes before any stage that writes code, pushes, or touches a shared system.
- Bug:
debugfinds and proves the cause, and stops. After a yes,codingfixes it, with the reproduction test written red first throughtesting. Thenreview. Addtest-casesonly when no automated test can reach it. - Feature:
design-docswhen there is no agreed spec, thencoding, thentesting, thenreview.shipcomes when the user wants it pushed. When the user wants all the questions first and the rest done with proof,deliverruns this chain with a prototype andprove. - Release:
review, thenship. Ship's done gate, its interview, andwriting-prfor the description all run insideship. A migration followsdatabaseand ship's deploy notes. - Cleanup:
refactor, which applies each approved step throughcoding. - Design:
design-docsfor the system design, then a spec indesign-docsif one is still needed, thencodingafter approval.prototypefirst when one question needs trying before deciding. - Slow:
observabilitymeasures it first.databasefor a slow query. Thencodingfor the change the measurement points to. - Live incident:
debug, reading production only. A mitigation is a proposal for the user. The fix then follows the bug chain.
Limits that hold across chains
debugandrefactorchange no code until the user says yes.reviewfixes proven findings only in the user's own work, and asks first before a schema, API, security or user-visible change. Someone else's PR is report-only.shipopens the PR or MR and stops. The user merges, deploys and tags.design-docsdoesn't write code.- No skill pushes to the default branch or writes to production.
Replies
Talk to the user in simple English: short sentences, everyday words, and a technical term only where it is needed, explained the first time it appears.
Name the skill or chain in one line, then run the first stage.