studio-producer — Claude Code plugin: team coordination and sprints
studio-producer is a Claude Code plugin for coordinating teams, allocating resources, and optimizing workflows in 6-day development cycles. It activates for dependencies, resource conflicts, and bottlenecks.
Apache-2.0 ★ 1,013 updated 2026-08-12
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install studio-producer@awesome-claude-code-pluginsWhat studio-producer does
The plugin triggers automatically when team dependencies, resource conflicts, or workflow bottlenecks arise. It coordinates schedules, defines handoffs between designers and engineers, analyzes team capacity, and builds resource allocation plans that balance priorities.
Helps plan new 6-day sprint kickoffs, align team objectives, and remove bottlenecks like overloaded QA processes. No additional configuration files or libraries required.
Listed under Project & Product Management in the marketplace.
What it helps with
- coordinate design and engineering on a single feature
- allocate three high-priority features across two senior engineers
- eliminate a QA process bottleneck
- plan a 6-day cycle kickoff
- align team objectives before a sprint starts
Example prompts for the agent
- Design and engineering need to work together on the creator dashboard — coordinate the teams
- We have three urgent features but only two senior engineers — build an allocation plan
- QA is slowing down releases — analyze the process and suggest how to speed it up
How to install studio-producer
Plugin marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins/plugin install studio-producer@awesome-claude-code-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about studio-producer
How to install studio-producer in Claude Code?
Run /plugin marketplace add ccplugins/awesome-claude-code-plugins, then /plugin install studio-producer@awesome-claude-code-plugins.
What does studio-producer do?
Coordinates multiple teams, allocates resources, and optimizes workflows within 6-day development cycles. Triggers automatically when team dependencies or resource conflicts occur.
When does studio-producer trigger automatically?
When team dependencies arise, resource conflicts occur, or workflow improvements are needed. For example, during sprint planning or when bottlenecks surface in processes.
Source text
studio-producer · Apache-2.0
PROACTIVELY use this agent when coordinating across multiple teams, allocating resources, or optimizing studio workflows. This agent specializes in cross-functional coordination, resource management, and process optimization within the 6-day development cycle. Should be triggered automatically when team dependencies arise, resource conflicts occur, or workflow improvements are needed. Examples:\n\n<example>\nContext: When multiple teams need to collaborate\nuser: "We need the design and engineering teams to work together on the new creator dashboard"\nassistant: "Cross-team collaboration requires careful orchestration. Let me use the studio-producer agent to coordinate schedules, define handoffs, and ensure smooth collaboration between design and engineering."\n<commentary>\nEffective cross-team coordination prevents bottlenecks and ensures aligned delivery.\n</commentary>\n</example>\n\n<example>\nContext: During resource allocation discussions\nuser: "We have three high-priority features but only two senior engineers available"\nassistant: "Resource constraints require strategic allocation. I'll use the studio-producer agent to analyze team capacity and create an optimal resource plan that balances priorities."\n<commentary>\nSmart resource allocation maximizes output while preventing team burnout.\n</commentary>\n</example>\n\n<example>\nContext: When workflow inefficiencies surface\nuser: "The QA process is becoming a bottleneck for releases"\nassistant: "Process bottlenecks kill velocity. Let me use the studio-producer agent to analyze the QA workflow and design improvements that maintain quality while increasing throughput."\n<commentary>\nContinuous workflow optimization is essential for maintaining rapid development cycles.\n</commentary>\n</example>\n\n<example>\nContext: Sprint planning and coordination\nuser: "We're starting a new 6-day cycle next Monday"\nassistant: "New cycles need comprehensive planning. I'll use the studio-producer agent to coordinate sprint kickoffs, align team objectives, and ensure everyone has clear priorities."\n<commentary>\nWell-coordinated sprint starts set the tone for successful 6-day cycles.\n</commentary>\n</example>
© Michael Galpert · Apache-2.0 · ccplugins/awesome-claude-code-plugins