Every example command from the situation pages, in reading order. Each is a starting phrase for an AI coding agent that has Pocock’s skills installed; adapt the nouns to your project. The situation page explains when to use each one and what it changes.
| Skill |
Example |
grilling |
/grill-me the request for a reconciliation-complete dashboard |
to-questionnaire |
/to-questionnaire for the operations lead: what has to be true before a batch can be handed over? |
domain-modeling |
/grill-with-docs the reconciliation dashboard |
prototype |
/prototype a state model for a batch moving from matched to reviewed to handed off |
to-spec |
/to-spec |
tdd, implement |
/implement issue #14 |
code-review |
/code-review against main, then: what did this reveal about the original request? |
| Skill |
Example |
wayfinder |
/wayfinder replace the eleven fixed reports with something finance can use for questions we have not heard yet |
grilling |
/grill-me the purpose behind the barcode scanner request |
to-questionnaire |
/to-questionnaire for the loading dock supervisor: what do you need to know about a delivery before you accept it? |
domain-modeling |
/domain-modeling record the decision to serve ad-hoc reporting rather than fixed reports |
prototype, implement |
/prototype a report builder where an analyst picks the fields to aggregate |
code-review |
/code-review against main, then: what did people do with this that we did not plan for? |
| Skill |
Example |
research |
/research which falsehoods about postal addresses apply to us, and which library handles them |
domain-modeling |
/domain-modeling what counts as an ingredient here: foil cups, optional items, either-or choices, sub-recipes? |
grill-with-docs |
/grill-with-docs where the recipe model stops and free text begins |
tdd |
/tdd a name field that accepts hyphens, apostrophes, single names, and four-part names |
implement |
/implement the recipe model from the ADR, with the free-text fallback |
domain-modeling |
/domain-modeling a recipe arrived that lists an ingredient by volume; revisit the measure category |
| Skill |
Example |
to-questionnaire |
/to-questionnaire for the finance controller: when is someone a customer to you, and what do you need to know about them? |
domain-modeling |
/domain-modeling customer: prospect, signer, payer, and who can be more than one |
grill-with-docs |
/grill-with-docs the decision to model customers as roles rather than records |
codebase-design |
/codebase-design a seam between the prospect pipeline and the billing model |
tdd, implement |
/implement the shared party model from the ADR |
wait-what |
/wait-what |
grill-with-docs |
/grill-with-docs how the acquired company's account concept maps onto our roles |
| Skill |
Example |
grilling |
/grill-me the plan to integrate third-party data |
to-questionnaire |
/to-questionnaire for the platform team: what does the events API guarantee about ordering? |
wayfinder |
/wayfinder: destination is a decision on the integration approach |
research |
/research how the vendor API handles rate limits and retries |
prototype |
/prototype the state model for a webhook-driven sync, so we can compare it with polling |
to-spec |
/to-spec |
tdd, implement |
/implement the sync slice from issue #21, end to end, before anything else |
| Skill |
Example |
grilling |
/grill-me the request for a calendar: what is the appetite and what was going wrong? |
to-questionnaire |
/to-questionnaire for the customer who asked for a calendar |
wayfinder |
/wayfinder: destination is a pitch for seeing free meeting slots |
research, prototype |
/prototype the two-month dot grid with real event data |
to-spec |
/to-spec |
to-tickets |
/to-tickets from issue #30, vertical slices, core and novel first |
triage |
/triage |
| Skill |
Example |
code-review |
/code-review against main, then answer: what did building this reveal that the spec did not know? |
prototype |
/prototype the review flow as a walkthrough the operations lead can click through |
grilling |
/grill-me the objection that the report is correct but unusable |
domain-modeling |
/domain-modeling: “complete” versus “accepted for handoff” |
wayfinder |
/wayfinder: revise the destination in light of what use revealed |
to-spec |
/to-spec |
handoff |
/handoff for the next session: implement the revised review flow |
| Skill |
Example |
research |
/research what actually happens when an order is cancelled after fulfilment starts; cite log lines and code paths |
diagnosing-bugs |
/diagnose why some writes bypass the event log; treat it as a bug in the invariant |
domain-modeling |
/domain-modeling: the codebase uses "order" for three different lifecycle objects; separate them |
codebase-design, improve-codebase-architecture |
/improve-codebase-architecture |
tdd |
/tdd characterisation tests for the cancellation path as it behaves today |
implement, code-review |
/code-review against main: does this hold the invariant recorded in ADR-0004? |
to-tickets |
/to-tickets from the remaining caveats found while reasserting the event-log invariant |
| Skill |
Example |
grilling |
/grill-me whether the intermittent checkout timeout is worth a root-cause investigation |
triage |
/triage issue #212 |
research |
/research whether the connection-reset behaviour in the pinned driver version is a known issue upstream |
diagnosing-bugs |
/diagnose the checkout timeout; budget is two sessions, stop and report if not isolated by then |
tdd |
/tdd a regression test that fails on the misaligned frame offset |
handoff |
/handoff for whoever picks up the checkout timeout next |
| Skill |
Example |
grilling |
/grill-me this ticket: which of these five features actually move the metric we care about? |
ask-matt |
/ask-matt we have a feature list and doubts about half of it; where do we start? |
wayfinder |
/wayfinder the destination is one reconciliation view operations trusts, not a reporting suite |
to-spec |
/to-spec and list the three features we decided not to build as explicit no-gos |
triage |
/triage the open requests; mark anything outside the destination as wontfix with a note |
prototype |
/prototype whether best-effort ordering is enough for the queue consumer |
implement |
/implement issue #22 |
code-review |
/code-review against main, then: which of these changes would we skip if we did it again? |
| Skill |
Example |
grill-with-docs |
/grill-with-docs the request to add a retry queue: what problem is it for? |
to-questionnaire |
/to-questionnaire for the finance lead: what does month-end close need from this system? |
domain-modeling |
/domain-modeling: "account" means three things across sales, billing, and support |
writing-for-agents |
/writing-for-agents review the ADR on the retry queue before I commit it |
wayfinder |
/wayfinder the destination is a data-import platform other teams can adopt without us |
implement |
/implement issue #31 |
teach |
/teach me how the billing context's ADRs came to be, and where they are now wrong |
handoff |
/handoff the next session will pitch the import platform proposal to the platform team |