wb-flow vs Superpowers
| Dimension | wb-flow | Superpowers |
|---|---|---|
| Execution (plan → parallel verified changes) | ✓ | partial |
| Planning (intent → executable task graph) | ✓ | — |
| Artifact traceability (task → explain/execute/validate links) | ✓ | — |
Architecture
Superpowers optimizes for minimal disciplined agent behavior (TDD, review, low ceremony). It represents the agent-as-disciplined-engineer model, aiming for the lightest possible touch. wb-flow provides a stronger persistent artifact and control plane, offering explicit traceability and orchestration layers that Superpowers omits in favor of simplicity.
Decision Framework
- Choose Superpowers if: you want the lowest ceremony, agent-as-disciplined-engineer approach.
- Choose wb-flow if: you need full engineering traceability, composable planning, and explicit wave-based execution.