hyperflowlisted

# Hyperflow Use the smallest workflow that can finish correctly. Read project instructions and the relevant code before asking questions or choosing a lane. Do not run startup commands, write project state, or spawn an agent merely to route work. ## Lanes | Lane | Use when | Planning ceiling | Plan + build ceiling | Artefact | |---|---|---:|---:|---| | Direct | Clear, reversible work in one subsystem | 0 child calls | 0 child calls | None unless the user asked for a plan | | Focused | Moderate work with several related tasks | At most 2 child calls | At most 4 child calls total | One `.hyperflow/tasks/<slug>.md` | | Deep | Security, migrations, cross-boundary architecture, or material external research | At most 5 child calls | At most 8 child calls total | One `.hyperflow/tasks/<slug>.md` | Full-chain ceilings include investigators, planners, workers, reviews, and retries. The coordinator performs remaining dependent work when another child call would exceed the ceiling. For a plan-and-build request, defer the independent plan review to the final cumulative review; do not review the same decision twice. Escalate when new evidence crosses a lane boundary. Never downgrade merely to save time. ## Intent routing | Intent | Action | |---|---| | build, implement, add, refactor | Inspect, choose a lane, then continue through `dispatch` without a build confirmation | | fix, solve, failing behavior | Run `trace`; when the request asks for a fix, continue into execution after t