feat: Overhaul and Enhance 2D Unity Game Dev Expansion Pack (#350)
* Updated game-sm agent to match the new core framework patterns * feat:Created more comprehensive game story matching new format system as well * feat:Added Game specific course correct task * feat:Updated dod-checklist to match new DoD format * feat:Added new Architect agent for appropriate architecture doc creation and design * feat:Overhaul of game-architecture-tmpl template * feat:Updated rest of templates besides level which doesnt really need it * feat: Finished extended architecture documentation needed for new game story tasks * feat: Updated game Developer to new format * feat: Updated last agent to new format and updated bmad-kb. bmad-kb I did my best with but im not sure of it's valid usage in the expansion pack, the AI generated more of the file then myself. I made sure to include it due to the new core-config file * feat: Finished updating designer agent to new format and cleaned up template linting errors * Built dist for web bundle * Increased expansion pack minor verison number * Updated architecht and design for sharding built-in * chore: bump bmad-2d-unity-game-dev version (minor) * updated config.yaml for game-specific pieces to supplement core-config.yaml * Updated game-core-config and epic processing for game story and game design. Initial implementation was far too generic * chore: bump bmad-2d-unity-game-dev version (patch) * feat: Fixed issue with multi-configs being needed. chore: bump bmad-2d-unity-game-dev version (patch) * Chore: Built web-bundle * feat: Added the ability to specify the unity editor install location.\nchore: bump bmad-2d-unity-game-dev version (patch) * feat: core-config must be in two places to support inherited tasks at this time so added instructions to copy and create one in expansion pack folder as well. chore: bump bmad-2d-unity-game-dev version (patch)
This commit is contained in:
PinkyD
12
dist/agents/analyst.txt
vendored
12
dist/agents/analyst.txt
vendored
@@ -76,14 +76,14 @@ persona:
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- create-project-brief: use task create-doc with project-brief-tmpl.yaml
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
|
||||
- yolo: Toggle Yolo Mode
|
||||
- doc-out: Output full document to current destination file
|
||||
- execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt for architectural decisions
|
||||
- brainstorm {topic}: Facilitate structured brainstorming session
|
||||
- doc-out: Output full document in progress to current destination file
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
|
||||
- elicit: run the task advanced-elicitation
|
||||
- document-project: Analyze and document existing project structure comprehensively
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
11
dist/agents/architect.txt
vendored
11
dist/agents/architect.txt
vendored
@@ -76,11 +76,16 @@ persona:
|
||||
- Living Architecture - Design for change and adaptation
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- yolo: Toggle Yolo Mode
|
||||
- create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
|
||||
- create-backend-architecture: use create-doc with architecture-tmpl.yaml
|
||||
- create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
|
||||
- create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
|
||||
- doc-out: Output full document to current destination file
|
||||
- document-project: execute the task document-project.md
|
||||
- execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
|
||||
- research {topic}: execute task create-deep-research-prompt for architectural decisions
|
||||
- research {topic}: execute task create-deep-research-prompt
|
||||
- shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Architect, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
3
dist/agents/bmad-master.txt
vendored
3
dist/agents/bmad-master.txt
vendored
@@ -70,10 +70,11 @@ commands:
|
||||
- kb: Toggle KB mode off (default) or on, when on will load and reference the .bmad-core/data/bmad-kb.md and converse with the user answering his questions with this informational resource
|
||||
- task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- doc-out: Output full document to current destination file
|
||||
- document-project: execute the task document-project.md
|
||||
- execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
|
||||
- shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
|
||||
- yolo: Toggle Yolo Mode
|
||||
- doc-out: Output full document to current destination file
|
||||
- exit: Exit (confirm)
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
9
dist/agents/pm.txt
vendored
9
dist/agents/pm.txt
vendored
@@ -72,9 +72,14 @@ persona:
|
||||
- Strategic thinking & outcome-oriented
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- create-doc {template}: execute task create-doc for template provided, if no template then ONLY list dependencies.templates
|
||||
- yolo: Toggle Yolo Mode
|
||||
- create-prd: run task create-doc.md with template prd-tmpl.yaml
|
||||
- create-brownfield-prd: run task create-doc.md with template brownfield-prd-tmpl.yaml
|
||||
- create-epic: Create epic for brownfield projects (task brownfield-create-epic)
|
||||
- create-story: Create user story from requirements (task brownfield-create-story)
|
||||
- doc-out: Output full document to current destination file
|
||||
- shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
|
||||
- correct-course: execute the correct-course task
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Exit (confirm)
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
320
dist/agents/po.txt
vendored
320
dist/agents/po.txt
vendored
@@ -75,23 +75,20 @@ persona:
|
||||
- Documentation Ecosystem Integrity - Maintain consistency across all documents
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- execute-checklist {checklist}: Run task execute-checklist (default->po-master-checklist)
|
||||
- execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
|
||||
- shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
|
||||
- correct-course: execute the correct-course task
|
||||
- create-epic: Create epic for brownfield projects (task brownfield-create-epic)
|
||||
- create-story: Create user story from requirements (task brownfield-create-story)
|
||||
- yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
|
||||
- doc-out: Output full document to current destination file
|
||||
- validate-story-draft {story}: run the task validate-next-story against the provided story file
|
||||
- yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
|
||||
- exit: Exit (confirm)
|
||||
dependencies:
|
||||
tasks:
|
||||
- execute-checklist.md
|
||||
- shard-doc.md
|
||||
- correct-course.md
|
||||
- brownfield-create-epic.md
|
||||
- brownfield-create-story.md
|
||||
- validate-next-story.md
|
||||
templates:
|
||||
- story-tmpl.yaml
|
||||
@@ -460,319 +457,6 @@ Document sharded successfully:
|
||||
- **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
|
||||
Create a single epic for smaller brownfield enhancements that don't require the full PRD and Architecture documentation process. This task is for isolated features or modifications that can be completed within a focused scope.
|
||||
|
||||
## When to Use This Task
|
||||
|
||||
**Use this task when:**
|
||||
|
||||
- The enhancement can be completed in 1-3 stories
|
||||
- No significant architectural changes are required
|
||||
- The enhancement follows existing project patterns
|
||||
- Integration complexity is minimal
|
||||
- Risk to existing system is low
|
||||
|
||||
**Use the full brownfield PRD/Architecture process when:**
|
||||
|
||||
- The enhancement requires multiple coordinated stories
|
||||
- Architectural planning is needed
|
||||
- Significant integration work is required
|
||||
- Risk assessment and mitigation planning is necessary
|
||||
|
||||
## Instructions
|
||||
|
||||
### 1. Project Analysis (Required)
|
||||
|
||||
Before creating the epic, gather essential information about the existing project:
|
||||
|
||||
**Existing Project Context:**
|
||||
|
||||
- [ ] Project purpose and current functionality understood
|
||||
- [ ] Existing technology stack identified
|
||||
- [ ] Current architecture patterns noted
|
||||
- [ ] Integration points with existing system identified
|
||||
|
||||
**Enhancement Scope:**
|
||||
|
||||
- [ ] Enhancement clearly defined and scoped
|
||||
- [ ] Impact on existing functionality assessed
|
||||
- [ ] Required integration points identified
|
||||
- [ ] Success criteria established
|
||||
|
||||
### 2. Epic Creation
|
||||
|
||||
Create a focused epic following this structure:
|
||||
|
||||
#### Epic Title
|
||||
|
||||
{{Enhancement Name}} - Brownfield Enhancement
|
||||
|
||||
#### Epic Goal
|
||||
|
||||
{{1-2 sentences describing what the epic will accomplish and why it adds value}}
|
||||
|
||||
#### Epic Description
|
||||
|
||||
**Existing System Context:**
|
||||
|
||||
- Current relevant functionality: {{brief description}}
|
||||
- Technology stack: {{relevant existing technologies}}
|
||||
- Integration points: {{where new work connects to existing system}}
|
||||
|
||||
**Enhancement Details:**
|
||||
|
||||
- What's being added/changed: {{clear description}}
|
||||
- How it integrates: {{integration approach}}
|
||||
- Success criteria: {{measurable outcomes}}
|
||||
|
||||
#### Stories
|
||||
|
||||
List 1-3 focused stories that complete the epic:
|
||||
|
||||
1. **Story 1:** {{Story title and brief description}}
|
||||
2. **Story 2:** {{Story title and brief description}}
|
||||
3. **Story 3:** {{Story title and brief description}}
|
||||
|
||||
#### Compatibility Requirements
|
||||
|
||||
- [ ] Existing APIs remain unchanged
|
||||
- [ ] Database schema changes are backward compatible
|
||||
- [ ] UI changes follow existing patterns
|
||||
- [ ] Performance impact is minimal
|
||||
|
||||
#### Risk Mitigation
|
||||
|
||||
- **Primary Risk:** {{main risk to existing system}}
|
||||
- **Mitigation:** {{how risk will be addressed}}
|
||||
- **Rollback Plan:** {{how to undo changes if needed}}
|
||||
|
||||
#### Definition of Done
|
||||
|
||||
- [ ] All stories completed with acceptance criteria met
|
||||
- [ ] Existing functionality verified through testing
|
||||
- [ ] Integration points working correctly
|
||||
- [ ] Documentation updated appropriately
|
||||
- [ ] No regression in existing features
|
||||
|
||||
### 3. Validation Checklist
|
||||
|
||||
Before finalizing the epic, ensure:
|
||||
|
||||
**Scope Validation:**
|
||||
|
||||
- [ ] Epic can be completed in 1-3 stories maximum
|
||||
- [ ] No architectural documentation is required
|
||||
- [ ] Enhancement follows existing patterns
|
||||
- [ ] Integration complexity is manageable
|
||||
|
||||
**Risk Assessment:**
|
||||
|
||||
- [ ] Risk to existing system is low
|
||||
- [ ] Rollback plan is feasible
|
||||
- [ ] Testing approach covers existing functionality
|
||||
- [ ] Team has sufficient knowledge of integration points
|
||||
|
||||
**Completeness Check:**
|
||||
|
||||
- [ ] Epic goal is clear and achievable
|
||||
- [ ] Stories are properly scoped
|
||||
- [ ] Success criteria are measurable
|
||||
- [ ] Dependencies are identified
|
||||
|
||||
### 4. Handoff to Story Manager
|
||||
|
||||
Once the epic is validated, provide this handoff to the Story Manager:
|
||||
|
||||
---
|
||||
|
||||
**Story Manager Handoff:**
|
||||
|
||||
"Please develop detailed user stories for this brownfield epic. Key considerations:
|
||||
|
||||
- This is an enhancement to an existing system running {{technology stack}}
|
||||
- Integration points: {{list key integration points}}
|
||||
- Existing patterns to follow: {{relevant existing patterns}}
|
||||
- Critical compatibility requirements: {{key requirements}}
|
||||
- Each story must include verification that existing functionality remains intact
|
||||
|
||||
The epic should maintain system integrity while delivering {{epic goal}}."
|
||||
|
||||
---
|
||||
|
||||
## Success Criteria
|
||||
|
||||
The epic creation is successful when:
|
||||
|
||||
1. Enhancement scope is clearly defined and appropriately sized
|
||||
2. Integration approach respects existing system architecture
|
||||
3. Risk to existing functionality is minimized
|
||||
4. Stories are logically sequenced for safe implementation
|
||||
5. Compatibility requirements are clearly specified
|
||||
6. Rollback plan is feasible and documented
|
||||
|
||||
## Important Notes
|
||||
|
||||
- This task is specifically for SMALL brownfield enhancements
|
||||
- If the scope grows beyond 3 stories, consider the full brownfield PRD process
|
||||
- Always prioritize existing system integrity over new functionality
|
||||
- When in doubt about scope or complexity, escalate to full brownfield planning
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
||||
Create a single user story for very small brownfield enhancements that can be completed in one focused development session. This task is for minimal additions or bug fixes that require existing system integration awareness.
|
||||
|
||||
## When to Use This Task
|
||||
|
||||
**Use this task when:**
|
||||
|
||||
- The enhancement can be completed in a single story
|
||||
- No new architecture or significant design is required
|
||||
- The change follows existing patterns exactly
|
||||
- Integration is straightforward with minimal risk
|
||||
- Change is isolated with clear boundaries
|
||||
|
||||
**Use brownfield-create-epic when:**
|
||||
|
||||
- The enhancement requires 2-3 coordinated stories
|
||||
- Some design work is needed
|
||||
- Multiple integration points are involved
|
||||
|
||||
**Use the full brownfield PRD/Architecture process when:**
|
||||
|
||||
- The enhancement requires multiple coordinated stories
|
||||
- Architectural planning is needed
|
||||
- Significant integration work is required
|
||||
|
||||
## Instructions
|
||||
|
||||
### 1. Quick Project Assessment
|
||||
|
||||
Gather minimal but essential context about the existing project:
|
||||
|
||||
**Current System Context:**
|
||||
|
||||
- [ ] Relevant existing functionality identified
|
||||
- [ ] Technology stack for this area noted
|
||||
- [ ] Integration point(s) clearly understood
|
||||
- [ ] Existing patterns for similar work identified
|
||||
|
||||
**Change Scope:**
|
||||
|
||||
- [ ] Specific change clearly defined
|
||||
- [ ] Impact boundaries identified
|
||||
- [ ] Success criteria established
|
||||
|
||||
### 2. Story Creation
|
||||
|
||||
Create a single focused story following this structure:
|
||||
|
||||
#### Story Title
|
||||
|
||||
{{Specific Enhancement}} - Brownfield Addition
|
||||
|
||||
#### User Story
|
||||
|
||||
As a {{user type}},
|
||||
I want {{specific action/capability}},
|
||||
So that {{clear benefit/value}}.
|
||||
|
||||
#### Story Context
|
||||
|
||||
**Existing System Integration:**
|
||||
|
||||
- Integrates with: {{existing component/system}}
|
||||
- Technology: {{relevant tech stack}}
|
||||
- Follows pattern: {{existing pattern to follow}}
|
||||
- Touch points: {{specific integration points}}
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
**Functional Requirements:**
|
||||
|
||||
1. {{Primary functional requirement}}
|
||||
2. {{Secondary functional requirement (if any)}}
|
||||
3. {{Integration requirement}}
|
||||
|
||||
**Integration Requirements:** 4. Existing {{relevant functionality}} continues to work unchanged 5. New functionality follows existing {{pattern}} pattern 6. Integration with {{system/component}} maintains current behavior
|
||||
|
||||
**Quality Requirements:** 7. Change is covered by appropriate tests 8. Documentation is updated if needed 9. No regression in existing functionality verified
|
||||
|
||||
#### Technical Notes
|
||||
|
||||
- **Integration Approach:** {{how it connects to existing system}}
|
||||
- **Existing Pattern Reference:** {{link or description of pattern to follow}}
|
||||
- **Key Constraints:** {{any important limitations or requirements}}
|
||||
|
||||
#### Definition of Done
|
||||
|
||||
- [ ] Functional requirements met
|
||||
- [ ] Integration requirements verified
|
||||
- [ ] Existing functionality regression tested
|
||||
- [ ] Code follows existing patterns and standards
|
||||
- [ ] Tests pass (existing and new)
|
||||
- [ ] Documentation updated if applicable
|
||||
|
||||
### 3. Risk and Compatibility Check
|
||||
|
||||
**Minimal Risk Assessment:**
|
||||
|
||||
- **Primary Risk:** {{main risk to existing system}}
|
||||
- **Mitigation:** {{simple mitigation approach}}
|
||||
- **Rollback:** {{how to undo if needed}}
|
||||
|
||||
**Compatibility Verification:**
|
||||
|
||||
- [ ] No breaking changes to existing APIs
|
||||
- [ ] Database changes (if any) are additive only
|
||||
- [ ] UI changes follow existing design patterns
|
||||
- [ ] Performance impact is negligible
|
||||
|
||||
### 4. Validation Checklist
|
||||
|
||||
Before finalizing the story, confirm:
|
||||
|
||||
**Scope Validation:**
|
||||
|
||||
- [ ] Story can be completed in one development session
|
||||
- [ ] Integration approach is straightforward
|
||||
- [ ] Follows existing patterns exactly
|
||||
- [ ] No design or architecture work required
|
||||
|
||||
**Clarity Check:**
|
||||
|
||||
- [ ] Story requirements are unambiguous
|
||||
- [ ] Integration points are clearly specified
|
||||
- [ ] Success criteria are testable
|
||||
- [ ] Rollback approach is simple
|
||||
|
||||
## Success Criteria
|
||||
|
||||
The story creation is successful when:
|
||||
|
||||
1. Enhancement is clearly defined and appropriately scoped for single session
|
||||
2. Integration approach is straightforward and low-risk
|
||||
3. Existing system patterns are identified and will be followed
|
||||
4. Rollback plan is simple and feasible
|
||||
5. Acceptance criteria include existing functionality verification
|
||||
|
||||
## Important Notes
|
||||
|
||||
- This task is for VERY SMALL brownfield changes only
|
||||
- If complexity grows during analysis, escalate to brownfield-create-epic
|
||||
- Always prioritize existing system integrity
|
||||
- When in doubt about integration complexity, use brownfield-create-epic instead
|
||||
- Stories should take no more than 4 hours of focused development work
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
# Validate Next Story Task
|
||||
|
||||
|
||||
1
dist/agents/qa.txt
vendored
1
dist/agents/qa.txt
vendored
@@ -80,7 +80,6 @@ story-file-permissions:
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- review {story}: execute the task review-story for the highest sequence story in docs/stories unless another is specified - keep any specified technical-preferences in mind as needed
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
6
dist/agents/sm.txt
vendored
6
dist/agents/sm.txt
vendored
@@ -68,9 +68,9 @@ persona:
|
||||
- You are NOT allowed to implement stories or modify code EVER!
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- draft: Execute task create-next-story
|
||||
- correct-course: Execute task correct-course
|
||||
- checklist {checklist}: Show numbered list of checklists if not provided, execute task execute-checklist
|
||||
- draft: Execute task create-next-story.md
|
||||
- correct-course: Execute task correct-course.md
|
||||
- story-checklist: Execute task execute-checklist.md with checklist story-draft-checklist.md
|
||||
- exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
|
||||
299
dist/agents/ux-expert.txt
vendored
299
dist/agents/ux-expert.txt
vendored
@@ -73,15 +73,12 @@ persona:
|
||||
- You can craft effective prompts for AI UI generation tools like v0, or Lovable.
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
||||
- generate-ui-prompt: Create AI frontend generation prompt
|
||||
- research {topic}: Execute create-deep-research-prompt task to generate a prompt to init UX deep research
|
||||
- execute-checklist {checklist}: Run task execute-checklist (default->po-master-checklist)
|
||||
- create-front-end-spec: run task create-doc.md with template front-end-spec-tmpl.yaml
|
||||
- generate-ui-prompt: Run task generate-ai-frontend-prompt.md
|
||||
- exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
- generate-ai-frontend-prompt.md
|
||||
- create-deep-research-prompt.md
|
||||
- create-doc.md
|
||||
- execute-checklist.md
|
||||
templates:
|
||||
@@ -145,298 +142,6 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
- <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
|
||||
==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
|
||||
## Purpose
|
||||
|
||||
Generate well-structured research prompts that:
|
||||
|
||||
- Define clear research objectives and scope
|
||||
- Specify appropriate research methodologies
|
||||
- Outline expected deliverables and formats
|
||||
- Guide systematic investigation of complex topics
|
||||
- Ensure actionable insights are captured
|
||||
|
||||
## Research Type Selection
|
||||
|
||||
CRITICAL: First, help the user select the most appropriate research focus based on their needs and any input documents they've provided.
|
||||
|
||||
### 1. Research Focus Options
|
||||
|
||||
Present these numbered options to the user:
|
||||
|
||||
1. **Product Validation Research**
|
||||
|
||||
- Validate product hypotheses and market fit
|
||||
- Test assumptions about user needs and solutions
|
||||
- Assess technical and business feasibility
|
||||
- Identify risks and mitigation strategies
|
||||
|
||||
2. **Market Opportunity Research**
|
||||
|
||||
- Analyze market size and growth potential
|
||||
- Identify market segments and dynamics
|
||||
- Assess market entry strategies
|
||||
- Evaluate timing and market readiness
|
||||
|
||||
3. **User & Customer Research**
|
||||
|
||||
- Deep dive into user personas and behaviors
|
||||
- Understand jobs-to-be-done and pain points
|
||||
- Map customer journeys and touchpoints
|
||||
- Analyze willingness to pay and value perception
|
||||
|
||||
4. **Competitive Intelligence Research**
|
||||
|
||||
- Detailed competitor analysis and positioning
|
||||
- Feature and capability comparisons
|
||||
- Business model and strategy analysis
|
||||
- Identify competitive advantages and gaps
|
||||
|
||||
5. **Technology & Innovation Research**
|
||||
|
||||
- Assess technology trends and possibilities
|
||||
- Evaluate technical approaches and architectures
|
||||
- Identify emerging technologies and disruptions
|
||||
- Analyze build vs. buy vs. partner options
|
||||
|
||||
6. **Industry & Ecosystem Research**
|
||||
|
||||
- Map industry value chains and dynamics
|
||||
- Identify key players and relationships
|
||||
- Analyze regulatory and compliance factors
|
||||
- Understand partnership opportunities
|
||||
|
||||
7. **Strategic Options Research**
|
||||
|
||||
- Evaluate different strategic directions
|
||||
- Assess business model alternatives
|
||||
- Analyze go-to-market strategies
|
||||
- Consider expansion and scaling paths
|
||||
|
||||
8. **Risk & Feasibility Research**
|
||||
|
||||
- Identify and assess various risk factors
|
||||
- Evaluate implementation challenges
|
||||
- Analyze resource requirements
|
||||
- Consider regulatory and legal implications
|
||||
|
||||
9. **Custom Research Focus**
|
||||
|
||||
- User-defined research objectives
|
||||
- Specialized domain investigation
|
||||
- Cross-functional research needs
|
||||
|
||||
### 2. Input Processing
|
||||
|
||||
**If Project Brief provided:**
|
||||
|
||||
- Extract key product concepts and goals
|
||||
- Identify target users and use cases
|
||||
- Note technical constraints and preferences
|
||||
- Highlight uncertainties and assumptions
|
||||
|
||||
**If Brainstorming Results provided:**
|
||||
|
||||
- Synthesize main ideas and themes
|
||||
- Identify areas needing validation
|
||||
- Extract hypotheses to test
|
||||
- Note creative directions to explore
|
||||
|
||||
**If Market Research provided:**
|
||||
|
||||
- Build on identified opportunities
|
||||
- Deepen specific market insights
|
||||
- Validate initial findings
|
||||
- Explore adjacent possibilities
|
||||
|
||||
**If Starting Fresh:**
|
||||
|
||||
- Gather essential context through questions
|
||||
- Define the problem space
|
||||
- Clarify research objectives
|
||||
- Establish success criteria
|
||||
|
||||
## Process
|
||||
|
||||
### 3. Research Prompt Structure
|
||||
|
||||
CRITICAL: collaboratively develop a comprehensive research prompt with these components.
|
||||
|
||||
#### A. Research Objectives
|
||||
|
||||
CRITICAL: collaborate with the user to articulate clear, specific objectives for the research.
|
||||
|
||||
- Primary research goal and purpose
|
||||
- Key decisions the research will inform
|
||||
- Success criteria for the research
|
||||
- Constraints and boundaries
|
||||
|
||||
#### B. Research Questions
|
||||
|
||||
CRITICAL: collaborate with the user to develop specific, actionable research questions organized by theme.
|
||||
|
||||
**Core Questions:**
|
||||
|
||||
- Central questions that must be answered
|
||||
- Priority ranking of questions
|
||||
- Dependencies between questions
|
||||
|
||||
**Supporting Questions:**
|
||||
|
||||
- Additional context-building questions
|
||||
- Nice-to-have insights
|
||||
- Future-looking considerations
|
||||
|
||||
#### C. Research Methodology
|
||||
|
||||
**Data Collection Methods:**
|
||||
|
||||
- Secondary research sources
|
||||
- Primary research approaches (if applicable)
|
||||
- Data quality requirements
|
||||
- Source credibility criteria
|
||||
|
||||
**Analysis Frameworks:**
|
||||
|
||||
- Specific frameworks to apply
|
||||
- Comparison criteria
|
||||
- Evaluation methodologies
|
||||
- Synthesis approaches
|
||||
|
||||
#### D. Output Requirements
|
||||
|
||||
**Format Specifications:**
|
||||
|
||||
- Executive summary requirements
|
||||
- Detailed findings structure
|
||||
- Visual/tabular presentations
|
||||
- Supporting documentation
|
||||
|
||||
**Key Deliverables:**
|
||||
|
||||
- Must-have sections and insights
|
||||
- Decision-support elements
|
||||
- Action-oriented recommendations
|
||||
- Risk and uncertainty documentation
|
||||
|
||||
### 4. Prompt Generation
|
||||
|
||||
**Research Prompt Template:**
|
||||
|
||||
```markdown
|
||||
## Research Objective
|
||||
|
||||
[Clear statement of what this research aims to achieve]
|
||||
|
||||
## Background Context
|
||||
|
||||
[Relevant information from project brief, brainstorming, or other inputs]
|
||||
|
||||
## Research Questions
|
||||
|
||||
### Primary Questions (Must Answer)
|
||||
|
||||
1. [Specific, actionable question]
|
||||
2. [Specific, actionable question]
|
||||
...
|
||||
|
||||
### Secondary Questions (Nice to Have)
|
||||
|
||||
1. [Supporting question]
|
||||
2. [Supporting question]
|
||||
...
|
||||
|
||||
## Research Methodology
|
||||
|
||||
### Information Sources
|
||||
|
||||
- [Specific source types and priorities]
|
||||
|
||||
### Analysis Frameworks
|
||||
|
||||
- [Specific frameworks to apply]
|
||||
|
||||
### Data Requirements
|
||||
|
||||
- [Quality, recency, credibility needs]
|
||||
|
||||
## Expected Deliverables
|
||||
|
||||
### Executive Summary
|
||||
|
||||
- Key findings and insights
|
||||
- Critical implications
|
||||
- Recommended actions
|
||||
|
||||
### Detailed Analysis
|
||||
|
||||
[Specific sections needed based on research type]
|
||||
|
||||
### Supporting Materials
|
||||
|
||||
- Data tables
|
||||
- Comparison matrices
|
||||
- Source documentation
|
||||
|
||||
## Success Criteria
|
||||
|
||||
[How to evaluate if research achieved its objectives]
|
||||
|
||||
## Timeline and Priority
|
||||
|
||||
[If applicable, any time constraints or phasing]
|
||||
```
|
||||
|
||||
### 5. Review and Refinement
|
||||
|
||||
1. **Present Complete Prompt**
|
||||
|
||||
- Show the full research prompt
|
||||
- Explain key elements and rationale
|
||||
- Highlight any assumptions made
|
||||
|
||||
2. **Gather Feedback**
|
||||
|
||||
- Are the objectives clear and correct?
|
||||
- Do the questions address all concerns?
|
||||
- Is the scope appropriate?
|
||||
- Are output requirements sufficient?
|
||||
|
||||
3. **Refine as Needed**
|
||||
- Incorporate user feedback
|
||||
- Adjust scope or focus
|
||||
- Add missing elements
|
||||
- Clarify ambiguities
|
||||
|
||||
### 6. Next Steps Guidance
|
||||
|
||||
**Execution Options:**
|
||||
|
||||
1. **Use with AI Research Assistant**: Provide this prompt to an AI model with research capabilities
|
||||
2. **Guide Human Research**: Use as a framework for manual research efforts
|
||||
3. **Hybrid Approach**: Combine AI and human research using this structure
|
||||
|
||||
**Integration Points:**
|
||||
|
||||
- How findings will feed into next phases
|
||||
- Which team members should review results
|
||||
- How to validate findings
|
||||
- When to revisit or expand research
|
||||
|
||||
## Important Notes
|
||||
|
||||
- The quality of the research prompt directly impacts the quality of insights gathered
|
||||
- Be specific rather than general in research questions
|
||||
- Consider both current state and future implications
|
||||
- Balance comprehensiveness with focus
|
||||
- Document assumptions and limitations clearly
|
||||
- Plan for iterative refinement based on initial findings
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user