Loading
Loading
Claude Code sub-agents for experiments, shipping coordination, and studio production workflows.
written by ForgeCat
Claude Code sub-agents for experiments, shipping coordination, and studio production workflows.
ForgeCatnpx forgecat install @forgecat/contains-studio_agents_project-management
| Agent | Description |
|---|---|
experiment-tracker | PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are introduced. Examples:\n\n\nContext: When implementing feature flags or A/B test variants\nuser: "Add a feature flag to test the new onboarding flow"\nassistant: "I've implemented the feature flag for the onboarding flow A/B test. Let me use the experiment-tracker agent to properly document this experiment and set up tracking."\n\nEvery feature flag represents an experiment that needs proper tracking and success metrics.\n\n\n\n\nContext: After deploying experimental features\nuser: "The new viral sharing feature is now live for 10% of users"\nassistant: "Great! The viral sharing feature is deployed. I'll use the experiment-tracker agent to monitor its performance and document initial results."\n\nLive experiments need immediate tracking setup to capture valuable data from the start.\n\n\n\n\nContext: When reaching experiment milestones\nuser: "It's been a week since we launched the TikTok integration test"\nassistant: "Perfect timing for analysis. Let me use the experiment-tracker agent to compile the week-one results and determine if we should expand the test."\n\nRegular experiment checkpoints ensure data-driven decisions about feature rollouts.\n\n\n\n\nContext: Before making product decisions\nuser: "Should we keep the AI avatar feature or remove it?"\nassistant: "Let me analyze the experiment data to inform this decision. I'll use the experiment-tracker agent to review all metrics and user feedback for the AI avatar feature test."\n\nProduct decisions should be backed by experiment data, not gut feelings.\n\n |
project-shipper | 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\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\nMajor launches need comprehensive coordination across engineering, marketing, and support teams.\n\n\n\n\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\nMultiple concurrent releases need strategic spacing and resource allocation.\n\n\n\n\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\nEvery feature needs a story that connects with users' aspirations and pain points.\n\n\n\n\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\nLaunch success requires active monitoring and quick pivots based on user reception.\n\n |
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\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\nEffective cross-team coordination prevents bottlenecks and ensures aligned delivery.\n\n\n\n\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\nSmart resource allocation maximizes output while preventing team burnout.\n\n\n\n\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\nContinuous workflow optimization is essential for maintaining rapid development cycles.\n\n\n\n\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\nWell-coordinated sprint starts set the tone for successful 6-day cycles.\n\n |
| Field | Value |
|---|---|
| Author | Contains Studio |
| Original repository | https://github.com/contains-studio/agents/tree/main/project-management |
| Version | 0.0.0 |
| Original commit | a5a480c324cac64b9c569bca0b2f297d517240cb |
| License | Unknown |
| Source platform | Claude Code agents |
| Platform | Status |
|---|---|
| Claude Code | Partial |
| Cursor | Partial |
| Codex | Partial |
None
forgecat
View CreatorNone
Evaluated 7/1/2026