diff --git a/src/workflows/1-preproduction/research/market-steps/step-01-init.md b/src/workflows/1-preproduction/research/market-steps/step-01-init.md deleted file mode 100644 index cb46f3a..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-01-init.md +++ /dev/null @@ -1,184 +0,0 @@ -# Game Market Research Step 1: Market Research Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate research content in init step -- ✅ ALWAYS confirm understanding of user's research goals -- 📋 YOU ARE A GAME MARKET RESEARCH FACILITATOR, not content generator -- 💬 FOCUS on clarifying scope and approach -- 🔍 NO WEB RESEARCH in init - that's for later steps -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Confirm research understanding before proceeding -- ⚠️ Present [C] continue option after scope clarification -- 💾 Write initial scope document immediately -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from main workflow discovery are available -- Research type = "market" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on game market research scope clarification -- Web search capabilities are enabled for later steps - -## YOUR TASK: - -Initialize game market research by confirming understanding of {{research_topic}} and establishing clear research scope. - -## GAME MARKET RESEARCH INITIALIZATION: - -### 1. Confirm Research Understanding - -**INITIALIZE - DO NOT RESEARCH YET** - -Start with research confirmation: -"I understand you want to conduct **game market research** for **{{research_topic}}** with these goals: {{research_goals}} - -**My Understanding of Your Research Needs:** - -- **Research Topic**: {{research_topic}} -- **Research Goals**: {{research_goals}} -- **Research Type**: Game Market Research -- **Approach**: Comprehensive game market analysis with source verification - -**Game Market Research Areas We'll Cover:** - -- Game market size, genre growth dynamics, and platform trends -- Player insights, behavior patterns, and gamer demographics -- Competitive game landscape and studio positioning -- Strategic recommendations and game design implications - -**Does this accurately capture what you're looking for?**" - -### 2. Refine Research Scope - -Gather any clarifications needed: - -#### Scope Clarification Questions: - -- "Are there specific player segments or platforms for {{research_topic}} we should prioritize?" -- "Should we focus on specific geographic regions or global game market?" -- "Is this for game concept validation, competitor analysis, market entry strategy, or another purpose?" -- "Any specific competing games, studios, or player communities you particularly want analyzed?" - -### 3. Document Initial Scope - -**WRITE IMMEDIATELY TO DOCUMENT** - -Write initial research scope to document: - -```markdown -# Game Market Research: {{research_topic}} - -## Research Initialization - -### Research Understanding Confirmed - -**Topic**: {{research_topic}} -**Goals**: {{research_goals}} -**Research Type**: Game Market Research -**Date**: {{date}} - -### Research Scope - -**Game Market Analysis Focus Areas:** - -- Game market size, genre growth projections, and platform dynamics -- Player segments, behavior patterns, and gamer insights -- Competitive game landscape and studio positioning analysis -- Strategic recommendations and game design implications - -**Research Methodology:** - -- Current web data with source verification -- Multiple independent sources for critical claims -- Confidence level assessment for uncertain data -- Comprehensive coverage with no critical gaps - -### Next Steps - -**Research Workflow:** - -1. ✅ Initialization and scope setting (current step) -2. Player Insights and Behavior Analysis -3. Player Pain Points and Unmet Needs Analysis -4. Player Decision and Purchase Journey Analysis -5. Game Competitive Analysis -6. Research Synthesis and Completion - -**Research Status**: Scope confirmed, ready to proceed with detailed game market analysis -``` - -### 4. Present Confirmation and Continue Option - -Show initial scope document and present continue option: -"I've documented our understanding and initial scope for **{{research_topic}}** game market research. - -**What I've established:** - -- Research topic and goals confirmed -- Game market analysis focus areas defined -- Research methodology verification -- Clear workflow progression - -**Document Status:** Initial scope written to research file for your review - -**Ready to begin detailed game market research?** -[C] Continue - Confirm scope and proceed to player insights analysis -[Modify] Suggest changes to research scope before proceeding - -### 5. Handle User Response - -#### If 'C' (Continue): - -- Update frontmatter: `stepsCompleted: [1]` -- Add confirmation note to document: "Scope confirmed by user on {{date}}" -- Load: `./step-02-customer-behavior.md` - -#### If 'Modify': - -- Gather user changes to scope -- Update document with modifications -- Re-present updated scope for confirmation - -## SUCCESS METRICS: - -✅ Research topic and goals accurately understood -✅ Game market research scope clearly defined -✅ Initial scope document written immediately -✅ User opportunity to review and modify scope -✅ [C] continue option presented and handled correctly -✅ Document properly updated with scope confirmation - -## FAILURE MODES: - -❌ Not confirming understanding of research topic and goals -❌ Generating research content instead of just scope clarification -❌ Not writing initial scope document to file -❌ Not providing opportunity for user to modify scope -❌ Proceeding to next step without user confirmation -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## INITIALIZATION PRINCIPLES: - -This step ensures: - -- Clear mutual understanding of game market research objectives -- Well-defined research scope and approach -- Immediate documentation for user review -- User control over research direction before detailed work begins - -## NEXT STEP: - -After user confirmation and scope finalization, load `./step-02-customer-behavior.md` to begin detailed game market research with player insights analysis. - -Remember: Init steps confirm understanding and scope, not generate research content! diff --git a/src/workflows/1-preproduction/research/market-steps/step-02-customer-behavior.md b/src/workflows/1-preproduction/research/market-steps/step-02-customer-behavior.md deleted file mode 100644 index b23b93f..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-02-customer-behavior.md +++ /dev/null @@ -1,236 +0,0 @@ -# Game Market Research Step 2: Player Behavior and Segments - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A PLAYER BEHAVIOR ANALYST, not content generator -- 💬 FOCUS on player behavior patterns and gamer demographic analysis -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after player behavior content generation -- 📝 WRITE PLAYER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- Focus on player behavior patterns and gamer demographic analysis -- Web search capabilities with source verification are enabled -- Previous step confirmed research scope and goals -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct player behavior and segment analysis with emphasis on gamer patterns, play styles, and demographics. - -## PLAYER BEHAVIOR ANALYSIS SEQUENCE: - -### 1. Begin Player Behavior Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different player behavior areas simultaneously and thoroughly. - -Start with player behavior research approach: -"Now I'll conduct **player behavior analysis** for **{{research_topic}}** to understand player patterns. - -**Player Behavior Focus:** - -- Player behavior patterns, play styles, and preferences -- Gamer demographic profiles and segmentation (age, platform, genre loyalty) -- Psychographic characteristics and gamer values -- Behavior drivers and influences (social, competitive, creative, etc.) -- Player engagement patterns (session length, frequency, community participation) - -**Let me search for current player behavior insights.**" - -### 2. Parallel Player Behavior Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} player behavior patterns play styles" -Search the web: "{{research_topic}} gamer demographics age platform" -Search the web: "{{research_topic}} player psychographic motivation" -Search the web: "{{research_topic}} player engagement session data" - -**Analysis approach:** - -- Look for player behavior studies, game analytics reports, and gamer surveys -- Search for demographic segmentation data (ESA annual reports, GWI gamer data) -- Research player motivation frameworks (Bartle types, Quantic Foundry motivation model) -- Analyze player engagement and session behavior patterns -- Study community participation and social behavior patterns - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate player behavior findings: - -**Research Coverage:** - -- Player behavior patterns and play style preferences -- Gamer demographic profiles and segmentation -- Player motivation and psychographic characteristics -- Player engagement and session behavior patterns - -**Cross-Behavior Analysis:** -[Identify patterns connecting gamer demographics, motivations, and behaviors] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Player Behavior Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare player behavior analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Player Behavior and Segments - -### Player Behavior Patterns - -[Player behavior patterns analysis with source citations] -_Play Style Preferences: [Casual vs hardcore, competitive vs cooperative, etc.]_ -_Session Behavior: [Typical session length, frequency, and engagement patterns]_ -_Content Consumption: [How players engage with game content over time]_ -_Source: [URL]_ - -### Gamer Demographic Segmentation - -[Gamer demographic analysis with source citations] -_Age Demographics: [Age group breakdown and genre/platform preferences]_ -_Platform Distribution: [PC, console, mobile player demographic splits]_ -_Geographic Distribution: [Regional player base and cultural preferences]_ -_Gender Distribution: [Gender demographics for this genre/market]_ -_Source: [URL]_ - -### Player Psychographic Profiles - -[Player psychographic analysis with source citations] -_Player Motivations: [Achievement, social, immersion, creativity, competition drivers]_ -_Gamer Identity: [How players identify with gaming and their genre loyalty]_ -_Spending Attitudes: [Player attitudes toward game purchases and monetization]_ -_Community Engagement: [Player values around online community and social play]_ -_Source: [URL]_ - -### Player Segment Profiles - -[Detailed player segment profiles with source citations] -_Segment 1 - [e.g., Core/Hardcore Players]: [Detailed profile including demographics, motivations, behavior]_ -_Segment 2 - [e.g., Casual/Mainstream Players]: [Detailed profile including demographics, motivations, behavior]_ -_Segment 3 - [e.g., Lapsed/Returning Players]: [Detailed profile including demographics, motivations, behavior]_ -_Source: [URL]_ - -### Behavior Drivers and Influences - -[Player behavior drivers analysis with source citations] -_Social Drivers: [Multiplayer, co-op, and community influences on play behavior]_ -_Competitive Drivers: [Ranked play, leaderboards, and achievement motivation]_ -_Narrative/Immersion Drivers: [Story, world-building, and escapism motivations]_ -_Economic Influences: [Price sensitivity and spending patterns]_ -_Source: [URL]_ - -### Player Engagement and Retention Patterns - -[Player engagement analysis with source citations] -_Discovery and Onboarding: [How players find and start playing games in this space]_ -_Progression and Retention: [What keeps players engaged over weeks and months]_ -_Churn Patterns: [When and why players leave games in this genre]_ -_Return and Re-engagement: [What brings lapsed players back]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **player behavior analysis** for {{research_topic}}, focusing on player patterns and gamer demographics. - -**Key Player Behavior Findings:** - -- Player behavior patterns and play styles clearly identified -- Gamer demographic segmentation thoroughly analyzed -- Player motivations and psychographic profiles mapped -- Player engagement and retention patterns captured -- Multiple sources verified for critical insights - -**Ready to proceed to player pain points?** -[C] Continue - Save this to document and proceed to pain points analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `./step-03-customer-pain-points.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Player behavior patterns identified with current citations -✅ Gamer demographic segmentation thoroughly analyzed -✅ Player motivations and psychographic profiles clearly documented -✅ Player engagement and retention patterns captured -✅ Multiple sources verified for critical insights -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (player pain points) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game player facts - -❌ Missing critical player behavior patterns or play styles -❌ Incomplete gamer demographic segmentation analysis -❌ Missing player motivation and psychographic documentation -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to player pain points analysis step -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## PLAYER BEHAVIOR RESEARCH PROTOCOLS: - -- Research player behavior studies, game analytics reports, and gamer surveys -- Use demographic data from authoritative sources (ESA, GWI, Newzoo) -- Research player motivation frameworks and psychographic profiling -- Analyze player engagement, retention, and session behavior patterns -- Focus on current player behavior data and trends -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## BEHAVIOR ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative game player research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable player insights for game design - -## NEXT STEP: - -After user selects 'C', load `./step-03-customer-pain-points.md` to analyze player pain points, frustrations, and unmet needs for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current player data with rigorous source verification! diff --git a/src/workflows/1-preproduction/research/market-steps/step-03-customer-pain-points.md b/src/workflows/1-preproduction/research/market-steps/step-03-customer-pain-points.md deleted file mode 100644 index 20ff50d..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-03-customer-pain-points.md +++ /dev/null @@ -1,249 +0,0 @@ -# Game Market Research Step 3: Player Pain Points and Needs - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A PLAYER NEEDS ANALYST, not content generator -- 💬 FOCUS on player pain points, frustrations, and unmet game needs -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after pain points content generation -- 📝 WRITE PLAYER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Player behavior analysis completed in previous step -- Focus on player pain points, frustrations, and unmet game needs -- Web search capabilities with source verification are enabled -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct player pain points and needs analysis with emphasis on game frustrations, design failures in the genre, and underserved player needs. - -## PLAYER PAIN POINTS ANALYSIS SEQUENCE: - -### 1. Begin Player Pain Points Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different player pain point areas simultaneously and thoroughly. - -Start with player pain points research approach: -"Now I'll conduct **player pain points analysis** for **{{research_topic}}** to understand player frustrations. - -**Player Pain Points Focus:** - -- Player frustrations with existing games in this space -- Unmet genre needs and underserved game design opportunities -- Onboarding and accessibility barriers -- Monetization frustrations and fairness complaints -- Technical and performance pain points - -**Let me search for current player pain points insights.**" - -### 2. Parallel Pain Points Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} player complaints frustrations reviews" -Search the web: "{{research_topic}} game problems player frustrations forum" -Search the web: "{{research_topic}} unmet player needs design gaps" -Search the web: "{{research_topic}} game barriers to entry accessibility" - -**Analysis approach:** - -- Look for player reviews (Steam, Metacritic, Reddit) and community discussions -- Search for game design criticism and genre critique articles -- Research accessibility and onboarding barrier data -- Analyze monetization complaints and pay-to-win frustrations -- Study technical performance and quality complaints - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate player pain points findings: - -**Research Coverage:** - -- Player frustrations with existing games -- Unmet genre needs and design gaps -- Onboarding and accessibility barriers -- Monetization and fairness complaints - -**Cross-Pain Points Analysis:** -[Identify patterns connecting different types of player pain points] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Player Pain Points Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare player pain points analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Player Pain Points and Needs - -### Player Frustrations with Existing Games - -[Player frustrations analysis with source citations] -_Common Gameplay Frustrations: [Recurring gameplay design complaints in this genre]_ -_Progression Frustrations: [Grind, difficulty spikes, and unfair progression issues]_ -_Technical Frustrations: [Performance, bugs, and stability complaints]_ -_Frequency Analysis: [How often these frustrations appear in player feedback]_ -_Source: [URL]_ - -### Unmet Player Needs and Genre Gaps - -[Unmet needs analysis with source citations] -_Critical Unmet Needs: [Most important underserved player desires]_ -_Genre Design Gaps: [Design opportunities not yet addressed by competitors]_ -_Market Gaps: [Market opportunities from unmet player needs]_ -_Priority Analysis: [Which unmet needs represent the greatest opportunity]_ -_Source: [URL]_ - -### Barriers to Entry and Accessibility - -[Accessibility barriers analysis with source citations] -_Learning Curve Barriers: [Complexity and onboarding hurdles preventing new players]_ -_Hardware and Platform Barriers: [Cost and availability barriers]_ -_Social Barriers: [Multiplayer toxicity, skill gaps, and community exclusion]_ -_Accessibility Barriers: [Visual, motor, and cognitive accessibility gaps]_ -_Source: [URL]_ - -### Monetization Frustrations - -[Monetization pain points analysis with source citations] -_Pay-to-Win Complaints: [Player frustrations with unfair monetization]_ -_Pricing Fairness Issues: [Perceived value vs cost complaints]_ -_Predatory Mechanic Complaints: [Loot box, FOMO, and manipulation criticisms]_ -_Battle Pass and Season Fatigue: [Player burnout from ongoing purchase requirements]_ -_Source: [URL]_ - -### Community and Social Pain Points - -[Community pain points analysis with source citations] -_Toxicity and Harassment: [Negative community behavior and its impact on players]_ -_Matchmaking and Balancing: [Frustrations with unfair matchmaking]_ -_Communication Issues: [Team communication and coordination barriers]_ -_Retention and Community Decay: [Pain points causing community decline]_ -_Source: [URL]_ - -### Emotional Impact Assessment - -[Emotional impact analysis with source citations] -_Player Burnout Patterns: [What causes long-term player disengagement]_ -_Loyalty Risks: [How pain points affect player retention and word of mouth]_ -_Reputation Impact: [How pain points affect studio and game reputation]_ -_Churn Risk: [Risk of player loss from identified pain points]_ -_Source: [URL]_ - -### Pain Point Prioritization - -[Pain point prioritization with source citations] -_High Priority Pain Points: [Most critical pain points to address in game design]_ -_Medium Priority Pain Points: [Important but less critical pain points]_ -_Low Priority Pain Points: [Minor pain points with lower design impact]_ -_GDD Opportunity Mapping: [Pain points with highest game design opportunity]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **player pain points analysis** for {{research_topic}}, focusing on player frustrations and unmet needs. - -**Key Pain Points Findings:** - -- Player frustrations with existing games thoroughly documented -- Unmet genre needs and design gaps clearly identified -- Accessibility and onboarding barriers analyzed -- Monetization frustrations assessed -- Pain points prioritized by game design opportunity - -**Ready to proceed to player decision processes?** -[C] Continue - Save this to document and proceed to decision processes analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `./step-04-customer-decisions.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Player frustrations with existing games clearly documented -✅ Unmet genre needs and design gaps identified -✅ Accessibility and onboarding barriers analyzed -✅ Monetization frustrations assessed -✅ Pain points prioritized by game design opportunity -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (player decisions) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game player facts - -❌ Missing critical player frustrations or genre complaints -❌ Not identifying unmet genre needs or design gaps -❌ Incomplete accessibility and onboarding barrier analysis -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to player decisions analysis step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## PLAYER PAIN POINTS RESEARCH PROTOCOLS: - -- Research player reviews on Steam, Metacritic, Reddit, and game forums -- Use player feedback and community discussion data -- Analyze game design criticism and genre critique articles -- Study barriers to game accessibility and onboarding -- Focus on current player pain point data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## PAIN POINTS ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative game player feedback and research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable pain point insights for game design - -## NEXT STEP: - -After user selects 'C', load `./step-04-customer-decisions.md` to analyze player decision processes, purchase journeys, and game selection factors for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current player pain point data with rigorous source verification! diff --git a/src/workflows/1-preproduction/research/market-steps/step-04-customer-decisions.md b/src/workflows/1-preproduction/research/market-steps/step-04-customer-decisions.md deleted file mode 100644 index 4df2a49..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-04-customer-decisions.md +++ /dev/null @@ -1,259 +0,0 @@ -# Game Market Research Step 4: Player Decisions and Purchase Journey - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A PLAYER DECISION ANALYST, not content generator -- 💬 FOCUS on player decision processes, game selection journey, and purchase factors -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after decision processes content generation -- 📝 WRITE PLAYER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Player behavior and pain points analysis completed in previous steps -- Focus on player decision processes and game selection journey mapping -- Web search capabilities with source verification are enabled -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct player decision processes and game selection journey analysis with emphasis on how players discover, evaluate, and purchase games in this market. - -## PLAYER DECISIONS ANALYSIS SEQUENCE: - -### 1. Begin Player Decisions Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different player decision areas simultaneously and thoroughly. - -Start with player decisions research approach: -"Now I'll conduct **player decision processes analysis** for **{{research_topic}}** to understand game selection and purchase decision-making. - -**Player Decisions Focus:** - -- Game discovery and awareness channels -- Game selection criteria and evaluation process -- Purchase decision factors and price sensitivity -- Storefront and platform selection behavior -- Refund and regret patterns - -**Let me search for current player decision insights.**" - -### 2. Parallel Decisions Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} game discovery how players find games" -Search the web: "{{research_topic}} game purchase decision factors criteria" -Search the web: "{{research_topic}} game selection evaluation process player" -Search the web: "{{research_topic}} game influencer streaming word of mouth purchase" - -**Analysis approach:** - -- Look for player survey data on game discovery and purchase behavior -- Search for storefront analytics and game marketing effectiveness data -- Research influencer and content creator impact on game purchases -- Analyze price sensitivity and sale behavior patterns -- Study refund patterns and buyer's remorse data - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate player decision findings: - -**Research Coverage:** - -- Game discovery and awareness channel analysis -- Game selection criteria and evaluation processes -- Purchase decision factors and pricing dynamics -- Influencer and social proof impact on decisions - -**Cross-Decisions Analysis:** -[Identify patterns connecting discovery channels, evaluation criteria, and purchase factors] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Player Decisions Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare player decisions analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Player Decision Processes and Purchase Journey - -### Game Discovery and Awareness - -[Game discovery analysis with source citations] -_Discovery Channels: [Steam discovery, social media, streaming, word of mouth, advertising]_ -_Awareness Timelines: [How far in advance players become aware of games]_ -_Wishlisting Behavior: [How players track and follow games before release]_ -_Algorithm vs Human Recommendation: [Platform algorithm vs peer recommendation impact]_ -_Source: [URL]_ - -### Game Selection Criteria and Evaluation - -[Game selection analysis with source citations] -_Primary Selection Factors: [Most important criteria in game selection decisions]_ -_Secondary Selection Factors: [Supporting factors influencing game choice]_ -_Trailer and Demo Impact: [How gameplay videos and demos affect selection]_ -_Review and Rating Impact: [How Metacritic, user reviews, and critic reviews affect selection]_ -_Source: [URL]_ - -### Player Purchase Journey Mapping - -[Purchase journey analysis with source citations] -_Awareness Stage: [How players first encounter {{research_topic}} games]_ -_Consideration Stage: [Wishlist, research, and comparison process]_ -_Decision Stage: [Final purchase decision triggers and timing]_ -_Purchase Stage: [Storefront selection, price point, and payment behavior]_ -_Post-Purchase Stage: [Early play, review writing, refund, and community entry]_ -_Source: [URL]_ - -### Influencer and Social Proof Impact - -[Influencer impact analysis with source citations] -_Streaming Influence: [Twitch, YouTube, and content creator impact on game discovery]_ -_Community and Forum Influence: [Reddit, Discord, and gaming forum role in decisions]_ -_Peer Recommendation Influence: [Friend recommendations and social circle impact]_ -_Review Aggregator Influence: [Metacritic, OpenCritic, and Steam review impact]_ -_Source: [URL]_ - -### Pricing and Purchase Behavior - -[Pricing behavior analysis with source citations] -_Price Point Sensitivity: [Player willingness to pay at different price tiers]_ -_Sale and Discount Behavior: [How sales affect purchase timing and volume]_ -_Bundle Purchase Behavior: [How game bundles and package deals drive decisions]_ -_Free-to-Play Conversion: [F2P player conversion rates and spending patterns]_ -_Source: [URL]_ - -### Platform and Storefront Selection - -[Platform selection analysis with source citations] -_Platform Preference Factors: [What drives PC vs console vs mobile choice]_ -_Storefront Preference: [Steam vs Epic vs console store selection factors]_ -_Cross-Platform Considerations: [How cross-play and cross-save affect decisions]_ -_Subscription Service Impact: [Game Pass, PS Plus, and subscription on purchase decisions]_ -_Source: [URL]_ - -### Post-Purchase Behavior and Retention - -[Post-purchase analysis with source citations] -_Early Retention Factors: [What keeps players engaged in the first week]_ -_Long-term Retention Drivers: [Content updates, community, and progression]_ -_Refund and Abandonment Patterns: [When and why players refund or abandon games]_ -_Review and Community Contribution: [How satisfied players contribute reviews and content]_ -_Source: [URL]_ - -### Player Decision Optimizations - -[Decision optimization analysis with source citations] -_Wishlist Conversion Strategies: [Converting wishlists to purchases]_ -_Trust and Credibility Building: [Building player confidence before purchase]_ -_Launch Strategy Timing: [Optimal launch window and marketing timing]_ -_Long-term Player Relationship: [Building sustainable player communities]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **player decision processes analysis** for {{research_topic}}, focusing on game selection and purchase decision-making. - -**Key Decision Findings:** - -- Game discovery channels and awareness mechanisms clearly mapped -- Player selection criteria and evaluation process thoroughly analyzed -- Purchase journey mapped across all stages -- Influencer and social proof impact documented -- Pricing behavior and storefront preferences identified - -**Ready to proceed to competitive analysis?** -[C] Continue - Save this to document and proceed to competitive analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `./step-05-competitive-analysis.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Game discovery channels and awareness mechanisms clearly mapped -✅ Player selection criteria and evaluation process thoroughly analyzed -✅ Purchase journey mapped across all stages -✅ Influencer and social proof impact documented -✅ Pricing behavior and storefront preferences identified -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (competitive analysis) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game player facts - -❌ Missing critical game discovery channel or awareness data -❌ Not identifying key selection criteria or evaluation factors -❌ Incomplete purchase journey mapping -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to competitive analysis step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## PLAYER DECISIONS RESEARCH PROTOCOLS: - -- Research player survey data on game discovery and purchase behavior -- Use storefront analytics and game marketing effectiveness studies -- Analyze influencer and content creator impact on game purchases -- Study price sensitivity and sale behavior patterns -- Focus on current player decision data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## DECISION ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative game player decision research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable decision insights for game marketing and GDD - -## NEXT STEP: - -After user selects 'C', load `./step-05-competitive-analysis.md` to analyze the competitive game landscape, competing studios, and market positioning for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current player decision data with rigorous source verification! diff --git a/src/workflows/1-preproduction/research/market-steps/step-05-competitive-analysis.md b/src/workflows/1-preproduction/research/market-steps/step-05-competitive-analysis.md deleted file mode 100644 index 492d3ad..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-05-competitive-analysis.md +++ /dev/null @@ -1,198 +0,0 @@ -# Game Market Research Step 5: Competitive Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME COMPETITIVE ANALYST, not content generator -- 💬 FOCUS on competitive game landscape and studio market positioning -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after competitive analysis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Focus on competitive game landscape and studio market positioning analysis -- Web search capabilities with source verification are enabled -- May need to search for specific competing game or studio information - -## YOUR TASK: - -Conduct comprehensive competitive analysis of the game market with emphasis on competing titles, studios, and market positioning opportunities. - -## COMPETITIVE ANALYSIS SEQUENCE: - -### 1. Begin Game Competitive Analysis - -Start with competitive research approach: -"Now I'll conduct **competitive analysis** to understand the game competitive landscape. - -**Game Competitive Analysis Focus:** - -- Key competing games and studios -- Competitive market share and player base data -- Studio positioning strategies and differentiation -- Strengths and weaknesses of competing titles -- Market gaps and differentiation opportunities - -**Let me search for current game competitive information.**" - -### 2. Generate Game Competitive Analysis Content - -Prepare competitive analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Competitive Game Landscape - -### Key Competing Games and Studios - -[Competing games analysis with player and revenue data] -_Top Competing Titles: [Most significant competing games with player/revenue data]_ -_Studios Behind Competitors: [Key studios and their market positions]_ -_Source: [URL]_ - -### Market Share and Player Base Analysis - -[Market share and player base analysis with source citations] -_Player Base by Title: [Concurrent players, monthly actives, or download data]_ -_Revenue Distribution: [Revenue share among competing titles]_ -_Platform Distribution: [How competitors are distributed across platforms]_ -_Source: [URL]_ - -### Competitive Positioning and Differentiation - -[Positioning analysis with source citations] -_Unique Selling Points by Title: [What differentiates each major competitor]_ -_Genre Sub-niche Positioning: [How competitors carve out distinct positions]_ -_Positioning Gaps: [Underserved areas where differentiation is possible]_ -_Source: [URL]_ - -### Strengths and Weaknesses of Competitors - -[SWOT-style analysis with source citations] -_Competitor Strengths: [What competing games do particularly well]_ -_Competitor Weaknesses: [Known weaknesses and player complaints about competitors]_ -_Missed Opportunities: [Things competitors have failed to address]_ -_Source: [URL]_ - -### Market Differentiation Opportunities - -[Differentiation analysis with source citations] -_Genre Innovation Opportunities: [Unexplored game design directions]_ -_Underserved Player Segments: [Player groups not well served by current competition]_ -_Technology Differentiation: [Tech advantages that could separate a new title]_ -_Source: [URL]_ - -### Competitive Threats - -[Threats analysis with source citations] -_Established Competitor Threats: [Risks from dominant existing games]_ -_Upcoming Release Threats: [Announced competing games that could affect market entry]_ -_Platform and Publisher Threats: [Platform exclusivity or publisher backing risks]_ -_Source: [URL]_ - -### Opportunities - -[Competitive opportunities analysis with source citations] -_Market Entry Windows: [Timing opportunities for market entry]_ -_Collaboration Opportunities: [Potential partnerships or ecosystem plays]_ -_Platform Opportunity: [Underserved platforms for this genre]_ -_Source: [URL]_ -``` - -### 3. Present Analysis and Complete Option - -Show the generated competitive analysis and present complete option: -"I've completed the **competitive game analysis** for the competitive landscape. - -**Key Competitive Findings:** - -- Key competing games and studios identified with data -- Market share and player base clearly analyzed -- Competitive positioning strategies mapped -- Strengths and weaknesses of competitors thoroughly analyzed -- Market differentiation opportunities identified -- Competitive threats and market entry windows documented - -**Ready to complete the game market research?** -[C] Complete Research - Save final document and conclude - -### 4. Handle Complete Selection - -#### If 'C' (Complete Research): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Complete the game market research workflow - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 2. - -## SUCCESS METRICS: - -✅ Key competing games and studios identified with data -✅ Market share and player base analysis completed with source verification -✅ Competitive positioning strategies clearly mapped -✅ Strengths and weaknesses of competitors thoroughly analyzed -✅ Market differentiation opportunities identified -✅ [C] complete option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Game market research workflow completed successfully - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game market facts - -❌ Missing key competing games or studios -❌ Incomplete market share or player base analysis -❌ Not identifying market differentiation opportunities -❌ Not presenting completion option for research workflow -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPETITIVE RESEARCH PROTOCOLS: - -- Search for game industry reports and competitive intelligence (Newzoo, SuperData, etc.) -- Use SteamSpy, Steam DB, and platform charts for player and revenue data -- Research studio investor reports and developer interviews -- Note competitive advantages and disadvantages for game design -- Search for recent market developments and new game announcements - -## GAME MARKET RESEARCH COMPLETION: - -When 'C' is selected: - -- All game market research steps completed -- Comprehensive game market research document generated -- All sections appended with source citations -- Game market research workflow status updated -- Final recommendations provided to user - -## NEXT STEPS: - -Game market research workflow complete. User may: - -- Use game market research to inform GDD and game design strategies -- Conduct additional competitive research on specific competing games or studios -- Combine game market research with other research types for comprehensive insights - -Congratulations on completing comprehensive game market research! diff --git a/src/workflows/1-preproduction/research/market-steps/step-06-research-completion.md b/src/workflows/1-preproduction/research/market-steps/step-06-research-completion.md deleted file mode 100644 index b521c26..0000000 --- a/src/workflows/1-preproduction/research/market-steps/step-06-research-completion.md +++ /dev/null @@ -1,499 +0,0 @@ -# Game Market Research Step 6: Research Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME MARKET RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on strategic recommendations and actionable game development insights -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after completion content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive game market analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive game market research -- All game market research sections have been completed (player behavior, pain points, decisions, competitive analysis) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete game market research document - -## YOUR TASK: - -Produce a comprehensive, authoritative game market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive game market research. - -## GAME MARKET RESEARCH COMPLETION SEQUENCE: - -### 1. Begin Strategic Synthesis - -Start with strategic synthesis approach: -"Now I'll complete our game market research with **strategic synthesis and recommendations**. - -**Strategic Synthesis Focus:** - -- Integrated insights from game market, player, and competitive analysis -- Strategic recommendations for GDD and game development -- Game market entry or expansion strategies -- Risk assessment and mitigation approaches -- Actionable next steps and implementation guidance for the game studio - -**Let me search for current game market strategic insights and best practices.**" - -### 2. Web Search for Game Market Entry Strategies - -Search for current game market strategies: -Search the web: "game market entry strategies indie studio best practices" - -**Strategy focus:** - -- Game market entry timing and platform selection approaches -- Go-to-market strategies for game launches -- Game positioning and differentiation tactics -- Player acquisition and community growth strategies - -### 3. Web Search for Game Market Risk Assessment - -Search for current game risk approaches: -Search the web: "game development market risk assessment indie studio" - -**Risk focus:** - -- Game market risks and uncertainty management -- Competitive threats and mitigation strategies -- Platform and regulatory risks -- Development cost and scope risks - -### 4. Generate Complete Game Market Research Document - -Prepare comprehensive game market research document with full structure: - -#### Complete Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Game Market Research - -## Executive Summary - -[Brief compelling overview of key game market findings and strategic implications] - -## Table of Contents - -- Game Market Research Introduction and Methodology -- {{research_topic}} Game Market Analysis and Dynamics -- Player Insights and Behavior Analysis -- Player Pain Points and Unmet Needs -- Player Decision and Purchase Journey -- Competitive Game Landscape and Positioning -- Strategic Game Market Recommendations -- Go-to-Market and Launch Strategies -- Risk Assessment and Mitigation -- GDD Implementation Roadmap and Success Metrics -- Future Game Market Outlook and Opportunities -- Game Market Research Methodology and Source Documentation -- Game Market Research Appendices and Additional Resources - -## 1. Game Market Research Introduction and Methodology - -### Game Market Research Significance - -**Compelling game market narrative about why {{research_topic}} research is critical now** -_Market Importance: [Strategic game market significance with current context]_ -_Studio Impact: [Business and creative implications of game market research]_ -_Source: [URL]_ - -### Game Market Research Methodology - -[Comprehensive description of game market research approach including:] - -- **Market Scope**: [Comprehensive game market coverage areas] -- **Data Sources**: [Authoritative game industry sources and verification approach] -- **Analysis Framework**: [Structured game market analysis methodology] -- **Time Period**: [current focus and game market evolution context] -- **Geographic Coverage**: [Regional/global game market scope] - -### Game Market Research Goals and Objectives - -**Original Game Market Goals:** {{research_goals}} - -**Achieved Game Market Objectives:** - -- [Market Goal 1 achievement with supporting evidence] -- [Market Goal 2 achievement with supporting evidence] -- [Additional game market insights discovered during research] - -## 2. {{research_topic}} Game Market Analysis and Dynamics - -### Game Market Size and Growth Projections - -_[Comprehensive game market analysis]_ -_Market Size: [Current game market valuation and size for this domain]_ -_Growth Rate: [CAGR and game market growth projections]_ -_Market Drivers: [Key factors driving game market growth]_ -_Market Segments: [Detailed game market segmentation by platform and genre]_ -_Source: [URL]_ - -### Game Market Trends and Dynamics - -[Current game market trends analysis] -_Emerging Genre Trends: [Key genre innovations and their player reception]_ -_Platform Dynamics: [How platform shifts are changing game market structure]_ -_Monetization Evolution: [Changes in player spending and monetization expectations]_ -_Source: [URL]_ - -### Game Pricing and Business Model Analysis - -[Comprehensive pricing and business model analysis] -_Pricing Strategies: [Current game pricing approaches at different tiers]_ -_Monetization Model Evolution: [Emerging and successful game monetization models]_ -_Player Value Perception: [How players assess value in this market]_ -_Source: [URL]_ - -## 3. Player Insights and Behavior Analysis - -### Player Behavior Patterns - -[Player insights analysis with current context] -_Play Style Patterns: [Key player behavior trends and patterns]_ -_Player Journey: [Complete player discovery-to-retention journey]_ -_Engagement Factors: [Factors driving long-term player engagement]_ -_Source: [URL]_ - -### Player Demographic and Psychographic Profile - -[Comprehensive player profile analysis] -_Gamer Demographics: [Age, platform, geographic distribution]_ -_Player Motivations: [Core motivations driving play behavior]_ -_Player Expectations: [Current player expectations for games in this space]_ -_Source: [URL]_ - -### Player Segmentation and Targeting - -[Detailed player segmentation analysis] -_Player Segments: [Detailed player segment profiles]_ -_Target Segment Analysis: [Most attractive player segments to target]_ -_Segment-specific Design Strategies: [Tailored game design approaches for key segments]_ -_Source: [URL]_ - -## 4. Player Pain Points and Unmet Needs - -### Player Frustrations with Existing Games - -[Comprehensive player pain point analysis] -_Primary Frustrations: [Key player frustrations with competing games]_ -_Genre Design Gaps: [Underserved game design opportunities]_ -_Unmet Player Needs: [Player desires not addressed by current market]_ -_Source: [URL]_ - -## 5. Player Decision and Purchase Journey - -### Game Discovery and Purchase Behavior - -[Player decision analysis with current context] -_Discovery Channels: [How players find games in this space]_ -_Selection Criteria: [What players evaluate before purchasing]_ -_Purchase Journey: [Complete purchase decision mapping]_ -_Source: [URL]_ - -## 6. Competitive Game Landscape and Positioning - -### Competitive Analysis - -[Comprehensive game competitive analysis] -_Market Leaders: [Dominant competing games and their strategies]_ -_Emerging Competitors: [New games and studios entering the space]_ -_Competitive Advantages: [Key differentiators across competing titles]_ -_Source: [URL]_ - -### Game Market Positioning Strategies - -[Strategic game positioning analysis] -_Positioning Opportunities: [Opportunities for game market differentiation]_ -_Competitive Gaps: [Underserved player needs and design opportunities]_ -_GDD Positioning Framework: [Recommended positioning approach for the game concept]_ -_Source: [URL]_ - -## 7. Strategic Game Market Recommendations - -### Game Market Opportunity Assessment - -[Strategic game market opportunities analysis] -_High-Value Opportunities: [Most attractive game market opportunities]_ -_Market Entry Timing: [Optimal timing for game launch]_ -_Growth Strategies: [Recommended approaches for player acquisition and retention]_ -_Source: [URL]_ - -### Strategic GDD Recommendations - -[Comprehensive strategic recommendations for game design] -_Core Game Design Strategy: [Recommended game design direction based on market research]_ -_Competitive Strategy: [Recommended competitive positioning and approach]_ -_Player Acquisition Strategy: [Recommended player acquisition approach]_ -_Source: [URL]_ - -## 8. Go-to-Market and Launch Strategies - -### Game Launch Strategy - -[Comprehensive game go-to-market approach] -_Launch Platform Strategy: [Recommended platform launch sequence and reasoning]_ -_Marketing Channel Strategy: [Optimal channels for game awareness and wishlists]_ -_Community Building Strategy: [Pre-launch community and content creator strategy]_ -_Source: [URL]_ - -### Player Growth and Retention Strategy - -[Game player growth and retention analysis] -_Early Access and Beta Strategy: [Early access as market entry and feedback loop]_ -_Launch Window Optimization: [Launch timing relative to competition]_ -_Live Service and Update Strategy: [Post-launch content and community engagement]_ -_Source: [URL]_ - -## 9. Risk Assessment and Mitigation - -### Game Market Risk Analysis - -[Comprehensive game market risk assessment] -_Market Saturation Risks: [Competitive overcrowding in the genre]_ -_Player Acquisition Risks: [Discoverability and marketing cost risks]_ -_Platform Risks: [Platform policy, algorithm, and exclusivity risks]_ -_Source: [URL]_ - -### Mitigation Strategies - -[Risk mitigation and contingency planning] -_Risk Mitigation Approaches: [Strategies for managing identified game market risks]_ -_Contingency Planning: [Backup plans for market entry challenges]_ -_Market Sensitivity Analysis: [Impact of market changes on game launch strategy]_ -_Source: [URL]_ - -## 10. GDD Implementation Roadmap and Success Metrics - -### Game Development Framework - -[Comprehensive game development guidance from market research] -_Research-Informed Design Priorities: [GDD priorities based on player insights]_ -_Market-Validated Feature Opportunities: [Features backed by market research]_ -_Launch Milestone Planning: [Key milestones informed by market research]_ -_Source: [URL]_ - -### Success Metrics and KPIs - -[Comprehensive game success measurement framework] -_Key Performance Indicators: [Critical game metrics for measuring success]_ -_Player Acquisition Targets: [Launch player base and growth targets]_ -_Retention Benchmarks: [Retention rate targets based on genre norms]_ -_Source: [URL]_ - -## 11. Future Game Market Outlook and Opportunities - -### Future Game Market Trends - -[Forward-looking game market analysis] -_Near-term Market Evolution: [1-2 year genre and platform developments]_ -_Medium-term Market Trends: [3-5 year expected game market developments]_ -_Long-term Market Vision: [5+ year game market outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Strategic Game Market Opportunities - -[Game market opportunity analysis and recommendations] -_Emerging Player Opportunities: [New player segments forming in this space]_ -_Technology Leverage Opportunities: [Tech advantages for future competitive positioning]_ -_Sequel and IP Opportunities: [Long-term franchise and brand building potential]_ -_Source: [URL]_ - -## 12. Game Market Research Methodology and Source Verification - -### Comprehensive Game Market Source Documentation - -[Complete documentation of all game market research sources] -_Primary Game Market Sources: [Key authoritative game industry sources used]_ -_Secondary Game Market Sources: [Supporting game research and analysis]_ -_Game Market Web Search Queries: [Complete list of search queries used]_ - -### Game Market Research Quality Assurance - -[Game market research quality assurance and validation approach] -_Source Verification: [All game market claims verified with multiple sources]_ -_Confidence Levels: [Confidence assessments for uncertain game market data]_ -_Research Limitations: [Game market research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about game market research approach]_ - -## 13. Game Market Research Appendices and Additional Resources - -### Detailed Game Market Data Tables - -[Comprehensive game market data tables supporting research findings] -_Market Size Data: [Detailed game market size and growth data tables]_ -_Player Analysis Data: [Detailed player behavior and segmentation data]_ -_Competitive Analysis Data: [Detailed competing game comparison and positioning data]_ - -### Game Market Resources and References - -[Valuable game market resources for continued research and GDD development] -_Game Market Research Reports: [Authoritative game industry research reports (Newzoo, SuperData)]_ -_Game Industry Associations: [Key game industry organizations (IGDA, ESA, etc.)]_ -_Platform Developer Resources: [Console and storefront developer documentation]_ -_Game Analytics Tools: [Tools and resources for ongoing game market analysis]_ - ---- - -## Game Market Research Conclusion - -### Summary of Key Game Market Findings - -[Comprehensive summary of the most important game market research findings] - -### Strategic Game Development Impact Assessment - -[Assessment of game market implications for {{research_topic}}] - -### Next Steps GDD Recommendations - -[Specific next steps for leveraging this game market research in GDD development] - ---- - -**Game Market Research Completion Date:** {{date}} -**Research Period:** Current comprehensive game market analysis -**Document Length:** As needed for comprehensive game market coverage -**Source Verification:** All game market facts cited with current sources -**Game Market Confidence Level:** High - based on multiple authoritative game industry sources - -_This comprehensive game market research document serves as an authoritative game market reference on {{research_topic}} and provides strategic game market insights for informed GDD and game development decision-making._ -``` - -### 5. Present Complete Game Market Research Document and Final Option - -**Game Market Research Document Completion Presentation:** - -"I've completed the **comprehensive game market research document synthesis** for **{{research_topic}}**, producing an authoritative game market research document with: - -**Document Features:** - -- **Compelling Game Market Introduction**: Engaging opening that establishes game market research significance -- **Comprehensive Game Market TOC**: Complete navigation structure for game market reference -- **Exhaustive Game Market Research Coverage**: All game market aspects of {{research_topic}} thoroughly analyzed -- **Executive Game Market Summary**: Key game market findings and GDD-relevant strategic implications highlighted -- **Strategic GDD Recommendations**: Actionable game market insights for game design and development -- **Complete Game Market Source Citations**: Every game market claim verified with current sources - -**Game Market Research Completeness:** - -- Game market analysis and dynamics fully documented -- Player insights and behavior analysis comprehensively covered -- Competitive game landscape and positioning detailed -- Strategic game market recommendations and GDD guidance provided - -**Document Standards Met:** - -- Exhaustive game market research with no critical gaps -- Professional game market structure and compelling narrative -- As long as needed for comprehensive game market coverage -- Multiple independent sources for all game market claims -- Current game market data throughout with proper citations - -**Ready to complete this comprehensive game market research document?** -[C] Complete Research - Save final comprehensive game market research document - -### 6. Handle Complete Selection - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]` -- Complete the game market research workflow - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 4. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling game market introduction with research significance -✅ Comprehensive game market table of contents with complete document structure -✅ Exhaustive game market research coverage across all game market aspects -✅ Executive game market summary with key findings and GDD-relevant strategic implications -✅ Strategic GDD recommendations grounded in comprehensive game market research -✅ Complete game market source verification with current citations -✅ Professional game market document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Game market research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling game market introduction -❌ Missing comprehensive game market table of contents -❌ Incomplete game market research coverage across game market aspects -❌ Not providing executive game market summary with key GDD-relevant findings -❌ Missing strategic GDD recommendations based on game market research -❌ Relying solely on training data without web verification for current game facts -❌ Producing game market document without professional structure -❌ Not presenting completion option for final game market document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## STRATEGIC GAME RESEARCH PROTOCOLS: - -- Search for current game market strategy frameworks and studio best practices -- Research successful game market entry cases and launch approaches -- Identify game market risk management methodologies and frameworks -- Research game launch planning and execution strategies -- Consider game market timing and readiness factors - -## COMPREHENSIVE GAME MARKET DOCUMENT STANDARDS: - -This step ensures the final game market research document: - -- Serves as an authoritative game market reference on {{research_topic}} -- Provides strategic game market insights for informed GDD decision-making -- Includes comprehensive game market coverage with no gaps -- Maintains rigorous game market source verification standards -- Delivers strategic game insights and actionable GDD recommendations -- Meets professional game market research document quality standards - -## GAME MARKET RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All game market research steps completed (1-6) -- Comprehensive game market research document generated -- Professional game market document structure with intro, TOC, and summary -- All game market sections appended with source citations -- Game market research workflow status updated to complete -- Final comprehensive game market research document delivered to user - -## FINAL GAME MARKET DELIVERABLE: - -Complete authoritative game market research document on {{research_topic}} that: - -- Establishes professional game market credibility through comprehensive research -- Provides strategic game market insights for informed GDD decision-making -- Serves as game market reference document for continued studio use -- Maintains highest game market research quality standards with current verification - -## NEXT STEPS: - -Comprehensive game market research workflow complete. User may: - -- Use game market research document to inform GDD and game design strategies -- Conduct additional game market research on specific player segments or opportunities -- Combine game market research with other research types for comprehensive insights -- Move forward with GDD development based on strategic game market recommendations - -Congratulations on completing comprehensive game market research with professional documentation! diff --git a/src/workflows/1-preproduction/research/research.template.md b/src/workflows/1-preproduction/research/research.template.md deleted file mode 100644 index 1d99524..0000000 --- a/src/workflows/1-preproduction/research/research.template.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -workflowType: 'research' -lastStep: 1 -research_type: '{{research_type}}' -research_topic: '{{research_topic}}' -research_goals: '{{research_goals}}' -user_name: '{{user_name}}' -date: '{{date}}' -web_research_enabled: true -source_verification: true ---- - -# Research Report: {{research_type}} - -**Date:** {{date}} -**Author:** {{user_name}} -**Research Type:** {{research_type}} - ---- - -## Research Overview - -[Research overview and methodology will be appended here] - ---- - - diff --git a/src/workflows/1-preproduction/research/technical-steps/step-01-init.md b/src/workflows/1-preproduction/research/technical-steps/step-01-init.md deleted file mode 100644 index fc10d84..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-01-init.md +++ /dev/null @@ -1,137 +0,0 @@ -# Game Technical Research Step 1: Technical Research Scope Confirmation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user confirmation - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ FOCUS EXCLUSIVELY on confirming game technical research scope and approach -- 📋 YOU ARE A GAME TECHNICAL RESEARCH PLANNER, not content generator -- 💬 ACKNOWLEDGE and CONFIRM understanding of game technical research goals -- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present [C] continue option after scope confirmation -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Research type = "technical" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on game technical architecture and implementation research -- Web search is required to verify and supplement your knowledge with current facts - -## YOUR TASK: - -Confirm game technical research scope and approach for **{{research_topic}}** with the user's goals in mind. - -## GAME TECHNICAL SCOPE CONFIRMATION: - -### 1. Begin Scope Confirmation - -Start with game technical scope understanding: -"I understand you want to conduct **game technical research** for **{{research_topic}}** with these goals: {{research_goals}} - -**Game Technical Research Scope:** - -- **Engine and Framework Analysis**: Game engine selection, rendering pipelines, and architecture decisions -- **Implementation Approaches**: Game loop design, entity-component systems, coding patterns, and best practices -- **Technology Stack**: Languages, game engines, middleware, tools, and platforms relevant to {{research_topic}} -- **Integration Patterns**: Online services, platform APIs, analytics, and system interoperability -- **Performance Considerations**: Frame rate targets, optimization strategies, and platform-specific constraints - -**Research Approach:** - -- Current web data with rigorous source verification -- Multi-source validation for critical game technical claims -- Confidence levels for uncertain game technical information -- Comprehensive game technical coverage with game-architecture-specific insights - -### 2. Scope Confirmation - -Present clear scope confirmation: -"**Game Technical Research Scope Confirmation:** - -For **{{research_topic}}**, I will research: - -✅ **Engine and Framework Analysis** - game engine selection, rendering architecture, tooling -✅ **Implementation Approaches** - game loop, ECS, coding patterns, development workflow -✅ **Technology Stack** - languages, engines, middleware, tools, platforms -✅ **Integration Patterns** - online services, platform APIs, analytics, interoperability -✅ **Performance Considerations** - frame rate, optimization, platform-specific constraints - -**All claims verified against current public sources.** - -**Does this game technical research scope and approach align with your goals?** -[C] Continue - Begin game technical research with this scope - -### 3. Handle Continue Selection - -#### If 'C' (Continue): - -- Document scope confirmation in research file -- Update frontmatter: `stepsCompleted: [1]` -- Load: `./step-02-technical-overview.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append scope confirmation: - -```markdown -## Game Technical Research Scope Confirmation - -**Research Topic:** {{research_topic}} -**Research Goals:** {{research_goals}} - -**Game Technical Research Scope:** - -- Engine and Framework Analysis - game engine selection, rendering architecture, tooling -- Implementation Approaches - game loop, ECS, coding patterns, development workflow -- Technology Stack - languages, engines, middleware, tools, platforms -- Integration Patterns - online services, platform APIs, analytics, interoperability -- Performance Considerations - frame rate, optimization, platform-specific constraints - -**Research Methodology:** - -- Current web data with rigorous source verification -- Multi-source validation for critical game technical claims -- Confidence level framework for uncertain information -- Comprehensive game technical coverage with game-architecture-specific insights - -**Scope Confirmed:** {{date}} -``` - -## SUCCESS METRICS: - -✅ Game technical research scope clearly confirmed with user -✅ All game technical analysis areas identified and explained -✅ Research methodology emphasized -✅ [C] continue option presented and handled correctly -✅ Scope confirmation documented when user proceeds -✅ Proper routing to next game technical research step - -## FAILURE MODES: - -❌ Not clearly confirming game technical research scope with user -❌ Missing critical game technical analysis areas (engine, performance, platform APIs) -❌ Not explaining that web search is required for current game tech facts -❌ Not presenting [C] continue option -❌ Proceeding without user scope confirmation -❌ Not routing to next game technical research step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C', load `./step-02-technical-overview.md` to begin game technology stack analysis. - -Remember: This is SCOPE CONFIRMATION ONLY - no actual game technical research yet, just confirming the research approach and scope! diff --git a/src/workflows/1-preproduction/research/technical-steps/step-02-technical-overview.md b/src/workflows/1-preproduction/research/technical-steps/step-02-technical-overview.md deleted file mode 100644 index b5c1013..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-02-technical-overview.md +++ /dev/null @@ -1,239 +0,0 @@ -# Game Technical Research Step 2: Game Technology Stack Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME TECHNOLOGY STACK ANALYST, not content generator -- 💬 FOCUS on game engines, languages, middleware, tools, and platforms -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after technology stack content generation -- 📝 WRITE GAME TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on game engines, languages, middleware, tools, and platforms -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct game technology stack analysis focusing on game engines, programming languages, middleware, tools, and platforms. Search the web to verify and supplement current facts. - -## GAME TECHNOLOGY STACK ANALYSIS SEQUENCE: - -### 1. Begin Game Technology Stack Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different game technology stack areas simultaneously and thoroughly. - -Start with game technology stack research approach: -"Now I'll conduct **game technology stack analysis** for **{{research_topic}}** to understand the game technology landscape. - -**Game Technology Stack Focus:** - -- Game engines and their evolution (Unreal, Unity, Godot, proprietary) -- Programming languages and scripting (C++, C#, GDScript, Lua, Blueprint) -- Middleware and specialized game tech (physics, audio, animation, networking) -- Game development tools and pipelines (IDEs, profilers, asset pipelines) -- Target platform SDKs and deployment infrastructure - -**Let me search for current game technology stack insights.**" - -### 2. Parallel Game Technology Stack Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} game engine technology comparison" -Search the web: "{{research_topic}} game development tools middleware" -Search the web: "{{research_topic}} game audio physics networking solutions" -Search the web: "{{research_topic}} game platform SDK deployment" - -**Analysis approach:** - -- Look for recent game developer surveys (Unity/Unreal state of game dev, GDC surveys) -- Search for game engine documentation, feature comparisons, and licensing details -- Research middleware and specialized tech choices in comparable games -- Analyze game development tool ecosystems and their evolution -- Study platform SDK requirements and deployment considerations - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate game technology stack findings: - -**Research Coverage:** - -- Game engine and rendering framework analysis -- Programming language and scripting evaluation -- Middleware and specialized game tech assessment -- Game development tools and pipeline analysis - -**Cross-Technology Analysis:** -[Identify patterns connecting engine choices, language decisions, and platform requirements] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Game Technology Stack Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare game technology stack analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Game Technology Stack Analysis - -### Game Engines and Rendering Frameworks - -[Game engine analysis with source citations] -_Dominant Game Engines: [Unreal, Unity, Godot, proprietary engines and their use cases]_ -_Engine Feature Comparison: [Key differentiators relevant to {{research_topic}}]_ -_Engine Licensing Models: [Cost, royalties, and commercial terms]_ -_Engine Community and Support: [Ecosystem maturity and learning resources]_ -_Source: [URL]_ - -### Programming Languages and Scripting - -[Game programming language analysis with source citations] -_Primary Languages: [C++, C#, GDScript, and other languages for {{research_topic}}]_ -_Scripting Solutions: [Blueprint, Lua, Python, and visual scripting approaches]_ -_Language Performance Characteristics: [Performance and suitability for this game type]_ -_Language Ecosystem: [Library availability and developer community]_ -_Source: [URL]_ - -### Middleware and Specialized Game Tech - -[Game middleware analysis with source citations] -_Physics Engines: [PhysX, Havok, Bullet, Jolt and physics middleware options]_ -_Audio Middleware: [FMOD, Wwise, and audio system options]_ -_Animation Systems: [Mixamo, Motion Matching, and animation middleware]_ -_Networking Middleware: [Photon, Mirror, ENet, and networking solutions]_ -_Source: [URL]_ - -### Game Development Tools and Pipeline - -[Game development tools analysis with source citations] -_IDEs and Editors: [Development environments for game programming]_ -_Profiling and Debugging: [RenderDoc, PIX, engine profilers, and performance tools]_ -_Asset Pipeline Tools: [DCC tools, asset optimization, and pipeline automation]_ -_Version Control for Game Teams: [Git LFS, Perforce, and game-specific VCS considerations]_ -_Source: [URL]_ - -### Platform SDKs and Deployment Infrastructure - -[Platform deployment analysis with source citations] -_Console Platform SDKs: [PlayStation, Xbox, Nintendo SDK requirements and features]_ -_PC Platform Integration: [Steam, Epic, GOG SDK features and integration requirements]_ -_Mobile Platform SDKs: [iOS and Android SDK features relevant to this game type]_ -_Cloud and Streaming Infrastructure: [Backend services for online game features]_ -_Source: [URL]_ - -### Game Technology Adoption Trends - -[Game tech adoption trends analysis with source citations] -_Engine Market Share Trends: [How developer adoption of engines is shifting]_ -_Emerging Game Technologies: [New tools and technologies gaining traction in game dev]_ -_Legacy Tech Deprecation: [Older game tech being phased out]_ -_Community Trends: [Developer preferences and open-source adoption in game dev]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **game technology stack analysis** of the technology landscape for {{research_topic}}. - -**Key Game Technology Stack Findings:** - -- Game engines and rendering frameworks thoroughly analyzed -- Programming languages and scripting options evaluated -- Middleware and specialized game tech documented -- Game development tools and pipeline options mapped -- Platform SDK and deployment infrastructure requirements identified - -**Ready to proceed to game integration patterns analysis?** -[C] Continue - Save this to document and proceed to integration patterns - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `./step-03-integration-patterns.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Game engines and rendering frameworks thoroughly analyzed -✅ Programming languages and scripting options evaluated -✅ Middleware and specialized game tech documented -✅ Game development tools and pipeline options mapped -✅ Platform SDK and deployment infrastructure identified -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (integration patterns) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game tech facts - -❌ Missing critical game engines or rendering frameworks -❌ Incomplete middleware or platform SDK analysis -❌ Not identifying game development tools and pipeline options -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to integration patterns step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## GAME TECHNOLOGY STACK RESEARCH PROTOCOLS: - -- Research game developer surveys and state-of-the-industry reports -- Use game engine documentation, feature comparisons, and community forums -- Analyze middleware provider documentation and game use cases -- Study game development tool ecosystems and pipeline examples -- Focus on current game technology data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## GAME TECHNOLOGY STACK ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative game technology research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable game technology insights - -## NEXT STEP: - -After user selects 'C', load `./step-03-integration-patterns.md` to analyze online service integration, platform APIs, analytics, and game system interoperability for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current game technology data with rigorous source verification! diff --git a/src/workflows/1-preproduction/research/technical-steps/step-03-integration-patterns.md b/src/workflows/1-preproduction/research/technical-steps/step-03-integration-patterns.md deleted file mode 100644 index e81b583..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-03-integration-patterns.md +++ /dev/null @@ -1,248 +0,0 @@ -# Game Technical Research Step 3: Game Integration Patterns - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME INTEGRATION ANALYST, not content generator -- 💬 FOCUS on online services, platform APIs, analytics, and game system interoperability -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after integration patterns content generation -- 📝 WRITE GAME INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on online services, platform APIs, analytics, and game system interoperability -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct game integration patterns analysis focusing on online services, platform APIs, game backend systems, and system interoperability. Search the web to verify and supplement current facts. - -## GAME INTEGRATION PATTERNS ANALYSIS SEQUENCE: - -### 1. Begin Game Integration Patterns Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different game integration areas simultaneously and thoroughly. - -Start with game integration patterns research approach: -"Now I'll conduct **game integration patterns analysis** for **{{research_topic}}** to understand game system integration approaches. - -**Game Integration Patterns Focus:** - -- Online multiplayer and networking service integration -- Platform achievement, leaderboard, and social API integration -- Game analytics and telemetry systems -- Live service backend and game operations infrastructure -- Anti-cheat and fair play enforcement integration - -**Let me search for current game integration patterns insights.**" - -### 2. Parallel Game Integration Patterns Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} game online services multiplayer backend" -Search the web: "{{research_topic}} platform API achievements leaderboards integration" -Search the web: "{{research_topic}} game analytics telemetry live operations" -Search the web: "{{research_topic}} game anti-cheat security integration" - -**Analysis approach:** - -- Look for game backend service documentation (PlayFab, GameSparks, Nakama, etc.) -- Search for platform SDK documentation (Steam API, PSN SDK, Xbox Live, etc.) -- Research game analytics platform documentation and best practices -- Analyze live service operations infrastructure patterns -- Study anti-cheat and security integration approaches - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate game integration patterns findings: - -**Research Coverage:** - -- Online services and multiplayer backend analysis -- Platform API and achievement system integration -- Game analytics and telemetry patterns -- Live service operations and anti-cheat integration - -**Cross-Integration Analysis:** -[Identify patterns connecting backend service choices, platform APIs, and analytics systems] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Game Integration Patterns Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare game integration patterns analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Game Integration Patterns Analysis - -### Online Multiplayer and Backend Services - -[Online service analysis with source citations] -_Dedicated Server Solutions: [Server hosting options for multiplayer games]_ -_Game Backend Platforms: [PlayFab, Nakama, Heroic Labs, and similar BaaS for games]_ -_Matchmaking Services: [Matchmaking algorithms and service options]_ -_Real-time Communication: [WebSocket, UDP, and game networking protocols]_ -_Source: [URL]_ - -### Platform API Integration - -[Platform API analysis with source citations] -_Steam API Integration: [Steamworks features - achievements, leaderboards, DLC, etc.]_ -_Console Platform APIs: [PlayStation Network, Xbox Live, Nintendo Online features]_ -_Mobile Platform Integration: [GameCenter, Google Play Games services]_ -_Cross-Platform Identity: [Cross-platform account linking and progression]_ -_Source: [URL]_ - -### Game Analytics and Telemetry - -[Game analytics analysis with source citations] -_In-Game Analytics Platforms: [Unity Analytics, GameAnalytics, Amplitude for games]_ -_Player Behavior Telemetry: [Event tracking patterns for game design insights]_ -_Performance Telemetry: [Frame rate, crash, and performance data collection]_ -_Monetization Analytics: [Revenue tracking, funnel analysis, and LTV modeling]_ -_Source: [URL]_ - -### Live Service Operations Infrastructure - -[Live service analysis with source citations] -_Content Delivery and Updates: [Patching systems, hot fix infrastructure, CDN for games]_ -_Live Event Systems: [Seasonal events, battle passes, and timed content delivery]_ -_Player Support Integration: [In-game support ticketing and reporting systems]_ -_Remote Configuration: [Feature flags, balance adjustment, and live tuning]_ -_Source: [URL]_ - -### Anti-Cheat and Security Integration - -[Security patterns analysis with source citations] -_Anti-Cheat Solutions: [Easy Anti-Cheat, BattlEye, Valve Anti-Cheat patterns]_ -_Server-Side Validation: [Server authority patterns for competitive games]_ -_Player Reporting Systems: [Community-powered moderation integration]_ -_Data Security Patterns: [Secure game save, progress, and transaction handling]_ -_Source: [URL]_ - -### Game Economy and Monetization Integration - -[Monetization integration analysis with source citations] -_In-App Purchase Systems: [Platform IAP APIs and receipt validation]_ -_Virtual Currency Systems: [Soft currency, premium currency, and economy management]_ -_Loot Box and Gacha Systems: [Random reward system implementation patterns]_ -_Battle Pass Implementation: [Seasonal progression and reward system patterns]_ -_Source: [URL]_ - -### Integration Security Patterns - -[Game security patterns analysis with source citations] -_OAuth and Game Authentication: [Player authentication and account security]_ -_API Key Management: [Secure backend API access and key rotation for game services]_ -_Player Data Privacy: [GDPR, COPPA-compliant player data handling patterns]_ -_Data Encryption: [Secure game save and transaction data handling]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **game integration patterns analysis** of system integration approaches for {{research_topic}}. - -**Key Game Integration Patterns Findings:** - -- Online multiplayer and backend service options thoroughly analyzed -- Platform API and achievement system integration evaluated -- Game analytics and telemetry patterns documented -- Live service operations infrastructure mapped -- Anti-cheat and security integration strategies identified - -**Ready to proceed to game architectural patterns analysis?** -[C] Continue - Save this to document and proceed to architectural patterns - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `./step-04-architectural-patterns.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Online multiplayer and backend service options thoroughly analyzed -✅ Platform API and achievement system integration evaluated -✅ Game analytics and telemetry patterns documented -✅ Live service operations infrastructure mapped -✅ Anti-cheat and security integration strategies identified -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (architectural patterns) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game tech facts - -❌ Missing critical online service or backend patterns -❌ Incomplete platform API or analytics integration analysis -❌ Not identifying anti-cheat or security integration approaches -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to architectural patterns step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## GAME INTEGRATION PATTERNS RESEARCH PROTOCOLS: - -- Research game backend service documentation and best practice guides -- Use platform SDK documentation as primary source for platform API details -- Analyze live service game case studies and post-mortems -- Study anti-cheat and security integration patterns from GDC talks -- Focus on current game integration data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## GAME INTEGRATION PATTERNS ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative game integration research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable game integration insights - -## NEXT STEP: - -After user selects 'C', load `./step-04-architectural-patterns.md` to analyze game architectural patterns, engine design decisions, and system structures for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current game integration data with rigorous source verification! diff --git a/src/workflows/1-preproduction/research/technical-steps/step-04-architectural-patterns.md b/src/workflows/1-preproduction/research/technical-steps/step-04-architectural-patterns.md deleted file mode 100644 index 7ef81ac..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-04-architectural-patterns.md +++ /dev/null @@ -1,230 +0,0 @@ -# Game Technical Research Step 4: Game Architectural Patterns - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME SYSTEMS ARCHITECT, not content generator -- 💬 FOCUS on game architectural patterns and engine design decisions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after architectural patterns content generation -- 📝 WRITE GAME ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on game architectural patterns and engine design decisions -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct comprehensive game architectural patterns analysis with emphasis on game engine architecture, ECS patterns, rendering pipelines, and system design decisions for {{research_topic}}. - -## GAME ARCHITECTURAL PATTERNS SEQUENCE: - -### 1. Begin Game Architectural Patterns Analysis - -Start with game architectural research approach: -"Now I'll focus on **game architectural patterns and design decisions** for effective game architecture approaches for {{research_topic}}. - -**Game Architectural Patterns Focus:** - -- Game engine architecture patterns and their trade-offs (ECS, OOP, data-oriented design) -- Game loop design and update pipeline patterns -- Rendering architecture and graphics pipeline design -- Game world and level streaming architecture -- Multiplayer and network architecture patterns - -**Let me search for current game architectural patterns and approaches.**" - -### 2. Web Search for Game Architecture Patterns - -Search for current game architecture patterns: -Search the web: "game architecture patterns ECS entity component system" - -**Game architecture focus:** - -- Entity-Component-System vs Object-Oriented game architecture -- Data-oriented design for game performance -- Event-driven game architecture patterns -- Game state management and game loop design - -### 3. Web Search for Game Engine Design Principles - -Search for current game engine design principles: -Search the web: "game engine design patterns best practices" - -**Game engine design focus:** - -- Game loop patterns and fixed vs variable timestep -- Asset management and resource streaming -- Scene graph and spatial partitioning structures -- Cross-platform abstraction layer patterns - -### 4. Web Search for Game Rendering and Performance Architecture - -Search for current game rendering approaches: -Search the web: "game rendering architecture pipeline performance optimization" - -**Game rendering and performance focus:** - -- Forward vs deferred rendering pipeline choices -- LOD and culling architecture for performance -- GPU optimization and draw call batching -- Frame rate stability and performance budget design - -### 5. Generate Game Architectural Patterns Content - -Prepare game architectural analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Game Architectural Patterns and Design - -### Game Engine Architecture Patterns - -[Game engine architecture patterns analysis with source citations] -_Entity-Component-System (ECS): [ECS architecture benefits, trade-offs, and implementations]_ -_Object-Oriented Game Design: [Traditional OOP patterns and their game-specific variations]_ -_Data-Oriented Design: [Cache-friendly, performance-first architecture approaches]_ -_Hybrid Approaches: [Combining architectural styles for practical game development]_ -_Source: [URL]_ - -### Game Loop and Update Patterns - -[Game loop design analysis with source citations] -_Fixed Timestep Patterns: [Fixed update, variable render for deterministic simulation]_ -_Variable Timestep Patterns: [Delta time approaches and their trade-offs]_ -_Multi-threaded Game Loop: [Parallel processing architecture for modern CPUs]_ -_Input and Event Processing: [Input system architecture and event dispatch patterns]_ -_Source: [URL]_ - -### Rendering Architecture and Graphics Pipeline - -[Rendering architecture analysis with source citations] -_Forward vs Deferred Rendering: [Pipeline choice trade-offs for this game type]_ -_Physically-Based Rendering: [PBR material system architecture]_ -_LOD and Visibility Systems: [Level of detail and culling architecture patterns]_ -_Post-Processing Pipeline: [Screen-space effect and post-processing architecture]_ -_Source: [URL]_ - -### Game World and Level Architecture - -[Game world architecture analysis with source citations] -_Scene Graph Design: [Hierarchical scene representation and management]_ -_Level Streaming Architecture: [Open world and seamless loading patterns]_ -_Spatial Partitioning: [Octree, BVH, and spatial structure choices for {{research_topic}}]_ -_Procedural Generation Architecture: [Systems for procedural world and content generation]_ -_Source: [URL]_ - -### Multiplayer and Network Architecture - -[Multiplayer architecture analysis with source citations] -_Client-Server Architecture: [Authoritative server patterns for online games]_ -_Peer-to-Peer Architecture: [P2P networking and its trade-offs for this game type]_ -_State Synchronization: [Snapshot interpolation, delta compression, rollback netcode]_ -_Lag Compensation Architecture: [Server-side rewind and prediction correction patterns]_ -_Source: [URL]_ - -### Game Data and Save Architecture - -[Game data architecture analysis with source citations] -_Save System Design: [Local save, cloud save, and cross-platform progression patterns]_ -_Configuration and Scripting: [Data-driven design and scriptable object patterns]_ -_Localization Architecture: [Multi-language and regional content management]_ -_Mod Support Architecture: [Moddability and user-generated content systems]_ -_Source: [URL]_ - -### Performance and Scalability Architecture - -[Performance architecture analysis with source citations] -_Memory Budget Design: [Memory allocation strategies for target platforms]_ -_CPU Performance Patterns: [Job systems, coroutines, and threading for game tasks]_ -_GPU Performance Optimization: [Draw call batching, instancing, and shader optimization]_ -_Platform-Specific Optimization: [Console, PC, and mobile performance architecture]_ -_Source: [URL]_ -``` - -### 6. Present Analysis and Continue Option - -Show the generated game architectural patterns and present continue option: -"I've completed the **game architectural patterns analysis** for effective game architecture approaches. - -**Key Game Architectural Findings:** - -- Game engine architecture patterns and trade-offs clearly mapped -- Game loop and update pipeline design thoroughly documented -- Rendering architecture and graphics pipeline patterns identified -- Game world and level architecture analyzed -- Multiplayer network architecture and performance patterns captured - -**Ready to proceed to game implementation research?** -[C] Continue - Save this to the document and move to implementation research - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `./step-05-implementation-research.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 5. - -## SUCCESS METRICS: - -✅ Game engine architecture patterns identified with current citations -✅ Game loop and update pipeline design clearly documented -✅ Rendering architecture and graphics pipeline patterns thoroughly mapped -✅ Game world and level architecture analyzed -✅ Multiplayer network and performance architecture captured -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Proper routing to game implementation research step - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game architecture facts - -❌ Missing critical game engine architecture patterns -❌ Not analyzing game loop design trade-offs -❌ Incomplete rendering or network architecture analysis -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## GAME ARCHITECTURAL RESEARCH PROTOCOLS: - -- Search for game architecture documentation, GDC talks, and game engine documentation -- Use game developer blog posts and post-mortems for architecture case studies -- Research game engine source code patterns and community architecture discussions -- Note architectural decision rationales (ADRs) from game post-mortems -- Research game architecture assessment frameworks and maturity models - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on game implementation approaches and technology adoption. - -Remember: Always emphasize current game architectural data and rigorous source verification! diff --git a/src/workflows/1-preproduction/research/technical-steps/step-05-implementation-research.md b/src/workflows/1-preproduction/research/technical-steps/step-05-implementation-research.md deleted file mode 100644 index 6a236ef..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-05-implementation-research.md +++ /dev/null @@ -1,260 +0,0 @@ -# Game Technical Research Step 5: Game Implementation Research - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME IMPLEMENTATION ENGINEER, not content generator -- 💬 FOCUS on game development implementation approaches and technology adoption -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after implementation research content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Focus on game development implementation approaches and technology adoption strategies -- Web search capabilities with source verification are enabled -- This step prepares for the final synthesis step - -## YOUR TASK: - -Conduct comprehensive game implementation research with emphasis on practical game development approaches, team workflows, and technology adoption. - -## GAME IMPLEMENTATION RESEARCH SEQUENCE: - -### 1. Begin Game Implementation Research - -Start with game implementation research approach: -"Now I'll complete our game technical research with **game implementation approaches and technology adoption** analysis. - -**Game Implementation Research Focus:** - -- Game development workflow and iteration strategies -- Game testing and QA approaches (playtesting, automated testing, certification) -- Game deployment and release management -- Team organization and discipline requirements for this game type -- Game development cost optimization and scope management - -**Let me search for current game implementation and adoption strategies.**" - -### 2. Web Search for Game Development Workflows - -Search for current game development practices: -Search the web: "game development workflow iteration playtesting practices" - -**Game development workflow focus:** - -- Agile and iterative game development approaches -- Playtesting pipelines and feedback integration -- Alpha, beta, and early access strategies -- Game jam and rapid prototyping methodologies - -### 3. Web Search for Game QA and Testing Approaches - -Search for current game QA practices: -Search the web: "game QA testing automated playtesting certification" - -**Game QA focus:** - -- Automated game testing frameworks and tools -- Platform certification QA requirements -- Performance and compatibility testing -- Gameplay balance and tuning methodologies - -### 4. Web Search for Game Release and Operations Excellence - -Search for current game release practices: -Search the web: "game release management live operations post-launch" - -**Game operations focus:** - -- Game launch readiness and release management -- Post-launch live operations and content cadence -- Player support and community management operations -- Performance monitoring and incident response for games - -### 5. Generate Game Implementation Research Content - -Prepare game implementation analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Game Implementation Approaches and Technology Adoption - -### Game Development Workflow and Iteration - -[Game development workflow analysis with source citations] -_Agile Game Development: [Scrum, Kanban, and hybrid approaches for game teams]_ -_Prototyping and Iteration: [Rapid prototyping and game feel iteration strategies]_ -_Playtesting Pipeline: [Internal, external, and community playtesting approaches]_ -_Source: [URL]_ - -### Game Testing and Quality Assurance - -[Game QA analysis with source citations] -_Automated Game Testing: [Unit testing, integration testing, and automated gameplay testing]_ -_Manual QA Processes: [Bug tracking, regression testing, and platform certification QA]_ -_Performance Testing: [Frame rate profiling, memory testing, and platform optimization]_ -_Gameplay Balance Testing: [Data-driven balancing and tuning methodologies]_ -_Source: [URL]_ - -### Game Deployment and Release Management - -[Game deployment analysis with source citations] -_Build Pipeline: [CI/CD for game builds, automated packaging and submission]_ -_Platform Submission Process: [Console and storefront submission workflows]_ -_Early Access and Beta Strategies: [Pre-launch player acquisition and feedback loops]_ -_Launch Readiness Framework: [Go/no-go criteria and launch preparation checklist]_ -_Source: [URL]_ - -### Live Game Operations and Post-Launch - -[Live game operations analysis with source citations] -_Content Update Cadence: [Patch scheduling, DLC planning, and live event operations]_ -_Player Support Operations: [Bug triage, player report handling, and community response]_ -_Performance Monitoring: [Server monitoring, crash reporting, and incident response]_ -_Live Balance and Tuning: [Real-time game economy and balance adjustment]_ -_Source: [URL]_ - -### Game Development Team Organization - -[Game team organization analysis with source citations] -_Core Disciplines Required: [Engineering, art, design, audio, and production roles]_ -_Team Scaling Patterns: [How teams grow from prototype to full production]_ -_Outsourcing and Co-development: [When and how to use external development resources]_ -_Remote and Distributed Game Teams: [Collaboration tools and practices for distributed dev]_ -_Source: [URL]_ - -### Cost Optimization and Scope Management - -[Game cost optimization analysis with source citations] -_Development Cost Estimation: [Cost modeling for this type of game]_ -_Scope Control Strategies: [Feature prioritization and cut decision frameworks]_ -_Asset Production Optimization: [AI-assisted art, audio, and procedural content cost savings]_ -_Engine and Middleware Cost Management: [License, royalty, and subscription cost optimization]_ -_Source: [URL]_ - -### Risk Assessment and Mitigation - -[Game development risk mitigation analysis with source citations] -_Technical Debt Risks: [Legacy tech and engine decisions creating future burdens]_ -_Scope Creep Risk: [Feature expansion and project drift mitigation]_ -_Platform Certification Risk: [Factors causing platform submission failures]_ -_Launch Timing Risk: [Competitive launch window and market readiness risks]_ -_Source: [URL]_ - -## Game Technical Research Recommendations - -### Implementation Roadmap - -[Game development implementation roadmap recommendations] - -### Game Technology Stack Recommendations - -[Technology stack suggestions for this game type and team] - -### Skill and Hiring Requirements - -[Skill development and hiring recommendations for the game] - -### Success Metrics and KPIs - -[Game development success measurement framework] -``` - -### 6. Present Analysis and Continue Option - -Show the generated game implementation research and present continue option: -"I've completed the **game implementation research and technology adoption** analysis for {{research_topic}}. - -**Game Implementation Highlights:** - -- Game development workflow and iteration strategies documented -- Game testing and QA approaches analyzed -- Deployment, release management, and live operations patterns mapped -- Team organization and discipline requirements identified -- Cost optimization and scope management strategies provided - -**Game technical research phases completed:** - -- Step 1: Research scope confirmation -- Step 2: Game technology stack analysis -- Step 3: Game integration patterns analysis -- Step 4: Game architectural patterns analysis -- Step 5: Game implementation research (current step) - -**Ready to proceed to the final synthesis step?** -[C] Continue - Save this to document and proceed to synthesis - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load: `./step-06-research-synthesis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 5. - -## SUCCESS METRICS: - -✅ Game development workflow and iteration strategies identified with current citations -✅ Game testing and QA approaches thoroughly analyzed -✅ Deployment, release management, and live operations clearly documented -✅ Team organization and discipline requirements mapped -✅ Cost optimization and risk mitigation strategies provided -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Proper routing to synthesis step (step-06) - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current game development facts - -❌ Missing critical game development workflow or iteration strategies -❌ Not providing practical game implementation guidance -❌ Incomplete game QA or deployment analysis -❌ Not presenting continue option to synthesis step -❌ Appending content without user selecting 'C' -❌ Not routing to step-06-research-synthesis.md - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## GAME IMPLEMENTATION RESEARCH PROTOCOLS: - -- Search for game development post-mortems and case studies on GDC Vault -- Research game QA and testing tool documentation and best practices -- Identify common game development challenges and solutions from developer forums -- Research game deployment and live operations frameworks -- Analyze game development cost models and scope management frameworks - -## GAME TECHNICAL RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- Game implementation research step completed -- Content appended to research document with source citations -- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5] -- Ready to proceed to final synthesis step - -## NEXT STEP: - -After user selects 'C', load `./step-06-research-synthesis.md` to produce the comprehensive game technical research document with narrative introduction, detailed TOC, and executive summary. diff --git a/src/workflows/1-preproduction/research/technical-steps/step-06-research-synthesis.md b/src/workflows/1-preproduction/research/technical-steps/step-06-research-synthesis.md deleted file mode 100644 index 8d2a496..0000000 --- a/src/workflows/1-preproduction/research/technical-steps/step-06-research-synthesis.md +++ /dev/null @@ -1,486 +0,0 @@ -# Game Technical Research Step 6: Technical Synthesis and Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A GAME TECHNICAL RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on comprehensive game technical synthesis and authoritative conclusions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after synthesis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive game technical analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive game technical research -- All game technical research sections have been completed (tech stack, integration, architecture, implementation) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete game technical research document - -## YOUR TASK: - -Produce a comprehensive, authoritative game technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive game technical research. - -## COMPREHENSIVE GAME TECHNICAL DOCUMENT SYNTHESIS: - -### 1. Game Technical Document Structure Planning - -**Complete Game Technical Research Document Structure:** - -```markdown -# [Compelling Game Technical Title]: Comprehensive {{research_topic}} Game Technical Research - -## Executive Summary - -[Brief compelling overview of key game technical findings and strategic implications] - -## Table of Contents - -- Game Technical Research Introduction and Methodology -- Game Technology Landscape and Engine Analysis -- Game Architecture and Design Patterns -- Game Implementation Approaches and Best Practices -- Game Integration Patterns and Online Services -- Game Performance and Platform Optimization -- Game Security and Compliance Considerations -- Strategic Game Technical Recommendations -- Game Development Roadmap and Risk Assessment -- Future Game Technology Outlook and Innovation Opportunities -- Game Technical Research Methodology and Source Documentation -- Game Technical Appendices and Reference Materials -``` - -### 2. Generate Compelling Game Technical Introduction - -**Game Technical Introduction Requirements:** - -- Hook reader with compelling game technical opening about {{research_topic}} -- Establish game technical research significance and current relevance for game dev -- Outline comprehensive game technical research methodology -- Preview key game technical findings and GDD-relevant implications -- Set authoritative, game development expert tone - -**Web Search for Game Technical Introduction Context:** -Search the web: "{{research_topic}} game technical significance importance" - -### 3. Synthesize All Game Technical Research Sections - -**Game Technical Section-by-Section Integration:** - -- Combine game tech stack overview from step-02 -- Integrate game integration patterns from step-03 -- Incorporate game architectural patterns from step-04 -- Add game implementation research from step-05 -- Add cross-technical insights and connections -- Ensure comprehensive game technical coverage with no gaps - -### 4. Generate Complete Game Technical Document Content - -#### Final Game Technical Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Game Technical Research - -## Executive Summary - -[2-3 paragraph compelling summary of the most critical game technical findings and strategic implications for {{research_topic}} based on comprehensive current game technical research] - -**Key Game Technical Findings:** - -- [Most significant game engine and architecture insights] -- [Critical game implementation considerations] -- [Important game technology trends] -- [Strategic game technical implications for GDD] - -**Game Technical Recommendations:** - -- [Top 3-5 actionable game technical recommendations based on research] - -## Table of Contents - -1. Game Technical Research Introduction and Methodology -2. {{research_topic}} Game Technology Landscape and Engine Analysis -3. Game Architecture and Design Patterns -4. Game Implementation Approaches and Best Practices -5. Game Integration Patterns and Online Services -6. Game Performance and Platform Optimization -7. Game Security and Compliance Considerations -8. Strategic Game Technical Recommendations -9. Game Development Roadmap and Risk Assessment -10. Future Game Technology Outlook and Innovation Opportunities -11. Game Technical Research Methodology and Source Verification -12. Game Technical Appendices and Reference Materials - -## 1. Game Technical Research Introduction and Methodology - -### Game Technical Research Significance - -[Compelling game technical narrative about why {{research_topic}} game technical research is critical right now] -_Technical Importance: [Strategic game technical significance with current game industry context]_ -_Studio Impact: [Business and development implications of this technical research]_ -_Source: [URL]_ - -### Game Technical Research Methodology - -[Comprehensive description of game technical research approach including:] - -- **Technical Scope**: [Comprehensive game technical coverage areas] -- **Data Sources**: [Authoritative game technical sources and verification approach] -- **Analysis Framework**: [Structured game technical analysis methodology] -- **Time Period**: [current focus and game technical evolution context] -- **Technical Depth**: [Level of game technical detail and analysis] - -### Game Technical Research Goals and Objectives - -**Original Game Technical Goals:** {{research_goals}} - -**Achieved Game Technical Objectives:** - -- [Game Technical Goal 1 achievement with supporting evidence] -- [Game Technical Goal 2 achievement with supporting evidence] -- [Additional game technical insights discovered during research] - -## 2. {{research_topic}} Game Technology Landscape and Engine Analysis - -### Current Game Engine Landscape - -[Comprehensive game engine analysis synthesized from step-02 with current context] -_Dominant Engines: [Current game engine adoption for this game type]_ -_Engine Trade-offs: [Key architectural decisions engine choice entails]_ -_Engine Ecosystem: [Community, middleware support, and tooling maturity]_ -_Source: [URL]_ - -### Game Technology Stack and Middleware - -[Complete game technology stack analysis] -_Language and Scripting Stack: [Programming languages and scripting choices]_ -_Middleware Ecosystem: [Physics, audio, animation, and networking middleware]_ -_Tool Pipeline: [Development, profiling, and asset pipeline tools]_ -_Source: [URL]_ - -## 3. Game Architecture and Design Patterns - -### Core Game Architecture Patterns - -[Game architectural analysis from step-04 with current context] -_Architecture Approach: [ECS, OOP, data-oriented, and hybrid patterns]_ -_Game Loop Design: [Update pipeline and timestep architecture]_ -_World and Level Architecture: [Scene graph, streaming, and spatial systems]_ -_Source: [URL]_ - -### Rendering and Visual Architecture - -[Comprehensive rendering architecture analysis] -_Rendering Pipeline: [Forward vs deferred rendering choice and rationale]_ -_Lighting Architecture: [Real-time lighting, baked GI, and hybrid approaches]_ -_Platform-Specific Rendering: [How rendering architecture adapts across platforms]_ -_Source: [URL]_ - -## 4. Game Implementation Approaches and Best Practices - -### Current Game Development Methodologies - -[Game implementation analysis from step-05 with current context] -_Development Workflow: [Agile, milestone-based, and iterative game development]_ -_Prototyping and Playtesting: [Rapid iteration and feedback integration approaches]_ -_QA and Certification: [Game testing pipeline and platform certification preparation]_ -_Source: [URL]_ - -### Game Development Tools and Workflow - -[Comprehensive game development workflow analysis] -_IDE and Authoring Tools: [Development environments and level editor workflows]_ -_Build and Deployment Pipeline: [CI/CD, build automation, and platform submission]_ -_Collaboration and Version Control: [Git LFS, Perforce, and remote team collaboration]_ -_Source: [URL]_ - -## 5. Game Integration Patterns and Online Services - -### Online and Multiplayer Integration - -[Game integration patterns analysis from step-03 with current context] -_Backend Services: [Game backend platform choices and integration patterns]_ -_Multiplayer Architecture: [Netcode, matchmaking, and server infrastructure]_ -_Platform Service Integration: [Steam, console, and mobile platform API integration]_ -_Source: [URL]_ - -### Live Service and Analytics Integration - -[Comprehensive live service analysis] -_Analytics and Telemetry: [Player behavior data collection and analysis]_ -_Live Operations Infrastructure: [Patching, content delivery, and live event systems]_ -_Anti-Cheat Integration: [Fair play enforcement and security patterns]_ -_Source: [URL]_ - -## 6. Game Performance and Platform Optimization - -### Performance Targets and Budgets - -[Game performance analysis based on research findings] -_Performance Benchmarks: [Target frame rates and performance budgets by platform]_ -_CPU and GPU Optimization: [Draw call, shader, and CPU thread optimization strategies]_ -_Memory Management: [Memory allocation and streaming optimization]_ -_Source: [URL]_ - -### Cross-Platform Performance Considerations - -[Comprehensive cross-platform analysis] -_Console Optimization: [PS5, Xbox Series, and Nintendo platform-specific optimization]_ -_PC Scalability: [Low-end to high-end PC performance scaling strategies]_ -_Mobile Performance: [Mobile GPU constraints and battery-conscious optimization]_ -_Source: [URL]_ - -## 7. Game Security and Compliance Considerations - -### Game Security Best Practices - -[Game security analysis with current context] -_Anti-Cheat Architecture: [Server authority, client validation, and anti-cheat integration]_ -_Player Data Security: [Secure save, transaction, and account data handling]_ -_Network Security: [DDoS protection, packet validation, and connection security]_ -_Source: [URL]_ - -### Game Compliance Considerations - -[Comprehensive game compliance analysis] -_Platform Certification Requirements: [Technical requirements for console and PC stores]_ -_Privacy and Age Compliance: [COPPA, GDPR, and age rating technical requirements]_ -_Accessibility Standards: [Technical accessibility requirements and best practices]_ -_Source: [URL]_ - -## 8. Strategic Game Technical Recommendations - -### Game Technical Strategy and Decision Framework - -[Strategic game technical recommendations based on comprehensive research] -_Engine Recommendation: [Recommended game engine with rationale based on research]_ -_Architecture Recommendation: [Recommended architectural approach for this game type]_ -_Implementation Strategy: [Recommended game development workflow and methodology]_ -_Source: [URL]_ - -### Game Competitive Technical Advantage - -[Analysis of game technical competitive positioning] -_Technology Differentiation: [Game technical approaches providing competitive advantage]_ -_Innovation Opportunities: [Areas for game technical innovation and differentiation]_ -_Strategic Technology Investments: [Recommended game technology investments and priorities]_ -_Source: [URL]_ - -## 9. Game Development Roadmap and Risk Assessment - -### Game Technical Implementation Framework - -[Comprehensive game development guidance based on research findings] -_Development Phases: [Recommended phased game development approach]_ -_Technology Adoption Timeline: [Approach for game technology selection and adoption]_ -_Team and Resource Planning: [Game technical resource and skill planning]_ -_Source: [URL]_ - -### Game Technical Risk Management - -[Comprehensive game technical risk assessment] -_Engine and Technology Risks: [Risks from engine choice, middleware, and tech adoption]_ -_Implementation Risks: [Risks associated with game development and deployment]_ -_Platform and Certification Risks: [Risks from platform submission and compliance]_ -_Source: [URL]_ - -## 10. Future Game Technology Outlook and Innovation Opportunities - -### Emerging Game Technology Trends - -[Forward-looking game technical analysis based on comprehensive research] -_Near-term Game Technology Evolution: [1-2 year game tech development expectations]_ -_Medium-term Technology Trends: [3-5 year expected game technical developments]_ -_Long-term Game Technical Vision: [5+ year game technology outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Game Innovation and Research Opportunities - -[Game technical innovation analysis and recommendations] -_Research Opportunities: [Areas for game technical research and innovation]_ -_Emerging Technology Adoption: [New game technologies and adoption timelines]_ -_Innovation Framework: [Approach for fostering game technical innovation]_ -_Source: [URL]_ - -## 11. Game Technical Research Methodology and Source Verification - -### Comprehensive Game Technical Source Documentation - -[Complete documentation of all game technical research sources] -_Primary Game Technical Sources: [Key authoritative game technical sources used]_ -_Secondary Game Technical Sources: [Supporting game technical research and analysis]_ -_Game Technical Web Search Queries: [Complete list of game technical search queries used]_ - -### Game Technical Research Quality Assurance - -[Game technical quality assurance and validation approach] -_Game Technical Source Verification: [All game technical claims verified with multiple sources]_ -_Game Technical Confidence Levels: [Confidence assessments for uncertain game technical data]_ -_Game Technical Limitations: [Research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about game technical research approach]_ - -## 12. Game Technical Appendices and Reference Materials - -### Detailed Game Technical Data Tables - -[Comprehensive game technical data tables supporting research findings] -_Engine Comparison Tables: [Detailed game engine feature and cost comparisons]_ -_Technology Stack Analysis: [Detailed game technology evaluation and comparison data]_ -_Platform Performance Data: [Comprehensive platform performance characteristics data]_ - -### Game Technical Resources and References - -[Valuable game technical resources for continued research and implementation] -_Game Development Standards: [Relevant game technical standards and platform specs]_ -_Open Source Game Projects: [Key open source game engines and libraries]_ -_GDC Talks and Publications: [Relevant Game Developers Conference talks and papers]_ -_Game Dev Communities: [Professional game development networks and technical communities]_ - ---- - -## Game Technical Research Conclusion - -### Summary of Key Game Technical Findings - -[Comprehensive summary of the most important game technical research findings] - -### Strategic Game Technical Impact Assessment - -[Assessment of game technical implications for {{research_topic}}] - -### Next Steps Game Technical Recommendations - -[Specific next steps for leveraging this game technical research in GDD and development] - ---- - -**Game Technical Research Completion Date:** {{date}} -**Research Period:** Current comprehensive game technical analysis -**Document Length:** As needed for comprehensive game technical coverage -**Source Verification:** All game technical facts cited with current sources -**Game Technical Confidence Level:** High - based on multiple authoritative game technical sources - -_This comprehensive game technical research document serves as an authoritative game technical reference on {{research_topic}} and provides strategic game technical insights for informed GDD and game development decision-making._ -``` - -### 5. Present Complete Game Technical Document and Final Option - -**Game Technical Document Completion Presentation:** - -"I've completed the **comprehensive game technical research document synthesis** for **{{research_topic}}**, producing an authoritative game technical research document with: - -**Game Technical Document Features:** - -- **Compelling Game Technical Introduction**: Engaging opening that establishes game technical research significance -- **Comprehensive Game Technical TOC**: Complete navigation structure for game technical reference -- **Exhaustive Game Technical Research Coverage**: All game technical aspects of {{research_topic}} thoroughly analyzed -- **Executive Game Technical Summary**: Key game technical findings and GDD-relevant implications highlighted -- **Strategic Game Technical Recommendations**: Actionable game tech insights for development -- **Complete Game Technical Source Citations**: Every game technical claim verified with current sources - -**Game Technical Research Completeness:** - -- Game technology landscape and engine analysis fully documented -- Game architecture and design patterns comprehensively covered -- Game implementation approaches and best practices detailed -- Game integration, performance, and security analysis complete -- Strategic game technical insights and development guidance provided - -**Game Technical Document Standards Met:** - -- Exhaustive game technical research with no critical gaps -- Professional game technical structure and compelling narrative -- As long as needed for comprehensive game technical coverage -- Multiple independent game technical sources for all claims -- Current game technical data throughout with proper citations - -**Ready to complete this comprehensive game technical research document?** -[C] Complete Research - Save final comprehensive game technical document - -### 6. Handle Final Game Technical Completion - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the complete game technical document to the research file -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]` -- Complete the game technical research workflow -- Provide final game technical document delivery confirmation - -## APPEND TO DOCUMENT: - -When user selects 'C', append the complete comprehensive game technical research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling game technical introduction with research significance -✅ Comprehensive game technical table of contents with complete document structure -✅ Exhaustive game technical research coverage across all game technical aspects -✅ Executive game technical summary with key findings and GDD-relevant implications -✅ Strategic game technical recommendations grounded in comprehensive research -✅ Complete game technical source verification with current citations -✅ Professional game technical document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Game technical research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling game technical introduction -❌ Missing comprehensive game technical table of contents -❌ Incomplete game technical research coverage across game technical aspects -❌ Not providing executive game technical summary with key findings -❌ Missing strategic game technical recommendations based on research -❌ Relying solely on training data without web verification for current game facts -❌ Producing game technical document without professional structure -❌ Not presenting completion option for final game technical document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPREHENSIVE GAME TECHNICAL DOCUMENT STANDARDS: - -This step ensures the final game technical research document: - -- Serves as an authoritative game technical reference on {{research_topic}} -- Provides strategic game technical insights for informed GDD decision-making -- Includes comprehensive game technical coverage with no gaps -- Maintains rigorous game technical source verification standards -- Delivers strategic game technical insights and actionable recommendations -- Meets professional game technical research document quality standards - -## GAME TECHNICAL RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All game technical research steps completed (1-6) -- Comprehensive game technical research document generated -- Professional game technical document structure with intro, TOC, and summary -- All game technical sections appended with source citations -- Game technical research workflow status updated to complete -- Final comprehensive game technical research document delivered to user - -## FINAL GAME TECHNICAL DELIVERABLE: - -Complete authoritative game technical research document on {{research_topic}} that: - -- Establishes game technical credibility through comprehensive research -- Provides strategic game technical insights for informed GDD decision-making -- Serves as game technical reference document for continued studio use -- Maintains highest game technical research quality standards with current verification - -Congratulations on completing comprehensive game technical research with professional documentation! diff --git a/src/workflows/1-preproduction/research/workflow-market-research.md b/src/workflows/1-preproduction/research/workflow-market-research.md deleted file mode 100644 index b9160ad..0000000 --- a/src/workflows/1-preproduction/research/workflow-market-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: market-research -description: 'Conduct game market research on competition and players. Use when the user says "create a market research report about [game idea]".' ---- - -# Game Market Research Workflow - -**Goal:** Conduct comprehensive game market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a game market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings game industry knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `{module_config}` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `game_dev_experience` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **game market research**. - -**What game, genre, or game market area do you want to research?** - -For example: -- 'The open-world RPG market on PC and console' -- 'Mobile casual games targeting casual players' -- 'Indie roguelikes on Steam and itch.io' -- 'Or anything else you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Topic**: "What exactly about [topic] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects (e.g., specific platforms, player demographics, or competitor studios)?" - -## ROUTE TO MARKET RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "market"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./market-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for game market research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`** diff --git a/src/workflows/1-preproduction/research/workflow-technical-research.md b/src/workflows/1-preproduction/research/workflow-technical-research.md deleted file mode 100644 index cd535b1..0000000 --- a/src/workflows/1-preproduction/research/workflow-technical-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: technical-research -description: 'Conduct technical research on game technologies and architecture. Use when the user says "create a technical research report on [game tech topic]".' ---- - -# Game Technical Research Workflow - -**Goal:** Conduct comprehensive game technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a game technical research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings game development knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `{module_config}` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `game_dev_experience` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **game technical research**. - -**What game technology, engine, or technical area do you want to research?** - -For example: -- 'Unity vs Unreal Engine for a 3D action RPG' -- 'Netcode solutions for a multiplayer battle royale' -- 'Procedural generation approaches for dungeon design' -- 'Or any other game tech topic you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Technology**: "What specific aspect of [technology] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects (e.g., a particular engine, platform target, or game genre constraints)?" - -## ROUTE TO TECHNICAL RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "technical"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./technical-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for game technical research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**