wb-flow vs GSD
| Dimension | wb-flow | GSD |
|---|---|---|
| Execution (plan → parallel verified changes) | ✓ | ✓ |
| Planning (intent → executable task graph) | ✓ | partial |
| Artifact traceability (task → explain/execute/validate links) | ✓ | — |
Architecture
GSD optimizes for context-fresh, dependency-aware wave execution. It represents the closest architectural peer to wb-flow on the execution side. Its philosophy is to keep context fresh and execute small, dependency-aware plans. wb-flow takes a broader approach by making the whole process a composable, traceable, model-aware workflow spanning from planning to execution validation.
Decision Framework
- Choose GSD if: you want to keep context fresh, execute small dependency-aware plans and worktrees, and prefer a tool whose center of gravity is pure execution architecture.
- Choose wb-flow if: you need full engineering traceability, composable planning, and explicit wave-based execution with a unified control plane.