Workflow Router

You don't remember every skill, so ask.

A flow is a path through the skills. Most paths run along one main flow, and two 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 sharpens the idea by interview. Start here whenever you are working in a working directory: it's stateful, retaining what it learns in CONTEXT.md and ADRs. (No working directory? Use /grill-me instead, covered under Standalone. Both run the same /grilling primitive; grill-with-docs is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)
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 (a prototype lives in its own directory, which is exactly what /handoff is for; see Phase boundaries):
   • /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. Shape the experience and implementation plan when the work needs them. For a product-facing feature where the user journey or interface should not be invented during coding, run /ui-spec to write docs/ux-spec.md, then /tech-spec to inspect that UX and the codebase and write docs/technical-spec.md. These are complementary planning artifacts: ui-spec decides what the user experiences; tech-spec decides the simplest way to preserve it. Skip either only when its decisions are already settled and available in an equivalent approved artifact.
4. Branch: is this a multi-session build?
   • Yes → /to-spec (turn the thread into a spec), then /to-tickets to split it into tracer-bullet tickets, each declaring its blocking edges. On a local tracker that's one file per ticket under .scratch/<feature>/issues/, worked blockers-first by hand; on a real tracker the edges become native blocking links. Run /implement per ticket, clearing context between tickets, or use /implement-spec to orchestrate the full ticket graph on one integration branch.
   • No → /implement right here, in the same context window.