Start with the task
A useful route collects evidence for the desired result. A feature needs working behavior, a bug fix needs a proven cause, and performance work needs measurements.
Choose a workflow
WHAT DO YOU NEED?
Feature pipeline
Define expected behavior and acceptance criteria. Approve the plan before implementation.
Explore → Plan → Approve → Code → Check → Accept
Consider complexity, risk, change size and open questions. Short routes suit clear changes with low risk.
This is workflow guidance. Your project profile defines the available routes.
| Task | Example | Evidence |
|---|---|---|
| New or changed behavior | Product filter | Acceptance criteria verified in a preview. |
| Reproducible defect | Duplicate submission | Proven cause and the original reproduction passing. |
| Performance improvement | Faster search | Comparable measurements with correct results. |
Who manages work
A route with separate stages defines steps and approval points in advance. In loop mode the lead assigns work to a worker, reviews results and manages rework until human acceptance.
Choose a loop when work can be split into verifiable pieces and the lead can manage intermediate decisions. If a plan requires prior approval, use a separate gate. Both require acceptance criteria.
Task kind and depth
Task kind describes the result: a profile may declare feature, debug, perf and hunt with matching routes.
Depth describes how much investigation and verification is needed. A small access-control change may have high risk. Uncertainty needs clarification before selecting a short process.
Triage evaluates the task from code and proposes a kind. Policy calculates depth from complexity, risk, change size, confidence and open questions. The profile maps these to a published route; a human confirms the launch selection.
Defect investigation
For a request such as finding checkout problems, define the scope, defect criteria and expected report first. A profile can support this as hunt.
The result is a set of confirmed findings with reproduction conditions and priority. Fixing them must be part of the agreed scope or a separate task.
Build your own workflow
Connect a project and create a route. For every stage, define its input, output and condition for continuing.
These recipes are learning examples to adapt, rather than universal routes automatically available after installation.