Indie Game Scope Validator
Validate indie game scope against team capacity and timeline before production
What You Can Do
You can objectively evaluate your game design against your specific constraints—team composition, development timeline, and budget—to identify scope risks before they derail your project. Claude analyzes your design document and team capacity using MoSCoW prioritization adapted for indie development, giving you clear recommendations on what to build, defer, or cut. This prevents the most common indie failure: starting with AAA scope on an indie budget.
Features
evaluates developer roles, experience levels, and availability to estimate realistic output velocity
categorizes design elements by implementation effort, asset requirements, and technical risk
sorts features into Must Have, Should Have, Could Have, and Won't Have based on your constraints
estimates realistic delivery dates for different feature sets and flags unrealistic deadlines
maps scope decisions to staffing costs and identifies where cuts reduce expenses most effectively
highlights design areas prone to feature bloat and suggests containment strategies
generates clear justification for scope decisions for team discussions and funder pitches
recommends feature buffers and fallback scopes if risks materialize during development
Example Output
Input: 2D pixel platformer, 5-person team (1 lead, 2 programmers, 1 artist, 1 designer), 18-month timeline, $80k budget
Output:
Scope Assessment: YELLOW FLAG
- Design doc includes 40 unique levels, 12 enemy types, 3 boss variants, dynamic weather system, local co-op, and leaderboards
- Team velocity: ~2-3 polished levels/month with current staffing
- Realistic delivery: 24-30 levels in 18 months, not 40
MoSCoW Prioritization:
- MUST: 16 core levels, 6 enemy types, 2 bosses, core movement mechanics
- SHOULD: 8 additional levels, co-op mode, basic progression system
- COULD: Advanced enemy AI, cosmetic skins, leaderboards
- WON'T: Dynamic weather, procedural generation, platform-specific ports
Timeline Risk: Leaderboards, weather system, and co-op implementation add 4-6 months if built as designed. Recommend deferring to post-launch or cutting entirely.
What's Included
- SKILL.md: Complete scope validation framework and MoSCoW methodology for indie development
- Scope Assessment Template: Structured worksheet for documenting team capacity, timeline, budget, and design elements
- Feature Complexity Matrix: Reference guide for scoring implementation effort, asset requirements, and technical risk
- MoSCoW Prioritization Worksheet: Interactive checklist for categorizing features and generating stakeholder-aligned priority lists
- Risk Register Template: Scope creep vectors and mitigation strategies specific to indie constraints
Who It's For
- Indie game producers managing scope and timelines across small teams
- Game designers preparing design documents with realistic production estimates
- Studio leads pitching projects to publishers or seeking funding with credible scope projections
- Technical leads assessing architectural feasibility and development velocity
- Producers transitioning between projects and recalibrating team capacity estimates
Best For
- Pre-production scope validation before green-lighting a project
- Mid-project scope reassessment when team size or timeline changes
- Feature prioritization disputes requiring data-driven resolution
- Publisher pitch preparation with realistic production timelines
- Post-mortem scope retrospectives to improve future estimation accuracy
You might also like
You can validate your game's scope against concrete constraints like team size, budget, and delivery timeline. The skill maps feature complexity to team velocity, identifies critical dependencies, and helps you make ruthless trade-off decisions to ship a viable product rather than an incomplete overscoped project. You'll get a prioritized feature roadmap with realistic delivery estimates and risk assessments.
by foundups
You systematically extract and synthesize player sentiment across multiple community channels—Discord, Reddit, forums, in-game chat, and social media—to identify patterns, emerging trends, and underlying pain points. Claude then generates targeted engagement strategies rooted in actual player concerns rather than assumptions, helping you diagnose why sentiment shifts occur, segment players by motivation, and craft messaging that resonates with specific player groups to reduce churn and amplify positive word-of-mouth.
by foundups
You can transform game design documents into organized functional test case matrices with clear objectives, preconditions, steps, expected results, and edge case identification. Claude analyzes your feature specifications to identify coverage gaps in existing test suites, revealing untested feature interactions and edge cases that informal testing might miss. This accelerates test planning while ensuring systematic coverage across complex game systems.
by foundups
You can transform raw profiler output into actionable performance reports by identifying exact bottlenecks, quantifying their impact on frame time, and recommending prioritized optimization fixes. This skill helps you compare performance across scenes, quality settings, and hardware platforms while tracking regressions between builds—enabling developers to validate improvements and hit target frame rates (60fps, 120fps, or platform-specific thresholds).
by foundups
You'll architect the emotional journey your trailer tells—structuring narrative strategy that balances marketing messaging with authentic gameplay representation. This skill helps you identify the core emotional hooks, establish thematic consistency across multiple trailer variations, and translate game design pillars into audience-facing marketing language that drives conversion and builds community investment.
by foundups
You can transform raw profiler data from Unity Profiler, Unreal Insights, PIX, or NVIDIA FrameView into structured performance analysis reports. This skill helps you isolate root causes of frame time spikes, distinguish transient dips from systemic issues, and create optimization priority matrices that guide developer focus. You'll generate reproducible test cases and validation metrics that accelerate performance fix implementation.
by foundups
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.
by foundups
You can systematically generate standardized QA test matrices that cover text rendering, font issues, cultural appropriateness, and platform-specific localization failures across dozens of languages and regional variants. The skill produces repeatable testing protocols with structured bug reproduction steps, language-specific test scenarios, and regional variant coverage plans—transforming ad-hoc localization testing into auditable, comprehensive processes that catch issues before player release.
by foundups