
Live Service Event Pipeline Planner
Generate production calendars, dependency maps, and risk assessments for live service events
What You Can Do
You can generate comprehensive production breakdowns for live service events that map critical dependencies across disciplines, identify bottlenecks before they occur, and establish realistic timelines with contingency buffers. The skill creates actionable calendars that show parallel workflows, handoff points, and resource constraints—enabling producers to communicate complex timelines to stakeholders and catch feasibility issues early in planning cycles.
Features
Creates phase-by-phase timelines with milestones, dependencies, and discipline-specific work streams for 3-6 month event cycles
Identifies critical handoff points, blockers, and parallel workflows showing which teams must complete work before others can proceed
Flags high-risk areas (scope creep, resource conflicts, technical unknowns) with contingency strategies and buffer recommendations
Maps design, engineering, art, QA, and marketing workflows with clear ownership, review cycles, and integration points
Highlights when multiple events compete for shared teams or assets, with alternative scheduling options
Provides feasibility assessment comparing planned event scope against available dev time with trade-off recommendations
Generates reusable production frameworks for seasonal or battle pass cycles to accelerate future planning
Produces timeline summaries and risk dashboards tailored for leadership, design, and engineering audiences
Example Output
Event Production Calendar (12-Week Battle Pass Launch)
Phase 1: Concept & Design (Weeks 1-3)
- Design finalization: Complete reward track, cosmetics, progression curve (Weeks 1-2)
- Engineering feasibility review: Backend infrastructure, progression systems (Week 2)
- Marketing creative brief: Key visuals, messaging pillars (Week 2)
- Dependency: Marketing cannot brief assets until design locks mechanics
Phase 2: Production (Weeks 4-8)
- Art production: 60+ cosmetic assets, UI, animations (Weeks 3-7)
- Engineering: Backend systems, progression logic, reward fulfillment (Weeks 4-8)
- Design iteration: Balance passes, economy tuning (Weeks 5-7)
- QA preparation: Test plan drafting, automation setup (Week 6)
- Critical Path: Art blocking engineering integration—4 week lead time required
Risk Assessment:
- 🔴 HIGH: Cosmetic art delay → cascades to QA, marketing content shoot (Week 6 buffer recommended)
- 🟡 MEDIUM: Economy rebalancing scope creep → recommend design lock by Week 5
- 🟡 MEDIUM: Cross-platform testing → add 1-week QA phase before launch
Resource Conflicts:
- Art team shares 2 animators with concurrent seasonal event (Weeks 5-7) → propose staggered delivery or contractor support
What's Included
- SKILL.md instruction file with event planning methodology:
- Production Calendar Template (Gantt-style breakdown for 3-6 month events):
- Dependency Map Framework (identifies critical paths and handoff points):
- Risk Assessment Checklist (high-risk areas specific to live service):
- Cross-Discipline Workflow Template (maps design, engineering, art, QA, marketing phases):
- Resource Conflict Resolution Worksheet (identifies shared team contention):
Who It's For
- Game Producers managing live service events and seasonal content pipelines
- Live Service Leads coordinating cross-disciplinary teams on time-sensitive launches
- Production Managers tracking dependencies and bottlenecks across game development studios
- Design Directors planning ambitious event scopes and assessing feasibility
- Studio Heads communicating event timelines and risks to leadership and stakeholders
Best For
- Planning seasonal events, battle passes, and limited-time content (3-6 month lead time)
- Identifying critical dependencies and bottlenecks before they become production crises
- Assessing whether ambitious event scopes fit available development bandwidth
- Coordinating multiple concurrent events competing for shared resources
- Building repeatable production templates for recurring event cycles
- Communicating complex timelines and constraints to non-technical stakeholders







