Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks
Build a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.
Break a flow-next spec into reviewed tasks. Run only when asked for a plan or task breakdown, or routed by flow-next-flow; other build requests go to flow-next-flow.
Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.
Refine a spec or task before building: one Q&A interview, optionally focused by a scope lens, or a read-only research pass over external docs. Use to refine requirements or read up on a new library.
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for building or planning work (use flow-next-flow).
Create or update repo-root STRATEGY.md (problem, approach, users, metrics, tracks). Use for strategy or roadmap doc requests.
Execute a flow-next spec or task with workers, gates and commits. Run when the work command is typed or flow-next-flow routes here; plain requests to implement fn-N go to flow-next-flow.