Ask Matt

You don't remember every skill, so ask.

A flow is a path through the skills. Most paths run along one main flow, and three on-ramps merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.

The main flow: idea → ship

The route most work travels. You have an idea and want it built.

1. /grill-with-docs — sharpen the idea by interview. Start here when you have a codebase: it's stateful, retaining what it learns in CONTEXT.md and ADRs. (No codebase? Use /grill-me — see Standalone. Both run the same /grilling primitive; grill-with-docs is the one that leaves a paper trail.)
2. Branch — can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by /handoff in both directions (see Crossing sessions):
   • /handoff out, then open a fresh session against that file,
   • /prototype to answer the question with throwaway code,
   • /handoff back what you learned, and reference it from the original idea thread.
3. Branch — is this a multi-session build?
   • Yes → /to-spec (turn the thread into a spec), then /to-issues to split it into tracer-bullet issues, each declaring its blocking edges and AFK/HITL mode. The default tracker is existing Beads state or local .scratch; a hosted tracker is used only when explicitly configured. Work the unblocked frontier: start each AFK issue with /implement in a fresh context, and surface each HITL issue to the human.
   • No → /implement right here, in the same context window.