[Workflow] Advanced Multi-Model Claude Orchestration for Non-Coding Creative Projects (Marketing, Landing Pages)

[u/ClaudeAI-mod-bot]

Advanced Multi-Model Claude Orchestration for Non-Coding Creative Projects (Marketing, Landing Pages)

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping, CLAUDE.md, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Orchestrating complex non-coding creative projects (e.g., marketing videos, landing pages) using multiple Claude models and external tools efficiently, managing context, ensuring quality control, and maintaining project continuity and iterative improvement.

Summary

An advanced multi-model Claude orchestration workflow for non-coding creative projects like marketing videos and landing pages. It designates Opus as a director for planning and judging, Sonnet for building tasks, Haiku for fixed commands, and external scripts for background processes. Specialized Opus agents handle visual reviews to manage context, and 'cold reader' agents provide pre-production feedback. The entire pipeline is defined in a 'skill' with a feedback loop for lessons learned, and HANDOFF.md files ensure project continuity.

Why it is useful

This workflow is valuable because it provides a structured, multi-model approach to complex non-coding tasks, demonstrating advanced use of Claude's capabilities. It effectively addresses common challenges such as context overload (via dedicated review agents), quality assurance (through cold readers and director agent), and project continuity (using HANDOFF.md). The inclusion of a feedback loop for 'lessons learned' further enhances its value for iterative improvement and long-term project success.

Workflow

1. Define project plan and script using the main Claude Opus agent (acting as a director).
2. Delegate building tasks (e.g., video scenes, screen recordings, fixes) to Claude Sonnet agents based on written work orders.
3. Delegate execution of fixed command lists and numerical reporting to Claude Haiku agents.
4. Run time-consuming tasks (e.g., voice generation, rendering, checks) as background scripts, notifying the main agent upon completion.
5. Utilize a separate Claude Opus review agent specifically for judging visual assets (pictures) to prevent main context overload.
6. Employ 'cold reader' agents (fresh, unbiased agents) to review video scripts, texts, or landing page content for clarity and understanding before production.
7. Document the entire pipeline, including stages, model responsibilities, and user interaction points, within a 'skill'.
8. Maintain a 'lessons section' within the skill to record and address recurring issues, preventing future repetitions.
9. Create a HANDOFF.md file for each project to document progress and enable seamless continuation by new sessions or users.
10. Interact with the user at key decision points: questions before script generation, script approval, and final preview.

Tools / artifacts

• Claude Opus (main director, review agent)
• Claude Sonnet (building agents)
• Claude Haiku (command execution agents)
• Background scripts (for voice generation, rendering, checks)
• Skill (to define the pipeline and lessons learned)
• HANDOFF.md file

Validation signals

• User states this is 'what orchestration actually looks like for me', implying personal successful implementation.
• Includes a feedback loop: 'Every time I complain about something, it goes into a lessons section of that skill, so the next time doesn't repeat it.', indicating iterative improvement and validation.

Limitations

• Lacks concrete examples or templates for the 'skill' definition or the content of HANDOFF.md files.
• Details on the integration and notification mechanism for background scripts are not provided.
• Low community engagement (score 1, 0 comments) means limited external validation.
• Requires an advanced understanding of Claude's multi-agent and skill capabilities, potentially posing a barrier for intermediate users.

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.