wb-flow vs OpenSpec
| Dimension | wb-flow | OpenSpec |
|---|---|---|
| Execution (plan → parallel verified changes) | ✓ | partial |
| Planning (intent → executable task graph) | ✓ | partial |
| Artifact traceability (task → explain/execute/validate links) | ✓ | — |
Architecture
OpenSpec optimizes for lightweight brownfield deltas (ADDED / MODIFIED / REMOVED). It is heavily focused on the delta/change model for existing projects, allowing quick, specific modifications. wb-flow is more comprehensive, tracking the entire artifact graph (requirements, tasks, explanations, validations) across both greenfield and brownfield projects with wave-based execution.
Decision Framework
- Choose OpenSpec if: you are doing brownfield work (e.g., "add OAuth without rewriting the world spec") and want a purely delta/change model.
- Choose wb-flow if: you need full engineering traceability, composable planning, and explicit wave-based execution.