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 two

on-ramps

merge onto it. Everything else is standalone.

The main flow: idea → ship

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

/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.)

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.

Branch — is this a multi-session build?

Yes

→

/to-prd

(turn the thread into a PRD) →

/to-issues

(split the PRD into independently-grabbable issues). Because the issues are independent,

clear context between each one

start a fresh session per issue and kick off /implement by passing it the PRD and the single issue to work on. No → /implement right here, in the same context window. Show more Installs 1.6K Repository mattpocock/skills GitHub Stars 132.4K First Seen Today Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass