Which skill?

You won't hold every skill in your head, so route through this instead of guessing.

A flow is a path traced across the skills. Most work follows a single main flow, with two on-ramps feeding into it. The rest are either standalone tools or a vocabulary layer that operates beneath everything else.

The main flow: idea → ship

The route most work takes. You have an idea; you want it built.

1. /grill-with-docs — sharpen the idea through interview. Start here when there is a codebase: it keeps state, folding what it learns back into CONTEXT.md and ADRs. (No codebase yet? Use /grill-me — see Standalone. Both drive the same /grilling primitive; only grill-with-docs leaves a written trail.)
2. Branch — can every open question be closed in conversation? If any question demands a runnable answer (state, business logic, a UI you have to lay eyes on), take a detour through a prototype, with /handoff carrying context in each direction (see Crossing sessions):
   • /handoff out, then start a clean session against that file,
   • /prototype to settle the question with disposable code,
   • /handoff the findings back, and cite them from the original idea thread.
3. Branch — is this a multi-session build?
   • Yes → /to-prd (fold the thread into a PRD) → /to-issues (cut the PRD into issues anyone can grab independently). Since the issues stand alone, reset context between them: open a fresh session per issue and start /implement with the PRD plus the one issue to work on.
   • No → /implement right here, without leaving this context window.