# Guides

Source: https://flow-next.dev/guides/

How to do the work - write specs, shape task graphs, run reviews, route models, drive the app, and work as a team.

Task-shaped pages. Each one assumes you already know what Flow-Next is and answers “how do I do this well?”

[One change through review ](https://flow-next.dev/guides/worked-example/)A real requirement, the defect review caught, its correction, and the PR evidence.

[Writing specs ](https://flow-next.dev/guides/writing-specs/)What belongs in a spec, the ready flag, how capture and refine divide the work, and the patterns that keep a team spec useful.

[From prototype to spec ](https://flow-next.dev/guides/prototype-to-spec/)Let something real answer the question first. The capture inputs, the fidelity rule, the evidence-first routes, and what happens to prototype code.

[Customizing the spec scaffold ](https://flow-next.dev/guides/spec-scaffold/)One-time read: the template cascade, house style for criteria, and the four headings flowctl parses.

[Tasks, dependencies & parallelism ](https://flow-next.dev/guides/tasks/)How a spec becomes an execution graph, what makes a good task, and when parallel workers are safe.

[Review workflow ](https://flow-next.dev/guides/review-workflow/)The gates from plan to PR, what each one checks, and one symptom-to-fix table for when a review finds something.

[Model routing & steering ](https://flow-next.dev/guides/model-routing/)Four named tiers, a routing block in your own instruction file, how each harness reaches a model, and the two layers of steering.

[Discovery before capture ](https://flow-next.dev/guides/discovery/)When an idea is too big and too unclear to capture, resolve one decision at a time until it is briefable.

[Live-app QA & driving UIs ](https://flow-next.dev/guides/live-qa/)The live pass that drives the running app against the spec, and the driver ladder underneath it.

[Keep the feature map current ](https://flow-next.dev/guides/keep-feature-map-current/)How work updates, drift reports, and the due trigger keep .flow/features/ true, and when to run maintain.

[For teams ](https://flow-next.dev/guides/for-teams/)Role map, ownership stances, spec ids across parallel creators, and the adoption ladder.

[Cookbook ](https://flow-next.dev/guides/cookbook/)96 verified recipes: skip, prompt into, chain, parallelize, route, and dial autonomy.