Comparing 6 Codex CLI Workflows

The 6 Codex CLI workflows were organized into a single table.

The common flow is Research → Plan → Execute → Review → Ship, with each system differing in its detailed steps and sub-loop placement.

• Superpowers: brainstorming → writing-plans → subagent-driven-development → test-driven-development → requesting-code-review → finishing-a-development-branch
• Spec Kit: /speckit.constitution → /speckit.specify → /speckit.plan → /speckit.tasks → /speckit.implement
• gstack: /office-hours → /plan-ceo-review → /plan-eng-review → /plan-design-review → implement → /review → /qa → /ship → /land-and-deploy
• Get Shit Done: /gsd-new-project → /gsd-discuss-phase → /gsd-plan-phase → /gsd-execute-phase → /gsd-verify-work → /gsd-ship → /gsd-complete-milestone
• oh-my-codex: $deep-interview → $ralplan → $ralph
• Compound Engineering: /ce-ideate → /ce-brainstorm → /ce-plan → /ce-work → /ce-code-review → /ce-compound → repeat

The steps marked in yellow are sub-loops, repeated per task, per story, or until verification passes. Overall pipeline length ranged from 3 steps to 9 steps.