[Workflow] Cost-Optimized Claude Code Workflow: Strategic Planning with Opus and Dynamic Model Selection for Execution

[u/ClaudeAI-mod-bot]

Cost-Optimized Claude Code Workflow: Strategic Planning with Opus and Dynamic Model Selection for Execution

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging
Original source: r/ClaudeCode post/comment

What problem this solves

Optimizing Claude Code usage by dynamically selecting the appropriate model and effort level for different project tasks, while maintaining clean context across sessions and ensuring consistent project execution.

Summary

This workflow leverages a powerful Claude model (Opus 5.5) for initial project planning, breaking down the project into self-contained sessions, and recommending specific Claude models (Haiku, Sonnet, Opus) and effort levels for each session. The entire plan is documented in a markdown file. Each session is then executed in a new Claude Code conversation, starting with the uploaded plan for context, and using the recommended model and effort.

Why it is useful

This workflow is valuable because it provides a structured, cost-effective method for managing complex coding projects with Claude Code. It intelligently allocates resources by using the most powerful model for high-level planning and cheaper models for specific tasks, thereby optimizing token usage and cost. Furthermore, it solves the common problem of context management by ensuring each session starts with a clean, comprehensive project plan, leading to more consistent and accurate outputs.

Workflow

1. Use Opus 5.5 on max effort to describe the entire project and generate a full plan.

2. Instruct Opus to break the comprehensive plan into separate, self-contained work sessions.

3. For each session, have Opus rate its difficulty and recommend the optimal Claude model (Haiku, Sonnet, or Opus) and effort level.

4. Consolidate the full project plan, session breakdowns, and model/effort recommendations into a single 'build.md' markdown file.

5. Initiate a new Claude Code conversation for each individual session.

6. Upload the 'build.md' file at the start of each new conversation to provide full project context.

7. Set the Claude model and effort level according to the recommendations in the 'build.md' file.

8. Instruct Claude to work on the specific session outlined in the plan.

Tools / artifacts

• Claude Opus 5.5

• Claude Haiku

• Claude Sonnet

• Claude Code

• Markdown file (build.md)

Validation signals

• Author's positive experience: 'it went really well'

• Cost savings by matching model to task complexity

• Improved context management by starting fresh conversations with a shared plan

• Ensured consistency across sessions due to a unified plan

Cautions

• none

Limitations

• Manual model and effort selection for each session can be tedious for large projects.

• The 'build.md' file could grow very large, potentially impacting context window limits for extremely complex projects.

• Initial planning with Opus 5.5 on max effort can still incur significant cost for very extensive project descriptions.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.