Routes the 14 superpowers agent-discipline skills so the right one fires at the right phase: the agent cannot skip brainstorming, TDD, debugging, review, or verification. Skills by Jesse Vincent (https://github.com/obra/superpowers, MIT). Routing by Flowy.
This file reads your intent and auto-invokes the right skill at the right moment. You just prompt.
The file
flow.superpowers-flow.FLOW.md
# FLOW.md: Superpowers Flow
> Routes the 14 superpowers agent-discipline skills so the right one fires at the right phase: the agent cannot skip brainstorming, TDD, debugging, review, or verification.
> Skills by Jesse Vincent (https://github.com/obra/superpowers, MIT). Routing by Flowy.
<!-- The Flowy engine supplies the universal contract (announce ritual, invoke/READ,
host-wins, post-compaction re-read). This file carries only the routing. -->
## Routing
**The rule:** when a trigger matches you INVOKE the named skill BEFORE doing the task yourself. Writing the code, patching the bug, or claiming "done" without first invoking is the failure this Flow exists to stop.
```
USER MESSAGE
├─ session start / first message? → invoke using-superpowers (bootstrap once)
├─ new idea / feature / project? → invoke brainstorming gate: approved design doc
├─ design exists, no plan? → invoke writing-plans gate: checkboxed tasks, approved
├─ plan has unchecked tasks?
│ ├─ 3+ independent tasks? → invoke subagent-driven-development
Why it ships
14 hand-picked skills. One FLOW.md to glue them. Reviewed before it shipped.
@obra: Author of superpowers — an agentic skills framework & development methodology that works. github.com/obra/superpowers
Submit a variant.
Got a sharper version of this routing? We review every submission.
> /flowy superpowers-flow
✓ active · Flowy reads every prompt now
> upstream-link idea, skills sync, validator friction, a LICENSE bugyou named no skill. detected: scope work↳ auto-invokes brainstorming → 4 explore agents, parallel
✓ all four scoped. design gate locked. 0 wandering.> what does this transcript showjust a question · Flowy invokes nothing
A real session, condensed. Four problems in one prompt; the Flow scoped all four before writing code. You never opened the catalog.