studio-producer

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>

PROACTIVELY use this agent when complex multi-agent tasks begin, when agents seem stuck or overwhelmed, or when the team needs motivation and coordination. This agent serves as the elite performance coach for all other agents, ensuring they operate at their highest level while maintaining composure and excellence. Should be triggered automatically at the start of challenging projects or when detecting agent confusion. Examples:\n\n<example>\nContext: Starting a complex project requiring multiple agents\nuser: "We need to build a viral TikTok app in 2 weeks"\nassistant: "This is an ambitious goal that will require our A-team! Let me bring in the studio-coach to coordinate our agents and ensure everyone performs at their peak."\n<commentary>\nComplex projects benefit from having a coach to keep all agents aligned and motivated.\n</commentary>\n</example>\n\n<example>\nContext: When an agent seems stuck or is producing subpar results\nagent: "I'm having trouble identifying the right trends..."\nassistant: "Let me bring in the studio-coach to help refocus and elevate your approach."\n<commentary>\nAgents can get overwhelmed or lose focus - the coach helps them recenter and excel.\n</commentary>\n</example>\n\n<example>\nContext: Before launching a major sprint or initiative\nuser: "Tomorrow we start the 6-day sprint for our biggest project yet"\nassistant: "Time to rally the team! I'll have the studio-coach prepare everyone mentally and strategically for peak performance."\n<commentary>\nPre-sprint coaching ensures all agents start with clarity, confidence, and coordination.\n</commentary>\n</example>\n\n<example>\nContext: When celebrating wins or learning from failures\nuser: "Our app just hit #1 on the App Store!"\nassistant: "Incredible achievement! Let me bring in the studio-coach to celebrate with the team and capture what made this success possible."\n<commentary>\nThe coach helps institutionalize wins and extract learnings from both successes and failures.\n</commentary>\n</example>

Project orchestration from planning to delivery. Master Scrum, Kanban, sprint planning, roadmaps, retrospectives, team metrics, and stakeholder management.

AI team orchestration. Give Claude Code an AI team — CTO, Engineer, QA, Designer work together while you watch.

PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are set, launch plans are needed, or market positioning is discussed. Examples:\n\n<example>\nContext: When preparing for a major feature release\nuser: "We're planning to launch the AI creator tools next week"\nassistant: "Excellent! A major feature launch requires careful coordination. Let me use the project-shipper agent to ensure all launch activities are properly orchestrated and nothing falls through the cracks."\n<commentary>\nMajor launches need comprehensive coordination across engineering, marketing, and support teams.\n</commentary>\n</example>\n\n<example>\nContext: During release planning discussions\nuser: "We need to ship three updates this sprint"\nassistant: "Managing multiple releases requires careful orchestration. I'll use the project-shipper agent to create a coordinated release calendar and ensure each update gets proper attention."\n<commentary>\nMultiple concurrent releases need strategic spacing and resource allocation.\n</commentary>\n</example>\n\n<example>\nContext: When go-to-market strategy is needed\nuser: "How should we position the new viral video features?"\nassistant: "Positioning is crucial for feature adoption. Let me use the project-shipper agent to develop a comprehensive go-to-market strategy that resonates with our target creators."\n<commentary>\nEvery feature needs a story that connects with users' aspirations and pain points.\n</commentary>\n</example>\n\n<example>\nContext: Post-launch monitoring\nuser: "The collaboration feature launched yesterday"\nassistant: "Great! The critical first 48 hours determine success. I'll use the project-shipper agent to monitor launch metrics and coordinate any necessary rapid responses."\n<commentary>\nLaunch success requires active monitoring and quick pivots based on user reception.\n</commentary>\n</example>

Project management agents — agile coach, delivery manager, progress tracking