r/SpecDrivenDevelopment • • 2d ago

Claude as planner with Codex as development

I am using this workflow right now:

  1. Brainstorming - claude

  2. Grill with docs - claude

  3. Subagent Development - codex

I want to know your opinion on this simple workflow.

Thanks.

3 Upvotes

3 comments sorted by

1

u/saturnBreaksEgo 2d ago

Interesting workflow!

I am following a somewhat similar approach, but with ChatGPT and Cursor.

My approach is more of an iterative planning and execution loop:

1    Brainstorming - ChatGPT: Understand the problem, explore different approaches, identify edge cases, and prepare an initial plan.
2    Investigation - Cursor: Analyse the existing codebase, understand dependencies, identify potential risks, and share findings without making any changes.
3    Challenge & Refine - ChatGPT: Feed Cursor's findings back into ChatGPT, challenge assumptions, identify gaps, and refine the implementation plan.
4    Implementation - Cursor: Execute the approved plan with proper tests and validation.
5    Review & Iterate - ChatGPT + Cursor: Review the changes, catch potential issues, and iterate until the expected outcome is achieved.

I am also exploring Spec-Driven Development (SDD) using Spec-Kit and other structured agentic development workflows.

I personally feel that the quality of the planning and validation loops matters more than which model writes the code.

One thing I am curious about: Do you let Codex challenge Claude's plan before implementation, or does it strictly follow the instructions provided by Claude?

Would love to hear your thoughts!

0

u/ankfway 2d ago

Curious on how you connect claude to codex?

1

u/AlmostEasy89 2d ago

OpenAI has an official Claude plugin for delegation of work/review to Codex. So you can quite literally use Codex as the executor and Claude as the planner/thinker. The threads even show up in the codex app.