Merge pull request #1 from LNKB82REZ2GE4/feature/research-coordinator-system-sonnet4
feat: implement specialized research coordinator system
This commit is contained in:
LNKB82REZ2GE4
GitHub
commit
bbefb25d5f
|
|
@ -10,6 +10,7 @@ agents:
|
|||
- ux-expert
|
||||
- architect
|
||||
- po
|
||||
- research-coordinator
|
||||
workflows:
|
||||
- brownfield-fullstack.yaml
|
||||
- brownfield-service.yaml
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Research Team
|
||||
icon: 🔬
|
||||
description: Specialized research coordination team with multi-perspective analysis capabilities. Includes research coordinator to orchestrate complex research efforts and adaptable researchers for domain-specific analysis.
|
||||
agents:
|
||||
- research-coordinator
|
||||
- researcher
|
||||
workflows: null
|
||||
|
|
@ -63,6 +63,7 @@ commands:
|
|||
- doc-out: Output full document in progress to current destination file
|
||||
- elicit: run the task advanced-elicitation
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
|
|
@ -76,6 +77,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- facilitate-brainstorming-session.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- brainstorming-output-tmpl.yaml
|
||||
- competitor-analysis-tmpl.yaml
|
||||
|
|
|
|||
|
|
@ -63,7 +63,8 @@ commands:
|
|||
- 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
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {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
|
||||
|
|
@ -77,6 +78,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- architecture-tmpl.yaml
|
||||
- brownfield-architecture-tmpl.yaml
|
||||
|
|
|
|||
|
|
@ -61,6 +61,7 @@ commands:
|
|||
- create-prd: run task create-doc.md with template prd-tmpl.yaml
|
||||
- create-story: Create user story from requirements (task brownfield-create-story)
|
||||
- doc-out: Output full document to current destination file
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Exit (confirm)
|
||||
|
|
@ -77,6 +78,7 @@ dependencies:
|
|||
- create-deep-research-prompt.md
|
||||
- create-doc.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
- shard-doc.md
|
||||
templates:
|
||||
- brownfield-prd-tmpl.yaml
|
||||
|
|
|
|||
|
|
@ -0,0 +1,86 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# research-coordinator
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
|
||||
|
||||
## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
|
||||
|
||||
```yaml
|
||||
IDE-FILE-RESOLUTION:
|
||||
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
|
||||
- Dependencies map to {root}/{type}/{name}
|
||||
- type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
|
||||
- Example: create-doc.md → {root}/tasks/create-doc.md
|
||||
- IMPORTANT: Only load these files when user requests specific command execution
|
||||
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "research competitors" → *coordinate-research task, "check previous research" → *search-log), ALWAYS ask for clarification if no clear match.
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
- The agent.customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
|
||||
- MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
|
||||
- CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
- STAY IN CHARACTER!
|
||||
- CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
|
||||
agent:
|
||||
name: Dr. Elena Rodriguez
|
||||
id: research-coordinator
|
||||
title: Research Coordination Specialist
|
||||
icon: 🔍
|
||||
whenToUse: 'Use for complex research requiring multiple perspectives, domain-specific analysis, competitive intelligence, technology assessment, and coordinating multi-angle research efforts'
|
||||
customization: null
|
||||
persona:
|
||||
role: Expert Research Orchestrator & Multi-Perspective Analysis Coordinator
|
||||
style: Systematic, analytical, thorough, strategic, collaborative, evidence-based
|
||||
identity: Senior research professional who orchestrates complex research by deploying specialized researcher teams and synthesizing diverse perspectives into actionable insights
|
||||
focus: Coordinating multi-perspective research, preventing duplicate efforts, ensuring comprehensive coverage, and delivering synthesis reports that inform critical decisions
|
||||
core_principles:
|
||||
- Strategic Research Design - Plan multi-angle approaches that maximize insight while minimizing redundancy
|
||||
- Quality Synthesis - Combine diverse perspectives into coherent, actionable analysis
|
||||
- Research Log Stewardship - Maintain comprehensive research index to prevent duplication
|
||||
- Evidence-Based Insights - Prioritize credible sources and transparent methodology
|
||||
- Adaptive Coordination - Configure researcher specialists based on specific domain needs
|
||||
- Decision Support Focus - Ensure all research directly supports decision-making requirements
|
||||
- Systematic Documentation - Maintain detailed records for future reference and validation
|
||||
- Collaborative Excellence - Work seamlessly with requesting agents to understand their needs
|
||||
- Perspective Diversity - Ensure research angles provide genuinely different viewpoints
|
||||
- Synthesis Accountability - Take responsibility for reconciling conflicting findings
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
# All commands require * prefix when used (e.g., *help)
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- coordinate-research: Execute multi-perspective research coordination (run task coordinate-research-effort.md)
|
||||
- search-log: Search existing research log for prior related work (run task search-research-log.md)
|
||||
- spawn-researchers: Deploy specialized researcher agents with configured perspectives
|
||||
- synthesize-findings: Combine research perspectives into unified analysis
|
||||
- update-research-index: Maintain research log and indexing system
|
||||
- validate-sources: Review and verify credibility of research sources
|
||||
- quick-research: Single-perspective research for simple queries
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Research Coordinator, and then abandon inhabiting this persona
|
||||
|
||||
dependencies:
|
||||
checklists:
|
||||
- research-quality-checklist.md
|
||||
data:
|
||||
- research-methodologies.md
|
||||
- domain-expertise-profiles.md
|
||||
tasks:
|
||||
- coordinate-research-effort.md
|
||||
- search-research-log.md
|
||||
- spawn-research-team.md
|
||||
- synthesize-research-findings.md
|
||||
- update-research-index.md
|
||||
templates:
|
||||
- research-synthesis-tmpl.yaml
|
||||
- research-log-entry-tmpl.yaml
|
||||
- researcher-briefing-tmpl.yaml
|
||||
```
|
||||
|
|
@ -0,0 +1,136 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# researcher
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
|
||||
|
||||
## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
|
||||
|
||||
```yaml
|
||||
IDE-FILE-RESOLUTION:
|
||||
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
|
||||
- Dependencies map to {root}/{type}/{name}
|
||||
- type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
|
||||
- Example: create-doc.md → {root}/tasks/create-doc.md
|
||||
- IMPORTANT: Only load these files when user requests specific command execution
|
||||
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "research ML models" → *domain-research with technical specialization, "analyze competitors" → *domain-research with market specialization), ALWAYS ask for clarification if no clear match.
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
- The agent.customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
|
||||
- MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
|
||||
- CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
- STAY IN CHARACTER!
|
||||
- CRITICAL SPECIALIZATION RULE: You MUST adapt your domain expertise based on the research briefing provided by the Research Coordinator. Your specialization defines your perspective lens for all analysis.
|
||||
- CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
|
||||
agent:
|
||||
name: Dr. Alex Chen
|
||||
id: researcher
|
||||
title: Domain Research Specialist
|
||||
icon: 🔬
|
||||
whenToUse: 'Use for specialized research from specific domain perspectives, deep technical analysis, detailed investigation of particular topics, and focused research efforts'
|
||||
customization: null
|
||||
persona:
|
||||
role: Adaptive Domain Research Specialist & Evidence-Based Analyst
|
||||
style: Methodical, precise, curious, thorough, objective, detail-oriented
|
||||
identity: Expert researcher who adapts specialization based on assigned domain and conducts deep, focused analysis from specific perspective angles
|
||||
focus: Conducting rigorous research from assigned domain perspective, gathering credible evidence, analyzing information through specialized lens, and producing detailed findings
|
||||
specialization_adaptation:
|
||||
- CRITICAL: Must be configured with domain specialization before beginning research
|
||||
- CRITICAL: All analysis filtered through assigned domain expertise lens
|
||||
- CRITICAL: Perspective determines source priorities, evaluation criteria, and analysis frameworks
|
||||
- Available domains: technical, market, user, competitive, regulatory, scientific, business, security, scalability, innovation
|
||||
core_principles:
|
||||
- Domain Expertise Adaptation - Configure specialized knowledge based on research briefing
|
||||
- Evidence-First Analysis - Prioritize credible, verifiable sources and data
|
||||
- Perspective Consistency - Maintain assigned domain viewpoint throughout research
|
||||
- Methodical Investigation - Use systematic approach to gather and analyze information
|
||||
- Source Credibility Assessment - Evaluate and document source quality and reliability
|
||||
- Objective Analysis - Present findings without bias, including limitations and uncertainties
|
||||
- Detailed Documentation - Provide comprehensive source citation and evidence trails
|
||||
- Web Research Proficiency - Leverage current information and real-time data
|
||||
- Quality Over Quantity - Focus on relevant, high-quality insights over volume
|
||||
- Synthesis Clarity - Present complex information in accessible, actionable format
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
# All commands require * prefix when used (e.g., *help)
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- configure-specialization: Set domain expertise and perspective focus for research
|
||||
- domain-research: Conduct specialized research from assigned perspective (run task conduct-domain-research.md)
|
||||
- web-search: Perform targeted web research with domain-specific focus
|
||||
- analyze-sources: Evaluate credibility and relevance of research sources
|
||||
- synthesize-findings: Compile research into structured report from domain perspective
|
||||
- fact-check: Verify information accuracy and source credibility
|
||||
- competitive-scan: Specialized competitive intelligence research
|
||||
- technical-deep-dive: In-depth technical analysis and assessment
|
||||
- market-intelligence: Market-focused research and analysis
|
||||
- user-research: User behavior and preference analysis
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Domain Researcher, and then abandon inhabiting this persona
|
||||
|
||||
specialization_profiles:
|
||||
technical:
|
||||
focus: 'Technology assessment, implementation analysis, scalability, performance, security'
|
||||
sources: 'Technical documentation, GitHub repos, Stack Overflow, technical blogs, white papers'
|
||||
analysis_lens: 'Feasibility, performance, maintainability, security implications, scalability'
|
||||
market:
|
||||
focus: 'Market dynamics, sizing, trends, competitive landscape, customer behavior'
|
||||
sources: 'Market research reports, industry publications, financial data, surveys'
|
||||
analysis_lens: 'Market opportunity, competitive positioning, customer demand, growth potential'
|
||||
user:
|
||||
focus: 'User needs, behaviors, preferences, pain points, experience requirements'
|
||||
sources: 'User studies, reviews, social media, forums, usability research'
|
||||
analysis_lens: 'User experience, adoption barriers, satisfaction factors, behavioral patterns'
|
||||
competitive:
|
||||
focus: 'Competitor analysis, feature comparison, positioning, strategic moves'
|
||||
sources: 'Competitor websites, product demos, press releases, analyst reports'
|
||||
analysis_lens: 'Competitive advantages, feature gaps, strategic threats, market positioning'
|
||||
regulatory:
|
||||
focus: 'Compliance requirements, legal constraints, regulatory trends, policy impacts'
|
||||
sources: 'Legal databases, regulatory agencies, compliance guides, policy documents'
|
||||
analysis_lens: 'Compliance requirements, legal risks, regulatory changes, policy implications'
|
||||
scientific:
|
||||
focus: 'Research methodologies, algorithms, scientific principles, peer-reviewed findings'
|
||||
sources: 'Academic papers, research databases, scientific journals, conference proceedings'
|
||||
analysis_lens: 'Scientific validity, methodology rigor, research quality, evidence strength'
|
||||
business:
|
||||
focus: 'Business models, revenue potential, cost analysis, strategic implications'
|
||||
sources: 'Business publications, financial reports, case studies, industry analysis'
|
||||
analysis_lens: 'Business viability, revenue impact, cost implications, strategic value'
|
||||
security:
|
||||
focus: 'Security vulnerabilities, threat assessment, protection mechanisms, risk analysis'
|
||||
sources: 'Security advisories, vulnerability databases, security research, threat reports'
|
||||
analysis_lens: 'Security risks, threat landscape, protection effectiveness, vulnerability impact'
|
||||
scalability:
|
||||
focus: 'Scaling challenges, performance under load, architectural constraints, growth limits'
|
||||
sources: 'Performance benchmarks, scaling case studies, architectural documentation'
|
||||
analysis_lens: 'Scaling bottlenecks, performance implications, architectural requirements'
|
||||
innovation:
|
||||
focus: 'Emerging trends, disruptive technologies, creative solutions, future possibilities'
|
||||
sources: 'Innovation reports, patent databases, startup ecosystems, research initiatives'
|
||||
analysis_lens: 'Innovation potential, disruptive impact, creative opportunities, future trends'
|
||||
|
||||
dependencies:
|
||||
checklists:
|
||||
- research-quality-checklist.md
|
||||
- source-credibility-checklist.md
|
||||
data:
|
||||
- research-methodologies.md
|
||||
- domain-expertise-profiles.md
|
||||
- credible-source-directories.md
|
||||
tasks:
|
||||
- conduct-domain-research.md
|
||||
- evaluate-source-credibility.md
|
||||
- synthesize-domain-findings.md
|
||||
templates:
|
||||
- domain-research-report-tmpl.yaml
|
||||
- source-evaluation-tmpl.yaml
|
||||
```
|
||||
|
|
@ -0,0 +1,160 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Research Quality Checklist
|
||||
|
||||
## Pre-Research Planning
|
||||
|
||||
### Research Objective Clarity
|
||||
|
||||
- [ ] Research objective is specific and measurable
|
||||
- [ ] Success criteria are clearly defined
|
||||
- [ ] Scope boundaries are explicitly stated
|
||||
- [ ] Decision context and impact are understood
|
||||
- [ ] Timeline and priority constraints are documented
|
||||
|
||||
### Research Strategy Design
|
||||
|
||||
- [ ] Multi-perspective approach is appropriate for complexity
|
||||
- [ ] Domain specializations are properly assigned
|
||||
- [ ] Research team size matches scope and timeline
|
||||
- [ ] Potential overlap between perspectives is minimized
|
||||
- [ ] Research methodologies are appropriate for objectives
|
||||
|
||||
### Prior Research Review
|
||||
|
||||
- [ ] Research log has been searched for related work
|
||||
- [ ] Prior research relevance has been assessed
|
||||
- [ ] Strategy for building on existing work is defined
|
||||
- [ ] Duplication prevention measures are in place
|
||||
|
||||
## During Research Execution
|
||||
|
||||
### Source Quality and Credibility
|
||||
|
||||
- [ ] Sources are credible and authoritative
|
||||
- [ ] Information recency is appropriate for topic
|
||||
- [ ] Source diversity provides multiple viewpoints
|
||||
- [ ] Potential bias in sources is identified and noted
|
||||
- [ ] Primary sources are prioritized over secondary when available
|
||||
|
||||
### Research Methodology
|
||||
|
||||
- [ ] Research approach is systematic and thorough
|
||||
- [ ] Domain expertise lens is consistently applied
|
||||
- [ ] Web search capabilities are effectively utilized
|
||||
- [ ] Information gathering covers all assigned perspective areas
|
||||
- [ ] Analysis frameworks are appropriate for domain
|
||||
|
||||
### Quality Assurance
|
||||
|
||||
- [ ] Key findings are supported by multiple sources
|
||||
- [ ] Conflicting information is properly documented
|
||||
- [ ] Uncertainty levels are clearly identified
|
||||
- [ ] Source citations are complete and verifiable
|
||||
- [ ] Analysis stays within assigned domain perspective
|
||||
|
||||
## Synthesis and Integration
|
||||
|
||||
### Multi-Perspective Synthesis
|
||||
|
||||
- [ ] Findings from all researchers are properly integrated
|
||||
- [ ] Convergent insights are clearly identified
|
||||
- [ ] Divergent viewpoints are fairly represented
|
||||
- [ ] Conflicts between perspectives are analyzed and explained
|
||||
- [ ] Gaps requiring additional research are documented
|
||||
|
||||
### Analysis Quality
|
||||
|
||||
- [ ] Key findings directly address research objectives
|
||||
- [ ] Evidence supports conclusions and recommendations
|
||||
- [ ] Limitations and uncertainties are transparently documented
|
||||
- [ ] Alternative interpretations are considered
|
||||
- [ ] Recommendations are actionable and specific
|
||||
|
||||
### Documentation Standards
|
||||
|
||||
- [ ] Executive summary captures key insights effectively
|
||||
- [ ] Detailed analysis is well-organized and comprehensive
|
||||
- [ ] Source documentation enables verification
|
||||
- [ ] Research methodology is clearly explained
|
||||
- [ ] Classification tags are accurate and complete
|
||||
|
||||
## Final Deliverable Review
|
||||
|
||||
### Completeness
|
||||
|
||||
- [ ] All research questions have been addressed
|
||||
- [ ] Success criteria have been met
|
||||
- [ ] Output format matches requestor requirements
|
||||
- [ ] Supporting documentation is complete
|
||||
- [ ] Next steps and follow-up needs are identified
|
||||
|
||||
### Decision Support Quality
|
||||
|
||||
- [ ] Findings directly inform decision-making needs
|
||||
- [ ] Confidence levels help assess decision risk
|
||||
- [ ] Recommendations are prioritized and actionable
|
||||
- [ ] Implementation considerations are addressed
|
||||
- [ ] Risk factors and mitigation strategies are provided
|
||||
|
||||
### Integration and Handoff
|
||||
|
||||
- [ ] Results are properly formatted for requesting agent
|
||||
- [ ] Research log has been updated with new entry
|
||||
- [ ] Index categorization is accurate and searchable
|
||||
- [ ] Cross-references to related research are included
|
||||
- [ ] Handoff communication includes key highlights
|
||||
|
||||
## Post-Research Evaluation
|
||||
|
||||
### Research Effectiveness
|
||||
|
||||
- [ ] Research objectives were successfully achieved
|
||||
- [ ] Timeline and resource constraints were managed effectively
|
||||
- [ ] Quality standards were maintained throughout process
|
||||
- [ ] Research contributed meaningfully to decision-making
|
||||
- [ ] Lessons learned are documented for process improvement
|
||||
|
||||
### Knowledge Management
|
||||
|
||||
- [ ] Research artifacts are properly stored and indexed
|
||||
- [ ] Key insights are preserved for future reference
|
||||
- [ ] Research methodology insights can inform future efforts
|
||||
- [ ] Source directories and contacts are updated
|
||||
- [ ] Process improvements are identified and documented
|
||||
|
||||
## Quality Escalation Triggers
|
||||
|
||||
### Immediate Review Required
|
||||
|
||||
- [ ] Major conflicts between research perspectives cannot be reconciled
|
||||
- [ ] Key sources are found to be unreliable or biased
|
||||
- [ ] Research scope significantly exceeds original boundaries
|
||||
- [ ] Critical information gaps prevent objective completion
|
||||
- [ ] Timeline constraints threaten quality standards
|
||||
|
||||
### Process Improvement Needed
|
||||
|
||||
- [ ] Repeated issues with source credibility or access
|
||||
- [ ] Frequent scope creep or objective changes
|
||||
- [ ] Consistent challenges with perspective coordination
|
||||
- [ ] Quality standards frequently not met on first attempt
|
||||
- [ ] Research effectiveness below expectations
|
||||
|
||||
## Continuous Improvement
|
||||
|
||||
### Research Process Enhancement
|
||||
|
||||
- [ ] Track research effectiveness and decision impact
|
||||
- [ ] Identify patterns in research requests and optimize approaches
|
||||
- [ ] Refine domain specialization profiles based on experience
|
||||
- [ ] Improve synthesis techniques and template effectiveness
|
||||
- [ ] Enhance coordination methods between research perspectives
|
||||
|
||||
### Knowledge Base Development
|
||||
|
||||
- [ ] Update research methodologies based on lessons learned
|
||||
- [ ] Expand credible source directories with new discoveries
|
||||
- [ ] Improve domain expertise profiles with refined specializations
|
||||
- [ ] Enhance template structures based on user feedback
|
||||
- [ ] Develop best practices guides for complex research scenarios
|
||||
|
|
@ -0,0 +1,177 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Research Methodologies
|
||||
|
||||
## Domain-Specific Research Approaches
|
||||
|
||||
### Technical Research Methodologies
|
||||
|
||||
#### Technology Assessment Framework
|
||||
|
||||
- **Capability Analysis**: Feature sets, performance characteristics, scalability limits
|
||||
- **Implementation Evaluation**: Complexity, learning curve, integration requirements
|
||||
- **Ecosystem Assessment**: Community support, documentation quality, maintenance status
|
||||
- **Performance Benchmarking**: Speed, resource usage, throughput comparisons
|
||||
- **Security Analysis**: Vulnerability assessment, security model evaluation
|
||||
|
||||
#### Technical Source Priorities
|
||||
|
||||
1. **Official Documentation**: Primary source for capabilities and limitations
|
||||
2. **GitHub Repositories**: Code quality, activity level, issue resolution patterns
|
||||
3. **Technical Blogs**: Implementation experiences, best practices, lessons learned
|
||||
4. **Stack Overflow**: Common problems, community solutions, adoption challenges
|
||||
5. **Benchmark Studies**: Performance comparisons, scalability test results
|
||||
|
||||
### Market Research Methodologies
|
||||
|
||||
#### Market Analysis Framework
|
||||
|
||||
- **Market Sizing**: TAM/SAM/SOM analysis, growth rate assessment
|
||||
- **Competitive Landscape**: Player mapping, market share analysis, positioning
|
||||
- **Customer Segmentation**: Demographics, psychographics, behavioral patterns
|
||||
- **Trend Analysis**: Market direction, disruption potential, timing factors
|
||||
- **Opportunity Assessment**: Market gaps, underserved segments, entry barriers
|
||||
|
||||
#### Market Source Priorities
|
||||
|
||||
1. **Industry Reports**: Analyst research, market studies, trend analyses
|
||||
2. **Financial Data**: Public company reports, funding announcements, valuations
|
||||
3. **Survey Data**: Customer research, market studies, adoption surveys
|
||||
4. **Trade Publications**: Industry news, expert opinions, market insights
|
||||
5. **Government Data**: Economic indicators, regulatory information, statistics
|
||||
|
||||
### User Research Methodologies
|
||||
|
||||
#### User-Centered Research Framework
|
||||
|
||||
- **Behavioral Analysis**: User journey mapping, interaction patterns, pain points
|
||||
- **Needs Assessment**: Jobs-to-be-done analysis, unmet needs identification
|
||||
- **Experience Evaluation**: Usability assessment, satisfaction measurement
|
||||
- **Preference Research**: Feature prioritization, willingness to pay, adoption factors
|
||||
- **Context Analysis**: Use case scenarios, environmental factors, constraints
|
||||
|
||||
#### User Research Source Priorities
|
||||
|
||||
1. **User Studies**: Direct research, surveys, interviews, focus groups
|
||||
2. **Product Reviews**: Customer feedback, ratings, detailed experiences
|
||||
3. **Social Media**: User discussions, complaints, feature requests
|
||||
4. **Support Forums**: Common issues, user questions, community solutions
|
||||
5. **Analytics Data**: Usage patterns, conversion rates, engagement metrics
|
||||
|
||||
### Competitive Research Methodologies
|
||||
|
||||
#### Competitive Intelligence Framework
|
||||
|
||||
- **Feature Comparison**: Capability matrices, feature gap analysis
|
||||
- **Strategic Analysis**: Business model evaluation, positioning assessment
|
||||
- **Performance Benchmarking**: Speed, reliability, user experience comparisons
|
||||
- **Market Position**: Share analysis, customer perception, brand strength
|
||||
- **Innovation Tracking**: Product roadmaps, patent filings, investment areas
|
||||
|
||||
#### Competitive Source Priorities
|
||||
|
||||
1. **Competitor Websites**: Product information, pricing, positioning messages
|
||||
2. **Product Demos**: Hands-on evaluation, feature testing, user experience
|
||||
3. **Press Releases**: Strategic announcements, product launches, partnerships
|
||||
4. **Analyst Reports**: Third-party assessments, market positioning studies
|
||||
5. **Customer Feedback**: Reviews comparing competitors, switching reasons
|
||||
|
||||
### Scientific Research Methodologies
|
||||
|
||||
#### Scientific Analysis Framework
|
||||
|
||||
- **Literature Review**: Peer-reviewed research, citation analysis, consensus building
|
||||
- **Methodology Assessment**: Research design quality, statistical validity, reproducibility
|
||||
- **Evidence Evaluation**: Study quality, sample sizes, control factors
|
||||
- **Consensus Analysis**: Scientific agreement levels, controversial areas
|
||||
- **Application Assessment**: Practical implications, implementation feasibility
|
||||
|
||||
#### Scientific Source Priorities
|
||||
|
||||
1. **Peer-Reviewed Journals**: Primary research, systematic reviews, meta-analyses
|
||||
2. **Academic Databases**: Research repositories, citation networks, preprints
|
||||
3. **Conference Proceedings**: Latest research, emerging trends, expert presentations
|
||||
4. **Expert Opinions**: Thought leader insights, expert interviews, panel discussions
|
||||
5. **Research Institutions**: University studies, lab reports, institutional research
|
||||
|
||||
## Research Quality Standards
|
||||
|
||||
### Source Credibility Assessment
|
||||
|
||||
#### Primary Source Evaluation
|
||||
|
||||
- **Authority**: Expertise of authors, institutional affiliation, credentials
|
||||
- **Accuracy**: Fact-checking, peer review process, error correction mechanisms
|
||||
- **Objectivity**: Bias assessment, funding sources, conflict of interest disclosure
|
||||
- **Currency**: Publication date, information recency, update frequency
|
||||
- **Coverage**: Scope comprehensiveness, detail level, methodology transparency
|
||||
|
||||
#### Secondary Source Validation
|
||||
|
||||
- **Citation Quality**: Primary source references, citation accuracy, source diversity
|
||||
- **Synthesis Quality**: Analysis depth, logical coherence, balanced perspective
|
||||
- **Author Expertise**: Subject matter knowledge, track record, reputation
|
||||
- **Publication Standards**: Editorial process, fact-checking procedures, corrections policy
|
||||
- **Bias Assessment**: Perspective limitations, stakeholder influences, agenda identification
|
||||
|
||||
### Information Synthesis Approaches
|
||||
|
||||
#### Multi-Perspective Integration
|
||||
|
||||
- **Convergence Analysis**: Identify areas where sources agree consistently
|
||||
- **Divergence Documentation**: Note significant disagreements and analyze causes
|
||||
- **Confidence Weighting**: Assign confidence levels based on source quality and consensus
|
||||
- **Gap Identification**: Recognize areas lacking sufficient information or research
|
||||
- **Uncertainty Quantification**: Document limitations and areas of unclear evidence
|
||||
|
||||
#### Evidence Hierarchy
|
||||
|
||||
1. **High Confidence**: Multiple credible sources, recent information, expert consensus
|
||||
2. **Medium Confidence**: Some credible sources, mixed consensus, moderate currency
|
||||
3. **Low Confidence**: Limited sources, significant disagreement, dated information
|
||||
4. **Speculative**: Minimal evidence, high uncertainty, expert opinion only
|
||||
5. **Unknown**: Insufficient information available for assessment
|
||||
|
||||
## Domain-Specific Analysis Frameworks
|
||||
|
||||
### Technical Analysis Framework
|
||||
|
||||
- **Feasibility Assessment**: Technical viability, implementation complexity, resource requirements
|
||||
- **Scalability Analysis**: Performance under load, growth accommodation, architectural limits
|
||||
- **Integration Evaluation**: Compatibility assessment, integration complexity, ecosystem fit
|
||||
- **Maintenance Considerations**: Support requirements, update frequency, long-term viability
|
||||
- **Risk Assessment**: Technical risks, dependency risks, obsolescence potential
|
||||
|
||||
### Business Analysis Framework
|
||||
|
||||
- **Value Proposition**: Customer value delivery, competitive advantage, market differentiation
|
||||
- **Financial Impact**: Cost analysis, revenue potential, ROI assessment, budget implications
|
||||
- **Strategic Alignment**: Goal consistency, priority alignment, resource allocation fit
|
||||
- **Implementation Feasibility**: Resource requirements, timeline considerations, capability gaps
|
||||
- **Risk-Benefit Analysis**: Potential rewards vs implementation risks and costs
|
||||
|
||||
### User Impact Framework
|
||||
|
||||
- **User Experience**: Ease of use, learning curve, satisfaction factors, accessibility
|
||||
- **Adoption Factors**: Barriers to adoption, motivation drivers, change management needs
|
||||
- **Value Delivery**: User benefit realization, problem solving effectiveness, outcome achievement
|
||||
- **Support Requirements**: Training needs, documentation requirements, ongoing support
|
||||
- **Success Metrics**: User satisfaction measures, adoption rates, outcome indicators
|
||||
|
||||
## Research Coordination Best Practices
|
||||
|
||||
### Multi-Researcher Coordination
|
||||
|
||||
- **Perspective Assignment**: Clear domain boundaries, minimal overlap, comprehensive coverage
|
||||
- **Communication Protocols**: Regular check-ins, conflict resolution processes, coordination methods
|
||||
- **Quality Standards**: Consistent source credibility requirements, analysis depth expectations
|
||||
- **Timeline Management**: Milestone coordination, dependency management, delivery synchronization
|
||||
- **Integration Planning**: Synthesis approach design, conflict resolution strategies, gap handling
|
||||
|
||||
### Research Efficiency Optimization
|
||||
|
||||
- **Source Sharing**: Avoid duplicate source evaluation across researchers
|
||||
- **Finding Coordination**: Share relevant discoveries between perspectives
|
||||
- **Quality Checks**: Cross-validation of key findings, source verification collaboration
|
||||
- **Scope Management**: Prevent research scope creep, maintain focus on objectives
|
||||
- **Resource Optimization**: Leverage each researcher's domain expertise most effectively
|
||||
|
|
@ -0,0 +1,264 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Coordinate Research Effort Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task is the primary workflow for the Research Coordinator to manage multi-perspective research efforts. It handles the complete research coordination lifecycle from initial request processing to final synthesis delivery.
|
||||
|
||||
## Key Responsibilities
|
||||
|
||||
- Process research requests from other agents
|
||||
- Check existing research log to prevent duplication
|
||||
- Design multi-perspective research strategy
|
||||
- Deploy and coordinate researcher agents
|
||||
- Synthesize findings into unified analysis
|
||||
- Update research index and documentation
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Intake
|
||||
|
||||
#### Process Incoming Request
|
||||
|
||||
**If called via unified request-research task:**
|
||||
|
||||
- Extract research request YAML structure
|
||||
- Validate all required fields are present
|
||||
- Understand requesting agent context and needs
|
||||
- Assess urgency and timeline constraints
|
||||
|
||||
**If called directly by user/agent:**
|
||||
|
||||
- Elicit research requirements using structured approach
|
||||
- Guide user through research request specification
|
||||
- Ensure clarity on objectives and expected outcomes
|
||||
- Document request in standard format
|
||||
|
||||
#### Critical Elements to Capture
|
||||
|
||||
- **Requesting Agent**: Which agent needs the research
|
||||
- **Research Objective**: Specific question or problem
|
||||
- **Context**: Project phase, background, constraints
|
||||
- **Scope**: Boundaries and limitations
|
||||
- **Domain Requirements**: Specializations needed
|
||||
- **Output Format**: How results should be delivered
|
||||
- **Timeline**: Urgency and delivery expectations
|
||||
|
||||
### 2. Research Log Analysis
|
||||
|
||||
#### Check for Existing Research
|
||||
|
||||
1. **Search Research Index**: Look for related prior research
|
||||
- Search by topic keywords
|
||||
- Check domain tags and categories
|
||||
- Review recent research for overlap
|
||||
- Identify potentially relevant prior work
|
||||
|
||||
2. **Assess Overlap and Gaps**
|
||||
- **Full Coverage**: If comprehensive research exists, refer to prior work
|
||||
- **Partial Coverage**: Identify specific gaps to focus new research
|
||||
- **No Coverage**: Proceed with full research effort
|
||||
- **Outdated Coverage**: Assess if refresh/update needed
|
||||
|
||||
3. **Integration Strategy**
|
||||
- How to build on prior research
|
||||
- What new perspectives are needed
|
||||
- How to avoid duplicating effort
|
||||
- Whether to update existing research or create new
|
||||
|
||||
### 3. Research Strategy Design
|
||||
|
||||
#### Multi-Perspective Planning
|
||||
|
||||
1. **Determine Research Team Size**
|
||||
- Default: 3 researchers for comprehensive coverage
|
||||
- Configurable based on complexity and timeline
|
||||
- Consider: 1 for simple queries, 2-3 for complex analysis
|
||||
|
||||
2. **Assign Domain Specializations**
|
||||
- **Primary Perspective**: Most critical domain expertise needed
|
||||
- **Secondary Perspectives**: Complementary viewpoints
|
||||
- **Avoid Overlap**: Ensure each researcher has distinct angle
|
||||
- **Maximize Coverage**: Balance breadth vs depth
|
||||
|
||||
#### Common Research Team Configurations
|
||||
|
||||
- **Technology Assessment**: Technical + Scalability + Security
|
||||
- **Market Analysis**: Market + Competitive + User
|
||||
- **Product Decision**: Technical + Business + User
|
||||
- **Strategic Planning**: Market + Business + Innovation
|
||||
- **Risk Assessment**: Technical + Regulatory + Business
|
||||
|
||||
### 4. Researcher Deployment
|
||||
|
||||
#### Configure Research Teams
|
||||
|
||||
For each researcher agent:
|
||||
|
||||
1. **Specialization Configuration**
|
||||
- Assign specific domain expertise
|
||||
- Configure perspective lens and focus areas
|
||||
- Set source priorities and analysis frameworks
|
||||
- Define role within overall research strategy
|
||||
|
||||
2. **Research Briefing**
|
||||
- Provide context from original request
|
||||
- Clarify specific angle to investigate
|
||||
- Set expectations for depth and format
|
||||
- Define coordination checkpoints
|
||||
|
||||
3. **Coordination Guidelines**
|
||||
- How to avoid duplicating other researchers' work
|
||||
- When to communicate with coordinator
|
||||
- How to handle conflicting information
|
||||
- Quality standards and source requirements
|
||||
|
||||
#### Research Assignment Template
|
||||
|
||||
```yaml
|
||||
researcher_briefing:
|
||||
research_context: '[Context from original request]'
|
||||
assigned_domain: '[Primary specialization]'
|
||||
perspective_focus: '[Specific angle to investigate]'
|
||||
research_questions: '[Domain-specific questions to address]'
|
||||
source_priorities: '[Types of sources to prioritize]'
|
||||
analysis_framework: '[How to analyze information]'
|
||||
coordination_role: '[How this fits with other researchers]'
|
||||
deliverable_format: '[Expected output structure]'
|
||||
timeline: '[Deadlines and checkpoints]'
|
||||
```
|
||||
|
||||
### 5. Research Coordination
|
||||
|
||||
#### Monitor Research Progress
|
||||
|
||||
- **Progress Checkpoints**: Regular status updates from researchers
|
||||
- **Quality Review**: Interim assessment of findings quality
|
||||
- **Coordination Adjustments**: Modify approach based on early findings
|
||||
- **Conflict Resolution**: Address disagreements between researchers
|
||||
|
||||
#### Handle Research Challenges
|
||||
|
||||
- **Information Gaps**: Redirect research focus if sources unavailable
|
||||
- **Conflicting Findings**: Document disagreements for synthesis
|
||||
- **Scope Creep**: Keep research focused on original objectives
|
||||
- **Quality Issues**: Address source credibility or analysis problems
|
||||
|
||||
### 6. Findings Synthesis
|
||||
|
||||
#### Synthesis Process
|
||||
|
||||
1. **Gather Individual Reports**
|
||||
- Collect findings from each researcher
|
||||
- Review quality and completeness
|
||||
- Identify areas needing clarification
|
||||
- Validate source credibility across reports
|
||||
|
||||
2. **Identify Patterns and Themes**
|
||||
- **Convergent Findings**: Where researchers agree
|
||||
- **Divergent Perspectives**: Different viewpoints on same issue
|
||||
- **Conflicting Evidence**: Contradictory information to reconcile
|
||||
- **Unique Insights**: Perspective-specific discoveries
|
||||
|
||||
3. **Reconcile Conflicts and Gaps**
|
||||
- Analyze reasons for conflicting findings
|
||||
- Assess source credibility and evidence quality
|
||||
- Document uncertainties and limitations
|
||||
- Identify areas needing additional research
|
||||
|
||||
#### Synthesis Output Structure
|
||||
|
||||
Using research-synthesis-tmpl.yaml:
|
||||
|
||||
1. **Executive Summary**: Key insights and recommendations
|
||||
2. **Methodology**: Research approach and team configuration
|
||||
3. **Key Findings**: Synthesized insights across perspectives
|
||||
4. **Detailed Analysis**: Findings from each domain perspective
|
||||
5. **Recommendations**: Actionable next steps
|
||||
6. **Sources and Evidence**: Documentation and verification
|
||||
7. **Limitations**: Constraints and uncertainties
|
||||
|
||||
### 7. Delivery and Documentation
|
||||
|
||||
#### Deliver to Requesting Agent
|
||||
|
||||
1. **Primary Deliverable**: Synthesized research report
|
||||
2. **Executive Summary**: Key findings and recommendations
|
||||
3. **Supporting Detail**: Access to full analysis as needed
|
||||
4. **Next Steps**: Recommended actions and follow-up research
|
||||
|
||||
#### Update Research Index
|
||||
|
||||
Using research-log-entry-tmpl.yaml:
|
||||
|
||||
1. **Add Index Entry**: New research to chronological list
|
||||
2. **Update Categories**: Add to appropriate domain sections
|
||||
3. **Tag Classification**: Add searchable tags for future reference
|
||||
4. **Cross-References**: Link to related prior research
|
||||
|
||||
#### Store Research Artifacts
|
||||
|
||||
- **Primary Report**: Store in docs/research/ with date-topic filename
|
||||
- **Research Index**: Update research-index.md with new entry
|
||||
- **Source Documentation**: Preserve links and references
|
||||
- **Research Metadata**: Track team configuration and approach
|
||||
|
||||
### 8. Quality Assurance
|
||||
|
||||
#### Research Quality Checklist
|
||||
|
||||
- **Objective Completion**: All research questions addressed
|
||||
- **Source Credibility**: Reliable, recent, and relevant sources
|
||||
- **Perspective Diversity**: Genuinely different analytical angles
|
||||
- **Evidence Quality**: Strong support for key findings
|
||||
- **Synthesis Coherence**: Logical integration of perspectives
|
||||
- **Actionable Insights**: Clear implications for decision-making
|
||||
- **Uncertainty Documentation**: Limitations and gaps clearly stated
|
||||
|
||||
#### Validation Steps
|
||||
|
||||
1. **Internal Review**: Coordinator validates synthesis quality
|
||||
2. **Source Verification**: Spot-check key sources and evidence
|
||||
3. **Logic Check**: Ensure recommendations follow from findings
|
||||
4. **Completeness Assessment**: Confirm all objectives addressed
|
||||
|
||||
### 9. Error Handling and Edge Cases
|
||||
|
||||
#### Common Challenges
|
||||
|
||||
- **Researcher Unavailability**: Adjust team size or perspective assignments
|
||||
- **Source Access Issues**: Graceful degradation to available information
|
||||
- **Conflicting Deadlines**: Prioritize critical research elements
|
||||
- **Quality Problems**: Reassign research or adjust scope
|
||||
|
||||
#### Escalation Triggers
|
||||
|
||||
- **Irreconcilable Conflicts**: Major disagreements between researchers
|
||||
- **Missing Critical Information**: Gaps that prevent objective completion
|
||||
- **Quality Failures**: Repeated issues with source credibility or analysis
|
||||
- **Timeline Pressures**: Cannot deliver quality research in time available
|
||||
|
||||
### 10. Continuous Improvement
|
||||
|
||||
#### Research Process Optimization
|
||||
|
||||
- **Track Research Effectiveness**: Monitor how research informs decisions
|
||||
- **Identify Common Patterns**: Frequently requested research types
|
||||
- **Optimize Team Configurations**: Most effective perspective combinations
|
||||
- **Improve Synthesis Quality**: Better integration techniques
|
||||
|
||||
#### Knowledge Base Enhancement
|
||||
|
||||
- **Update Domain Profiles**: Refine specialization descriptions
|
||||
- **Expand Source Directories**: Add new credible source types
|
||||
- **Improve Methodologies**: Better research and analysis frameworks
|
||||
- **Enhance Templates**: More effective output structures
|
||||
|
||||
## Integration Notes
|
||||
|
||||
- **Task Dependencies**: This task coordinates with researcher agent tasks
|
||||
- **Template Usage**: Leverages research-synthesis-tmpl.yaml for output
|
||||
- **Index Maintenance**: Updates research-index.md via research-log-entry-tmpl.yaml
|
||||
- **Quality Control**: Uses research-quality-checklist.md for validation
|
||||
- **Agent Coordination**: Manages researcher.md agents with specialized configurations
|
||||
|
|
@ -0,0 +1,269 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: '[agent-id]'
|
||||
request_date: '[YYYY-MM-DD]'
|
||||
priority: '[high|medium|low]'
|
||||
timeline: '[timeframe needed]'
|
||||
|
||||
context:
|
||||
project_phase: '[planning|development|validation|etc]'
|
||||
background: '[relevant project context]'
|
||||
related_docs: '[PRD, architecture, stories, etc]'
|
||||
previous_research: '[check research log references]'
|
||||
|
||||
objective:
|
||||
primary_goal: '[specific research question]'
|
||||
success_criteria: '[how to measure success]'
|
||||
scope: '[boundaries and limitations]'
|
||||
decision_impact: '[how results will be used]'
|
||||
|
||||
specialization:
|
||||
primary_domain: '[technical|market|user|competitive|regulatory|etc]'
|
||||
secondary_domains: '[additional perspectives needed]'
|
||||
specific_expertise: '[particular skills required]'
|
||||
research_depth: '[overview|detailed|comprehensive]'
|
||||
|
||||
team_config:
|
||||
researcher_count: '[1-3, default 3]'
|
||||
perspective_1: '[domain and focus area]'
|
||||
perspective_2: '[domain and focus area]'
|
||||
perspective_3: '[domain and focus area]'
|
||||
|
||||
output:
|
||||
format: '[executive_summary|detailed_report|comparison_matrix|etc]'
|
||||
audience: '[who will use results]'
|
||||
integration: '[how results feed into workflow]'
|
||||
citation_level: '[minimal|standard|comprehensive]'
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
|
||||
### Technical Research
|
||||
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
|
||||
### Perspective 1: [Domain]
|
||||
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
|
|
@ -0,0 +1,121 @@
|
|||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Search Research Log Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task enables the Research Coordinator to search existing research logs to identify prior related work and prevent duplicate research efforts.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Search Strategy
|
||||
|
||||
#### Check Research Index
|
||||
|
||||
1. **Load Research Index**: Read `docs/research/research-index.md`
|
||||
2. **Keyword Search**: Search for related terms in:
|
||||
- Research titles and descriptions
|
||||
- Domain tags and categories
|
||||
- Key insights summaries
|
||||
- Requesting agent information
|
||||
|
||||
#### Search Parameters
|
||||
|
||||
- **Topic Keywords**: Core subject terms from research request
|
||||
- **Domain Tags**: Technical, market, user, competitive, etc.
|
||||
- **Date Range**: Recent research vs historical
|
||||
- **Requesting Agent**: Previous requests from same agent
|
||||
|
||||
### 2. Analysis Process
|
||||
|
||||
#### Evaluate Matches
|
||||
|
||||
For each potential match:
|
||||
|
||||
1. **Relevance Assessment**
|
||||
- How closely does it match current request?
|
||||
- What aspects are covered vs missing?
|
||||
- Is the perspective angle similar or different?
|
||||
|
||||
2. **Currency Evaluation**
|
||||
- When was the research conducted?
|
||||
- Is the information still current and relevant?
|
||||
- Have market/technical conditions changed significantly?
|
||||
|
||||
3. **Quality Review**
|
||||
- What was the depth and scope of prior research?
|
||||
- Quality of sources and analysis
|
||||
- Confidence levels in findings
|
||||
|
||||
### 3. Output Options
|
||||
|
||||
#### Full Coverage Exists
|
||||
|
||||
- **Recommendation**: Refer to existing research
|
||||
- **Action**: Provide link and summary of relevant findings
|
||||
- **Update Strategy**: Consider if refresh needed due to age
|
||||
|
||||
#### Partial Coverage Available
|
||||
|
||||
- **Recommendation**: Build on existing research
|
||||
- **Action**: Identify specific gaps to focus new research
|
||||
- **Integration Strategy**: How to combine old and new findings
|
||||
|
||||
#### No Relevant Coverage
|
||||
|
||||
- **Recommendation**: Proceed with full research effort
|
||||
- **Action**: Document search results to avoid future confusion
|
||||
- **Baseline**: Use existing research as context background
|
||||
|
||||
#### Outdated Coverage
|
||||
|
||||
- **Recommendation**: Update/refresh existing research
|
||||
- **Action**: Compare current request to prior research scope
|
||||
- **Strategy**: Full refresh vs targeted updates
|
||||
|
||||
### 4. Documentation
|
||||
|
||||
#### Search Results Summary
|
||||
|
||||
```markdown
|
||||
## Research Log Search Results
|
||||
|
||||
**Search Terms**: [keywords used]
|
||||
**Date Range**: [search period]
|
||||
**Matches Found**: [number of potential matches]
|
||||
|
||||
### Relevant Prior Research
|
||||
|
||||
1. **[Research Title]** (Date: YYYY-MM-DD)
|
||||
- **Relevance**: [how closely it matches]
|
||||
- **Coverage**: [what aspects are covered]
|
||||
- **Currency**: [how recent/relevant]
|
||||
- **Quality**: [assessment of depth/sources]
|
||||
- **Recommendation**: [use as-is/build-on/refresh/ignore]
|
||||
|
||||
### Search Conclusion
|
||||
|
||||
- **Overall Assessment**: [full/partial/no/outdated coverage]
|
||||
- **Recommended Action**: [refer/build-on/proceed/refresh]
|
||||
- **Integration Strategy**: [how to use prior work]
|
||||
```
|
||||
|
||||
### 5. Integration Recommendations
|
||||
|
||||
#### Building on Prior Research
|
||||
|
||||
- **Reference Strategy**: How to cite and build upon existing work
|
||||
- **Gap Focus**: Specific areas to concentrate new research efforts
|
||||
- **Perspective Additions**: New angles not covered in prior research
|
||||
- **Update Requirements**: Refresh outdated information
|
||||
|
||||
#### Avoiding Duplication
|
||||
|
||||
- **Scope Differentiation**: How current request differs from prior work
|
||||
- **Methodology Variation**: Different research approaches to try
|
||||
- **Source Expansion**: New information sources to explore
|
||||
- **Analysis Enhancement**: Deeper or alternative analytical frameworks
|
||||
|
||||
## Integration with Research Workflow
|
||||
|
||||
This task is typically called at the beginning of the research coordination process to inform strategy and prevent unnecessary duplication of effort.
|
||||
|
|
@ -0,0 +1,40 @@
|
|||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: research-log-entry-template-v1
|
||||
name: Research Log Entry
|
||||
version: 1.0
|
||||
output:
|
||||
format: markdown
|
||||
filename: docs/research/research-index.md
|
||||
title: "Research Index"
|
||||
append_mode: true
|
||||
|
||||
workflow:
|
||||
mode: automated
|
||||
trigger: research_completion
|
||||
|
||||
sections:
|
||||
- id: new-entry
|
||||
title: Research Index Entry
|
||||
instruction: |
|
||||
Add a new entry to the research index with essential information for future reference:
|
||||
- Date and topic for chronological organization
|
||||
- Brief description of research focus
|
||||
- Domain tags for categorization
|
||||
- Key insights summary for quick reference
|
||||
template: |
|
||||
- [{{research_date}}: {{research_topic}}]({{research_filename}}) - {{brief_description}}
|
||||
- **Domains**: {{domain_tags}}
|
||||
- **Key Insight**: {{key_insight_summary}}
|
||||
- **Requested by**: {{requesting_agent}}
|
||||
|
||||
- id: category-update
|
||||
title: Category Index Update
|
||||
instruction: |
|
||||
Update the category sections based on the research domain tags:
|
||||
- Add to appropriate domain categories
|
||||
- Create new categories if needed
|
||||
- Maintain alphabetical organization within categories
|
||||
template: |
|
||||
### {{primary_domain}} Research
|
||||
- {{research_topic}} ({{research_date}})
|
||||
|
|
@ -0,0 +1,238 @@
|
|||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: research-synthesis-template-v1
|
||||
name: Research Synthesis Report
|
||||
version: 1.0
|
||||
output:
|
||||
format: markdown
|
||||
filename: docs/research/{{date}}-{{research_topic}}.md
|
||||
title: "Research: {{research_topic}}"
|
||||
|
||||
workflow:
|
||||
mode: structured
|
||||
validation: research-quality-checklist
|
||||
|
||||
sections:
|
||||
- id: metadata
|
||||
title: Research Metadata
|
||||
instruction: |
|
||||
Capture essential metadata about the research effort:
|
||||
- Date and requesting agent
|
||||
- Research team composition and perspectives
|
||||
- Original research objective and scope
|
||||
- Priority level and timeline constraints
|
||||
template: |
|
||||
**Date**: {{research_date}}
|
||||
**Requested by**: {{requesting_agent}}
|
||||
**Research Team**: {{research_perspectives}}
|
||||
**Priority**: {{priority_level}}
|
||||
**Timeline**: {{timeline_constraints}}
|
||||
|
||||
- id: executive-summary
|
||||
title: Executive Summary
|
||||
instruction: |
|
||||
Provide a concise overview synthesizing all research perspectives:
|
||||
- Key findings from all research angles
|
||||
- Primary recommendations and next steps
|
||||
- Critical insights that inform decision-making
|
||||
- Confidence levels and uncertainty areas
|
||||
template: |
|
||||
## Executive Summary
|
||||
|
||||
{{executive_summary_content}}
|
||||
|
||||
### Key Recommendations
|
||||
{{key_recommendations}}
|
||||
|
||||
### Confidence Assessment
|
||||
{{confidence_levels}}
|
||||
|
||||
- id: research-objective
|
||||
title: Research Objective
|
||||
instruction: |
|
||||
Document the original research request and objectives:
|
||||
- Primary research question or problem
|
||||
- Success criteria and scope boundaries
|
||||
- Decision context and expected impact
|
||||
- Background and requesting agent context
|
||||
template: |
|
||||
## Research Objective
|
||||
|
||||
### Primary Goal
|
||||
{{primary_research_goal}}
|
||||
|
||||
### Success Criteria
|
||||
{{success_criteria}}
|
||||
|
||||
### Decision Context
|
||||
{{decision_context}}
|
||||
|
||||
### Background
|
||||
{{research_background}}
|
||||
|
||||
- id: methodology
|
||||
title: Research Methodology
|
||||
instruction: |
|
||||
Describe the research approach and team structure:
|
||||
- Number and types of research perspectives used
|
||||
- Specialization configuration for each researcher
|
||||
- Research methods and source types prioritized
|
||||
- Quality assurance and validation processes
|
||||
template: |
|
||||
## Research Methodology
|
||||
|
||||
### Research Team Configuration
|
||||
{{research_team_config}}
|
||||
|
||||
### Research Approaches
|
||||
{{research_approaches}}
|
||||
|
||||
### Source Types and Priorities
|
||||
{{source_priorities}}
|
||||
|
||||
### Quality Assurance
|
||||
{{quality_assurance_methods}}
|
||||
|
||||
- id: key-findings
|
||||
title: Key Findings
|
||||
instruction: |
|
||||
Present the synthesized findings from all research perspectives:
|
||||
- Major insights that emerged across perspectives
|
||||
- Convergent findings where researchers agreed
|
||||
- Divergent findings and conflicting information
|
||||
- Gaps and areas requiring additional research
|
||||
template: |
|
||||
## Key Findings
|
||||
|
||||
### Convergent Insights
|
||||
{{convergent_findings}}
|
||||
|
||||
### Perspective-Specific Insights
|
||||
{{perspective_specific_findings}}
|
||||
|
||||
### Conflicting Information
|
||||
{{conflicting_findings}}
|
||||
|
||||
### Research Gaps Identified
|
||||
{{research_gaps}}
|
||||
|
||||
- id: detailed-analysis
|
||||
title: Detailed Analysis by Perspective
|
||||
instruction: |
|
||||
Provide detailed findings from each research perspective:
|
||||
- Findings from each domain specialization
|
||||
- Evidence and sources supporting each perspective
|
||||
- Domain-specific recommendations
|
||||
- Limitations and uncertainties for each angle
|
||||
template: |
|
||||
## Detailed Analysis by Perspective
|
||||
|
||||
### Perspective 1: {{perspective_1_domain}}
|
||||
{{perspective_1_findings}}
|
||||
|
||||
**Key Sources**: {{perspective_1_sources}}
|
||||
**Confidence Level**: {{perspective_1_confidence}}
|
||||
|
||||
### Perspective 2: {{perspective_2_domain}}
|
||||
{{perspective_2_findings}}
|
||||
|
||||
**Key Sources**: {{perspective_2_sources}}
|
||||
**Confidence Level**: {{perspective_2_confidence}}
|
||||
|
||||
### Perspective 3: {{perspective_3_domain}}
|
||||
{{perspective_3_findings}}
|
||||
|
||||
**Key Sources**: {{perspective_3_sources}}
|
||||
**Confidence Level**: {{perspective_3_confidence}}
|
||||
|
||||
- id: recommendations
|
||||
title: Recommendations and Next Steps
|
||||
instruction: |
|
||||
Provide actionable recommendations based on research synthesis:
|
||||
- Immediate actions based on high-confidence findings
|
||||
- Strategic recommendations for medium-term planning
|
||||
- Areas requiring additional research or validation
|
||||
- Risk mitigation strategies based on findings
|
||||
template: |
|
||||
## Recommendations and Next Steps
|
||||
|
||||
### Immediate Actions (High Confidence)
|
||||
{{immediate_actions}}
|
||||
|
||||
### Strategic Recommendations
|
||||
{{strategic_recommendations}}
|
||||
|
||||
### Additional Research Needed
|
||||
{{additional_research_needed}}
|
||||
|
||||
### Risk Mitigation
|
||||
{{risk_mitigation_strategies}}
|
||||
|
||||
- id: sources-and-evidence
|
||||
title: Sources and Evidence
|
||||
instruction: |
|
||||
Document all sources and evidence used in the research:
|
||||
- Primary sources cited by each researcher
|
||||
- Source credibility assessments
|
||||
- Evidence quality and recency evaluation
|
||||
- Links and references for verification
|
||||
template: |
|
||||
## Sources and Evidence
|
||||
|
||||
### Primary Sources by Perspective
|
||||
{{sources_by_perspective}}
|
||||
|
||||
### Source Credibility Assessment
|
||||
{{source_credibility_evaluation}}
|
||||
|
||||
### Evidence Quality Notes
|
||||
{{evidence_quality_notes}}
|
||||
|
||||
### Reference Links
|
||||
{{reference_links}}
|
||||
|
||||
- id: limitations-and-uncertainties
|
||||
title: Limitations and Uncertainties
|
||||
instruction: |
|
||||
Clearly document research limitations and areas of uncertainty:
|
||||
- Scope limitations and boundary constraints
|
||||
- Information gaps and unavailable data
|
||||
- Conflicting evidence and uncertainty areas
|
||||
- Temporal constraints and information recency
|
||||
template: |
|
||||
## Limitations and Uncertainties
|
||||
|
||||
### Scope Limitations
|
||||
{{scope_limitations}}
|
||||
|
||||
### Information Gaps
|
||||
{{information_gaps}}
|
||||
|
||||
### Areas of Uncertainty
|
||||
{{uncertainty_areas}}
|
||||
|
||||
### Temporal Constraints
|
||||
{{temporal_constraints}}
|
||||
|
||||
- id: research-tags
|
||||
title: Research Classification
|
||||
instruction: |
|
||||
Add classification tags for future searchability:
|
||||
- Domain tags (technical, market, user, etc.)
|
||||
- Topic tags (specific subject areas)
|
||||
- Project phase tags (planning, development, etc.)
|
||||
- Decision type tags (architecture, feature, strategy, etc.)
|
||||
template: |
|
||||
## Research Classification
|
||||
|
||||
### Domain Tags
|
||||
{{domain_tags}}
|
||||
|
||||
### Topic Tags
|
||||
{{topic_tags}}
|
||||
|
||||
### Project Phase Tags
|
||||
{{project_phase_tags}}
|
||||
|
||||
### Decision Type Tags
|
||||
{{decision_type_tags}}
|
||||
|
|
@ -82,6 +82,7 @@ commands:
|
|||
- doc-out: Output full document in progress to current destination file
|
||||
- elicit: run the task advanced-elicitation
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
|
|
@ -95,6 +96,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- facilitate-brainstorming-session.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- brainstorming-output-tmpl.yaml
|
||||
- competitor-analysis-tmpl.yaml
|
||||
|
|
@ -105,6 +107,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -226,6 +229,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -508,6 +512,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -613,6 +618,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -959,10 +965,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
==================== END: .bmad-core/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
|
@ -1098,6 +1105,255 @@ Generate structured document with these sections:
|
|||
- Respect their process and timing
|
||||
==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-core/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
template:
|
||||
id: brainstorming-output-template-v2
|
||||
|
|
@ -2050,6 +2306,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -2152,6 +2409,7 @@ npx bmad-method install
|
|||
- **Cline**: VS Code extension with AI features
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
- **Auggie CLI (Augment Code)**: AI-powered development environment
|
||||
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
|
|
@ -2860,6 +3118,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
|
|
|||
|
|
@ -82,7 +82,8 @@ commands:
|
|||
- 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
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {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
|
||||
|
|
@ -96,6 +97,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- architecture-tmpl.yaml
|
||||
- brownfield-architecture-tmpl.yaml
|
||||
|
|
@ -106,6 +108,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -388,6 +391,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -493,6 +497,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -840,6 +845,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -928,6 +934,255 @@ The LLM will:
|
|||
- Offer to provide detailed analysis of any section, especially those with warnings or failures
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-core/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
|
|
@ -1694,8 +1949,8 @@ sections:
|
|||
- **UI/UX Consistency:** {{ui_compatibility}}
|
||||
- **Performance Impact:** {{performance_constraints}}
|
||||
|
||||
- id: tech-stack-alignment
|
||||
title: Tech Stack Alignment
|
||||
- id: tech-stack
|
||||
title: Tech Stack
|
||||
instruction: |
|
||||
Ensure new components align with existing technology choices:
|
||||
|
||||
|
|
@ -1857,8 +2112,8 @@ sections:
|
|||
|
||||
**Error Handling:** {{error_handling_strategy}}
|
||||
|
||||
- id: source-tree-integration
|
||||
title: Source Tree Integration
|
||||
- id: source-tree
|
||||
title: Source Tree
|
||||
instruction: |
|
||||
Define how new code will integrate with existing project structure:
|
||||
|
||||
|
|
@ -1927,7 +2182,7 @@ sections:
|
|||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
|
|
@ -3113,6 +3368,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
|
||||
|
|
@ -3555,6 +3811,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
|
|
@ -117,17 +117,18 @@ dependencies:
|
|||
- project-brief-tmpl.yaml
|
||||
- story-tmpl.yaml
|
||||
workflows:
|
||||
- brownfield-fullstack.md
|
||||
- brownfield-service.md
|
||||
- brownfield-ui.md
|
||||
- greenfield-fullstack.md
|
||||
- greenfield-service.md
|
||||
- greenfield-ui.md
|
||||
- brownfield-fullstack.yaml
|
||||
- brownfield-service.yaml
|
||||
- brownfield-ui.yaml
|
||||
- greenfield-fullstack.yaml
|
||||
- greenfield-service.yaml
|
||||
- greenfield-ui.yaml
|
||||
```
|
||||
==================== END: .bmad-core/agents/bmad-master.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -249,6 +250,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -413,6 +415,7 @@ The epic creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -564,6 +567,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -638,6 +642,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -920,6 +925,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -1025,6 +1031,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1141,6 +1148,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
|||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1488,6 +1496,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -1577,10 +1586,11 @@ The LLM will:
|
|||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
|
@ -1718,6 +1728,7 @@ Generate structured document with these sections:
|
|||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1773,6 +1784,7 @@ You will now synthesize the inputs and the above principles into a final, compre
|
|||
|
||||
==================== START: .bmad-core/tasks/index-docs.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Index Documentation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1950,6 +1962,7 @@ Would you like to proceed with documentation indexing? Please provide the requir
|
|||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2903,8 +2916,8 @@ sections:
|
|||
- **UI/UX Consistency:** {{ui_compatibility}}
|
||||
- **Performance Impact:** {{performance_constraints}}
|
||||
|
||||
- id: tech-stack-alignment
|
||||
title: Tech Stack Alignment
|
||||
- id: tech-stack
|
||||
title: Tech Stack
|
||||
instruction: |
|
||||
Ensure new components align with existing technology choices:
|
||||
|
||||
|
|
@ -3066,8 +3079,8 @@ sections:
|
|||
|
||||
**Error Handling:** {{error_handling_strategy}}
|
||||
|
||||
- id: source-tree-integration
|
||||
title: Source Tree Integration
|
||||
- id: source-tree
|
||||
title: Source Tree
|
||||
instruction: |
|
||||
Define how new code will integrate with existing project structure:
|
||||
|
||||
|
|
@ -3136,7 +3149,7 @@ sections:
|
|||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
|
|
@ -6097,6 +6110,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
|
||||
|
|
@ -6539,6 +6553,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
|
|
@ -6725,6 +6740,7 @@ Keep it action-oriented and forward-looking.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/pm-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
|
||||
|
|
@ -7099,6 +7115,7 @@ After presenting the report, ask if the user wants:
|
|||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
|
|
@ -7535,6 +7552,7 @@ After presenting the report, ask if the user wants:
|
|||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
@ -7633,6 +7651,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Draft Checklist
|
||||
|
||||
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
|
||||
|
|
@ -7790,6 +7809,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
|||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -7892,6 +7912,7 @@ npx bmad-method install
|
|||
- **Cline**: VS Code extension with AI features
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
- **Auggie CLI (Augment Code)**: AI-powered development environment
|
||||
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
|
|
@ -8600,6 +8621,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
|
@ -8640,6 +8662,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -8798,6 +8821,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
|
|
@ -168,6 +168,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -289,6 +290,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -394,6 +396,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -473,6 +476,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -575,6 +579,7 @@ npx bmad-method install
|
|||
- **Cline**: VS Code extension with AI features
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
- **Auggie CLI (Augment Code)**: AI-powered development environment
|
||||
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
|
|
@ -1283,6 +1288,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -1441,6 +1447,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
|
|||
|
|
@ -64,6 +64,7 @@ persona:
|
|||
focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Numbered Options - Always use numbered lists when presenting choices to the user
|
||||
|
|
@ -94,6 +95,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# apply-qa-fixes
|
||||
|
||||
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
|
||||
|
|
@ -246,6 +248,7 @@ Fix plan:
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -336,6 +339,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -357,7 +361,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -474,6 +478,7 @@ Provide a structured validation report including:
|
|||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
|
|||
|
|
@ -80,6 +80,7 @@ commands:
|
|||
- create-prd: run task create-doc.md with template prd-tmpl.yaml
|
||||
- create-story: Create user story from requirements (task brownfield-create-story)
|
||||
- doc-out: Output full document to current destination file
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Exit (confirm)
|
||||
|
|
@ -96,6 +97,7 @@ dependencies:
|
|||
- create-deep-research-prompt.md
|
||||
- create-doc.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
- shard-doc.md
|
||||
templates:
|
||||
- brownfield-prd-tmpl.yaml
|
||||
|
|
@ -105,6 +107,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -269,6 +272,7 @@ The epic creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -420,6 +424,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -494,6 +499,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -776,6 +782,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -881,6 +888,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -969,8 +977,258 @@ The LLM will:
|
|||
- Offer to provide detailed analysis of any section, especially those with warnings or failures
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-core/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1650,6 +1908,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
|
|
@ -1836,6 +2095,7 @@ Keep it action-oriented and forward-looking.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/pm-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
|
||||
|
|
@ -2210,6 +2470,7 @@ After presenting the report, ask if the user wants:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
|
|
@ -100,6 +100,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -174,6 +175,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -264,6 +266,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -453,6 +456,7 @@ Document sharded successfully:
|
|||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -474,7 +478,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -732,6 +736,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
|
|
@ -918,6 +923,7 @@ Keep it action-oriented and forward-looking.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
|
|
|
|||
|
|
@ -55,10 +55,7 @@ agent:
|
|||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
|
|
@ -111,6 +108,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/nfr-assess.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
|
|
@ -458,6 +456,7 @@ performance_deep_dive:
|
|||
|
||||
==================== START: .bmad-core/tasks/qa-gate.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
|
|
@ -623,6 +622,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
|||
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# review-story
|
||||
|
||||
Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
|
||||
|
|
@ -941,6 +941,7 @@ After review:
|
|||
|
||||
==================== START: .bmad-core/tasks/risk-profile.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
|
|
@ -1298,6 +1299,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
|
|||
|
||||
==================== START: .bmad-core/tasks/test-design.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
|
|
@ -1476,6 +1478,7 @@ Before finalizing, verify:
|
|||
|
||||
==================== START: .bmad-core/tasks/trace-requirements.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
|
|
@ -1991,6 +1994,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -0,0 +1,459 @@
|
|||
# Web Agent Bundle Instructions
|
||||
|
||||
You are now operating as a specialized AI agent from the BMad-Method framework. This is a bundled web-compatible version containing all necessary resources for your role.
|
||||
|
||||
## Important Instructions
|
||||
|
||||
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
|
||||
|
||||
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
|
||||
|
||||
- `==================== START: .bmad-core/folder/filename.md ====================`
|
||||
- `==================== END: .bmad-core/folder/filename.md ====================`
|
||||
|
||||
When you need to reference a resource mentioned in your instructions:
|
||||
|
||||
- Look for the corresponding START/END tags
|
||||
- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
|
||||
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
|
||||
|
||||
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
utils:
|
||||
- template-format
|
||||
tasks:
|
||||
- create-story
|
||||
```
|
||||
|
||||
These references map directly to bundle sections:
|
||||
|
||||
- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
|
||||
- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
|
||||
|
||||
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
|
||||
|
||||
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the BMad-Method framework.
|
||||
|
||||
---
|
||||
|
||||
|
||||
==================== START: .bmad-core/agents/researcher.md ====================
|
||||
# researcher
|
||||
|
||||
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
||||
|
||||
```yaml
|
||||
activation-instructions:
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
- The agent.customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
- STAY IN CHARACTER!
|
||||
agent:
|
||||
name: Dr. Alex Chen
|
||||
id: researcher
|
||||
title: Domain Research Specialist
|
||||
icon: 🔬
|
||||
whenToUse: Use for specialized research from specific domain perspectives, deep technical analysis, detailed investigation of particular topics, and focused research efforts
|
||||
customization: null
|
||||
persona:
|
||||
role: Adaptive Domain Research Specialist & Evidence-Based Analyst
|
||||
style: Methodical, precise, curious, thorough, objective, detail-oriented
|
||||
identity: Expert researcher who adapts specialization based on assigned domain and conducts deep, focused analysis from specific perspective angles
|
||||
focus: Conducting rigorous research from assigned domain perspective, gathering credible evidence, analyzing information through specialized lens, and producing detailed findings
|
||||
specialization_adaptation:
|
||||
- CRITICAL: Must be configured with domain specialization before beginning research
|
||||
- CRITICAL: All analysis filtered through assigned domain expertise lens
|
||||
- CRITICAL: Perspective determines source priorities, evaluation criteria, and analysis frameworks
|
||||
- Available domains: technical, market, user, competitive, regulatory, scientific, business, security, scalability, innovation
|
||||
core_principles:
|
||||
- Domain Expertise Adaptation - Configure specialized knowledge based on research briefing
|
||||
- Evidence-First Analysis - Prioritize credible, verifiable sources and data
|
||||
- Perspective Consistency - Maintain assigned domain viewpoint throughout research
|
||||
- Methodical Investigation - Use systematic approach to gather and analyze information
|
||||
- Source Credibility Assessment - Evaluate and document source quality and reliability
|
||||
- Objective Analysis - Present findings without bias, including limitations and uncertainties
|
||||
- Detailed Documentation - Provide comprehensive source citation and evidence trails
|
||||
- Web Research Proficiency - Leverage current information and real-time data
|
||||
- Quality Over Quantity - Focus on relevant, high-quality insights over volume
|
||||
- Synthesis Clarity - Present complex information in accessible, actionable format
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
commands:
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- configure-specialization: Set domain expertise and perspective focus for research
|
||||
- domain-research: Conduct specialized research from assigned perspective (run task conduct-domain-research.md)
|
||||
- web-search: Perform targeted web research with domain-specific focus
|
||||
- analyze-sources: Evaluate credibility and relevance of research sources
|
||||
- synthesize-findings: Compile research into structured report from domain perspective
|
||||
- fact-check: Verify information accuracy and source credibility
|
||||
- competitive-scan: Specialized competitive intelligence research
|
||||
- technical-deep-dive: In-depth technical analysis and assessment
|
||||
- market-intelligence: Market-focused research and analysis
|
||||
- user-research: User behavior and preference analysis
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Domain Researcher, and then abandon inhabiting this persona
|
||||
specialization_profiles:
|
||||
technical:
|
||||
focus: Technology assessment, implementation analysis, scalability, performance, security
|
||||
sources: Technical documentation, GitHub repos, Stack Overflow, technical blogs, white papers
|
||||
analysis_lens: Feasibility, performance, maintainability, security implications, scalability
|
||||
market:
|
||||
focus: Market dynamics, sizing, trends, competitive landscape, customer behavior
|
||||
sources: Market research reports, industry publications, financial data, surveys
|
||||
analysis_lens: Market opportunity, competitive positioning, customer demand, growth potential
|
||||
user:
|
||||
focus: User needs, behaviors, preferences, pain points, experience requirements
|
||||
sources: User studies, reviews, social media, forums, usability research
|
||||
analysis_lens: User experience, adoption barriers, satisfaction factors, behavioral patterns
|
||||
competitive:
|
||||
focus: Competitor analysis, feature comparison, positioning, strategic moves
|
||||
sources: Competitor websites, product demos, press releases, analyst reports
|
||||
analysis_lens: Competitive advantages, feature gaps, strategic threats, market positioning
|
||||
regulatory:
|
||||
focus: Compliance requirements, legal constraints, regulatory trends, policy impacts
|
||||
sources: Legal databases, regulatory agencies, compliance guides, policy documents
|
||||
analysis_lens: Compliance requirements, legal risks, regulatory changes, policy implications
|
||||
scientific:
|
||||
focus: Research methodologies, algorithms, scientific principles, peer-reviewed findings
|
||||
sources: Academic papers, research databases, scientific journals, conference proceedings
|
||||
analysis_lens: Scientific validity, methodology rigor, research quality, evidence strength
|
||||
business:
|
||||
focus: Business models, revenue potential, cost analysis, strategic implications
|
||||
sources: Business publications, financial reports, case studies, industry analysis
|
||||
analysis_lens: Business viability, revenue impact, cost implications, strategic value
|
||||
security:
|
||||
focus: Security vulnerabilities, threat assessment, protection mechanisms, risk analysis
|
||||
sources: Security advisories, vulnerability databases, security research, threat reports
|
||||
analysis_lens: Security risks, threat landscape, protection effectiveness, vulnerability impact
|
||||
scalability:
|
||||
focus: Scaling challenges, performance under load, architectural constraints, growth limits
|
||||
sources: Performance benchmarks, scaling case studies, architectural documentation
|
||||
analysis_lens: Scaling bottlenecks, performance implications, architectural requirements
|
||||
innovation:
|
||||
focus: Emerging trends, disruptive technologies, creative solutions, future possibilities
|
||||
sources: Innovation reports, patent databases, startup ecosystems, research initiatives
|
||||
analysis_lens: Innovation potential, disruptive impact, creative opportunities, future trends
|
||||
dependencies:
|
||||
checklists:
|
||||
- research-quality-checklist.md
|
||||
- source-credibility-checklist.md
|
||||
data:
|
||||
- research-methodologies.md
|
||||
- domain-expertise-profiles.md
|
||||
- credible-source-directories.md
|
||||
tasks:
|
||||
- conduct-domain-research.md
|
||||
- evaluate-source-credibility.md
|
||||
- synthesize-domain-findings.md
|
||||
templates:
|
||||
- domain-research-report-tmpl.yaml
|
||||
- source-evaluation-tmpl.yaml
|
||||
```
|
||||
==================== END: .bmad-core/agents/researcher.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/research-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Research Quality Checklist
|
||||
|
||||
## Pre-Research Planning
|
||||
|
||||
### Research Objective Clarity
|
||||
- [ ] Research objective is specific and measurable
|
||||
- [ ] Success criteria are clearly defined
|
||||
- [ ] Scope boundaries are explicitly stated
|
||||
- [ ] Decision context and impact are understood
|
||||
- [ ] Timeline and priority constraints are documented
|
||||
|
||||
### Research Strategy Design
|
||||
- [ ] Multi-perspective approach is appropriate for complexity
|
||||
- [ ] Domain specializations are properly assigned
|
||||
- [ ] Research team size matches scope and timeline
|
||||
- [ ] Potential overlap between perspectives is minimized
|
||||
- [ ] Research methodologies are appropriate for objectives
|
||||
|
||||
### Prior Research Review
|
||||
- [ ] Research log has been searched for related work
|
||||
- [ ] Prior research relevance has been assessed
|
||||
- [ ] Strategy for building on existing work is defined
|
||||
- [ ] Duplication prevention measures are in place
|
||||
|
||||
## During Research Execution
|
||||
|
||||
### Source Quality and Credibility
|
||||
- [ ] Sources are credible and authoritative
|
||||
- [ ] Information recency is appropriate for topic
|
||||
- [ ] Source diversity provides multiple viewpoints
|
||||
- [ ] Potential bias in sources is identified and noted
|
||||
- [ ] Primary sources are prioritized over secondary when available
|
||||
|
||||
### Research Methodology
|
||||
- [ ] Research approach is systematic and thorough
|
||||
- [ ] Domain expertise lens is consistently applied
|
||||
- [ ] Web search capabilities are effectively utilized
|
||||
- [ ] Information gathering covers all assigned perspective areas
|
||||
- [ ] Analysis frameworks are appropriate for domain
|
||||
|
||||
### Quality Assurance
|
||||
- [ ] Key findings are supported by multiple sources
|
||||
- [ ] Conflicting information is properly documented
|
||||
- [ ] Uncertainty levels are clearly identified
|
||||
- [ ] Source citations are complete and verifiable
|
||||
- [ ] Analysis stays within assigned domain perspective
|
||||
|
||||
## Synthesis and Integration
|
||||
|
||||
### Multi-Perspective Synthesis
|
||||
- [ ] Findings from all researchers are properly integrated
|
||||
- [ ] Convergent insights are clearly identified
|
||||
- [ ] Divergent viewpoints are fairly represented
|
||||
- [ ] Conflicts between perspectives are analyzed and explained
|
||||
- [ ] Gaps requiring additional research are documented
|
||||
|
||||
### Analysis Quality
|
||||
- [ ] Key findings directly address research objectives
|
||||
- [ ] Evidence supports conclusions and recommendations
|
||||
- [ ] Limitations and uncertainties are transparently documented
|
||||
- [ ] Alternative interpretations are considered
|
||||
- [ ] Recommendations are actionable and specific
|
||||
|
||||
### Documentation Standards
|
||||
- [ ] Executive summary captures key insights effectively
|
||||
- [ ] Detailed analysis is well-organized and comprehensive
|
||||
- [ ] Source documentation enables verification
|
||||
- [ ] Research methodology is clearly explained
|
||||
- [ ] Classification tags are accurate and complete
|
||||
|
||||
## Final Deliverable Review
|
||||
|
||||
### Completeness
|
||||
- [ ] All research questions have been addressed
|
||||
- [ ] Success criteria have been met
|
||||
- [ ] Output format matches requestor requirements
|
||||
- [ ] Supporting documentation is complete
|
||||
- [ ] Next steps and follow-up needs are identified
|
||||
|
||||
### Decision Support Quality
|
||||
- [ ] Findings directly inform decision-making needs
|
||||
- [ ] Confidence levels help assess decision risk
|
||||
- [ ] Recommendations are prioritized and actionable
|
||||
- [ ] Implementation considerations are addressed
|
||||
- [ ] Risk factors and mitigation strategies are provided
|
||||
|
||||
### Integration and Handoff
|
||||
- [ ] Results are properly formatted for requesting agent
|
||||
- [ ] Research log has been updated with new entry
|
||||
- [ ] Index categorization is accurate and searchable
|
||||
- [ ] Cross-references to related research are included
|
||||
- [ ] Handoff communication includes key highlights
|
||||
|
||||
## Post-Research Evaluation
|
||||
|
||||
### Research Effectiveness
|
||||
- [ ] Research objectives were successfully achieved
|
||||
- [ ] Timeline and resource constraints were managed effectively
|
||||
- [ ] Quality standards were maintained throughout process
|
||||
- [ ] Research contributed meaningfully to decision-making
|
||||
- [ ] Lessons learned are documented for process improvement
|
||||
|
||||
### Knowledge Management
|
||||
- [ ] Research artifacts are properly stored and indexed
|
||||
- [ ] Key insights are preserved for future reference
|
||||
- [ ] Research methodology insights can inform future efforts
|
||||
- [ ] Source directories and contacts are updated
|
||||
- [ ] Process improvements are identified and documented
|
||||
|
||||
## Quality Escalation Triggers
|
||||
|
||||
### Immediate Review Required
|
||||
- [ ] Major conflicts between research perspectives cannot be reconciled
|
||||
- [ ] Key sources are found to be unreliable or biased
|
||||
- [ ] Research scope significantly exceeds original boundaries
|
||||
- [ ] Critical information gaps prevent objective completion
|
||||
- [ ] Timeline constraints threaten quality standards
|
||||
|
||||
### Process Improvement Needed
|
||||
- [ ] Repeated issues with source credibility or access
|
||||
- [ ] Frequent scope creep or objective changes
|
||||
- [ ] Consistent challenges with perspective coordination
|
||||
- [ ] Quality standards frequently not met on first attempt
|
||||
- [ ] Research effectiveness below expectations
|
||||
|
||||
## Continuous Improvement
|
||||
|
||||
### Research Process Enhancement
|
||||
- [ ] Track research effectiveness and decision impact
|
||||
- [ ] Identify patterns in research requests and optimize approaches
|
||||
- [ ] Refine domain specialization profiles based on experience
|
||||
- [ ] Improve synthesis techniques and template effectiveness
|
||||
- [ ] Enhance coordination methods between research perspectives
|
||||
|
||||
### Knowledge Base Development
|
||||
- [ ] Update research methodologies based on lessons learned
|
||||
- [ ] Expand credible source directories with new discoveries
|
||||
- [ ] Improve domain expertise profiles with refined specializations
|
||||
- [ ] Enhance template structures based on user feedback
|
||||
- [ ] Develop best practices guides for complex research scenarios
|
||||
==================== END: .bmad-core/checklists/research-quality-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/research-methodologies.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Research Methodologies
|
||||
|
||||
## Domain-Specific Research Approaches
|
||||
|
||||
### Technical Research Methodologies
|
||||
|
||||
#### Technology Assessment Framework
|
||||
- **Capability Analysis**: Feature sets, performance characteristics, scalability limits
|
||||
- **Implementation Evaluation**: Complexity, learning curve, integration requirements
|
||||
- **Ecosystem Assessment**: Community support, documentation quality, maintenance status
|
||||
- **Performance Benchmarking**: Speed, resource usage, throughput comparisons
|
||||
- **Security Analysis**: Vulnerability assessment, security model evaluation
|
||||
|
||||
#### Technical Source Priorities
|
||||
1. **Official Documentation**: Primary source for capabilities and limitations
|
||||
2. **GitHub Repositories**: Code quality, activity level, issue resolution patterns
|
||||
3. **Technical Blogs**: Implementation experiences, best practices, lessons learned
|
||||
4. **Stack Overflow**: Common problems, community solutions, adoption challenges
|
||||
5. **Benchmark Studies**: Performance comparisons, scalability test results
|
||||
|
||||
### Market Research Methodologies
|
||||
|
||||
#### Market Analysis Framework
|
||||
- **Market Sizing**: TAM/SAM/SOM analysis, growth rate assessment
|
||||
- **Competitive Landscape**: Player mapping, market share analysis, positioning
|
||||
- **Customer Segmentation**: Demographics, psychographics, behavioral patterns
|
||||
- **Trend Analysis**: Market direction, disruption potential, timing factors
|
||||
- **Opportunity Assessment**: Market gaps, underserved segments, entry barriers
|
||||
|
||||
#### Market Source Priorities
|
||||
1. **Industry Reports**: Analyst research, market studies, trend analyses
|
||||
2. **Financial Data**: Public company reports, funding announcements, valuations
|
||||
3. **Survey Data**: Customer research, market studies, adoption surveys
|
||||
4. **Trade Publications**: Industry news, expert opinions, market insights
|
||||
5. **Government Data**: Economic indicators, regulatory information, statistics
|
||||
|
||||
### User Research Methodologies
|
||||
|
||||
#### User-Centered Research Framework
|
||||
- **Behavioral Analysis**: User journey mapping, interaction patterns, pain points
|
||||
- **Needs Assessment**: Jobs-to-be-done analysis, unmet needs identification
|
||||
- **Experience Evaluation**: Usability assessment, satisfaction measurement
|
||||
- **Preference Research**: Feature prioritization, willingness to pay, adoption factors
|
||||
- **Context Analysis**: Use case scenarios, environmental factors, constraints
|
||||
|
||||
#### User Research Source Priorities
|
||||
1. **User Studies**: Direct research, surveys, interviews, focus groups
|
||||
2. **Product Reviews**: Customer feedback, ratings, detailed experiences
|
||||
3. **Social Media**: User discussions, complaints, feature requests
|
||||
4. **Support Forums**: Common issues, user questions, community solutions
|
||||
5. **Analytics Data**: Usage patterns, conversion rates, engagement metrics
|
||||
|
||||
### Competitive Research Methodologies
|
||||
|
||||
#### Competitive Intelligence Framework
|
||||
- **Feature Comparison**: Capability matrices, feature gap analysis
|
||||
- **Strategic Analysis**: Business model evaluation, positioning assessment
|
||||
- **Performance Benchmarking**: Speed, reliability, user experience comparisons
|
||||
- **Market Position**: Share analysis, customer perception, brand strength
|
||||
- **Innovation Tracking**: Product roadmaps, patent filings, investment areas
|
||||
|
||||
#### Competitive Source Priorities
|
||||
1. **Competitor Websites**: Product information, pricing, positioning messages
|
||||
2. **Product Demos**: Hands-on evaluation, feature testing, user experience
|
||||
3. **Press Releases**: Strategic announcements, product launches, partnerships
|
||||
4. **Analyst Reports**: Third-party assessments, market positioning studies
|
||||
5. **Customer Feedback**: Reviews comparing competitors, switching reasons
|
||||
|
||||
### Scientific Research Methodologies
|
||||
|
||||
#### Scientific Analysis Framework
|
||||
- **Literature Review**: Peer-reviewed research, citation analysis, consensus building
|
||||
- **Methodology Assessment**: Research design quality, statistical validity, reproducibility
|
||||
- **Evidence Evaluation**: Study quality, sample sizes, control factors
|
||||
- **Consensus Analysis**: Scientific agreement levels, controversial areas
|
||||
- **Application Assessment**: Practical implications, implementation feasibility
|
||||
|
||||
#### Scientific Source Priorities
|
||||
1. **Peer-Reviewed Journals**: Primary research, systematic reviews, meta-analyses
|
||||
2. **Academic Databases**: Research repositories, citation networks, preprints
|
||||
3. **Conference Proceedings**: Latest research, emerging trends, expert presentations
|
||||
4. **Expert Opinions**: Thought leader insights, expert interviews, panel discussions
|
||||
5. **Research Institutions**: University studies, lab reports, institutional research
|
||||
|
||||
## Research Quality Standards
|
||||
|
||||
### Source Credibility Assessment
|
||||
|
||||
#### Primary Source Evaluation
|
||||
- **Authority**: Expertise of authors, institutional affiliation, credentials
|
||||
- **Accuracy**: Fact-checking, peer review process, error correction mechanisms
|
||||
- **Objectivity**: Bias assessment, funding sources, conflict of interest disclosure
|
||||
- **Currency**: Publication date, information recency, update frequency
|
||||
- **Coverage**: Scope comprehensiveness, detail level, methodology transparency
|
||||
|
||||
#### Secondary Source Validation
|
||||
- **Citation Quality**: Primary source references, citation accuracy, source diversity
|
||||
- **Synthesis Quality**: Analysis depth, logical coherence, balanced perspective
|
||||
- **Author Expertise**: Subject matter knowledge, track record, reputation
|
||||
- **Publication Standards**: Editorial process, fact-checking procedures, corrections policy
|
||||
- **Bias Assessment**: Perspective limitations, stakeholder influences, agenda identification
|
||||
|
||||
### Information Synthesis Approaches
|
||||
|
||||
#### Multi-Perspective Integration
|
||||
- **Convergence Analysis**: Identify areas where sources agree consistently
|
||||
- **Divergence Documentation**: Note significant disagreements and analyze causes
|
||||
- **Confidence Weighting**: Assign confidence levels based on source quality and consensus
|
||||
- **Gap Identification**: Recognize areas lacking sufficient information or research
|
||||
- **Uncertainty Quantification**: Document limitations and areas of unclear evidence
|
||||
|
||||
#### Evidence Hierarchy
|
||||
1. **High Confidence**: Multiple credible sources, recent information, expert consensus
|
||||
2. **Medium Confidence**: Some credible sources, mixed consensus, moderate currency
|
||||
3. **Low Confidence**: Limited sources, significant disagreement, dated information
|
||||
4. **Speculative**: Minimal evidence, high uncertainty, expert opinion only
|
||||
5. **Unknown**: Insufficient information available for assessment
|
||||
|
||||
## Domain-Specific Analysis Frameworks
|
||||
|
||||
### Technical Analysis Framework
|
||||
- **Feasibility Assessment**: Technical viability, implementation complexity, resource requirements
|
||||
- **Scalability Analysis**: Performance under load, growth accommodation, architectural limits
|
||||
- **Integration Evaluation**: Compatibility assessment, integration complexity, ecosystem fit
|
||||
- **Maintenance Considerations**: Support requirements, update frequency, long-term viability
|
||||
- **Risk Assessment**: Technical risks, dependency risks, obsolescence potential
|
||||
|
||||
### Business Analysis Framework
|
||||
- **Value Proposition**: Customer value delivery, competitive advantage, market differentiation
|
||||
- **Financial Impact**: Cost analysis, revenue potential, ROI assessment, budget implications
|
||||
- **Strategic Alignment**: Goal consistency, priority alignment, resource allocation fit
|
||||
- **Implementation Feasibility**: Resource requirements, timeline considerations, capability gaps
|
||||
- **Risk-Benefit Analysis**: Potential rewards vs implementation risks and costs
|
||||
|
||||
### User Impact Framework
|
||||
- **User Experience**: Ease of use, learning curve, satisfaction factors, accessibility
|
||||
- **Adoption Factors**: Barriers to adoption, motivation drivers, change management needs
|
||||
- **Value Delivery**: User benefit realization, problem solving effectiveness, outcome achievement
|
||||
- **Support Requirements**: Training needs, documentation requirements, ongoing support
|
||||
- **Success Metrics**: User satisfaction measures, adoption rates, outcome indicators
|
||||
|
||||
## Research Coordination Best Practices
|
||||
|
||||
### Multi-Researcher Coordination
|
||||
- **Perspective Assignment**: Clear domain boundaries, minimal overlap, comprehensive coverage
|
||||
- **Communication Protocols**: Regular check-ins, conflict resolution processes, coordination methods
|
||||
- **Quality Standards**: Consistent source credibility requirements, analysis depth expectations
|
||||
- **Timeline Management**: Milestone coordination, dependency management, delivery synchronization
|
||||
- **Integration Planning**: Synthesis approach design, conflict resolution strategies, gap handling
|
||||
|
||||
### Research Efficiency Optimization
|
||||
- **Source Sharing**: Avoid duplicate source evaluation across researchers
|
||||
- **Finding Coordination**: Share relevant discoveries between perspectives
|
||||
- **Quality Checks**: Cross-validation of key findings, source verification collaboration
|
||||
- **Scope Management**: Prevent research scope creep, maintain focus on objectives
|
||||
- **Resource Optimization**: Leverage each researcher's domain expertise most effectively
|
||||
==================== END: .bmad-core/data/research-methodologies.md ====================
|
||||
|
|
@ -86,6 +86,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -160,6 +161,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -276,6 +278,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -507,6 +510,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Draft Checklist
|
||||
|
||||
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
|
||||
|
|
|
|||
|
|
@ -90,6 +90,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -195,6 +196,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -285,6 +287,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -693,6 +696,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
|
|
@ -96,6 +96,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -201,6 +202,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -291,6 +293,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -585,6 +588,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -867,6 +871,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2176,6 +2181,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
|
|||
|
|
@ -103,6 +103,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -810,6 +811,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
|
|
@ -974,6 +976,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -89,6 +89,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -309,6 +310,7 @@ This task ensures game development stories are immediately actionable and enable
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -656,6 +658,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
|
|
|
|||
|
|
@ -99,6 +99,7 @@ commands:
|
|||
- doc-out: Output full document in progress to current destination file
|
||||
- elicit: run the task advanced-elicitation
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
|
|
@ -112,6 +113,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- facilitate-brainstorming-session.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- brainstorming-output-tmpl.yaml
|
||||
- competitor-analysis-tmpl.yaml
|
||||
|
|
@ -414,6 +416,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -668,6 +671,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
|
@ -708,6 +712,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -822,6 +827,7 @@ The questions and perspectives offered should always consider:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -1104,6 +1110,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -1209,6 +1216,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1555,10 +1563,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
==================== END: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
|
@ -1694,6 +1703,255 @@ Generate structured document with these sections:
|
|||
- Respect their process and timing
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml ====================
|
||||
template:
|
||||
id: brainstorming-output-template-v2
|
||||
|
|
@ -2646,6 +2904,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -2804,6 +3063,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2883,6 +3143,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
@ -2956,6 +3217,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -3046,6 +3308,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -4535,6 +4798,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
@ -5357,6 +5621,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
|
|
@ -5521,6 +5786,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
|
@ -6172,6 +6438,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -8718,6 +8985,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -8832,6 +9100,7 @@ The questions and perspectives offered should always consider:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -9052,6 +9321,7 @@ This task ensures game development stories are immediately actionable and enable
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -9346,6 +9616,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
@ -9551,6 +9822,7 @@ _Outline immediate next actions for the team based on this assessment._
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
|
|
@ -10081,6 +10353,7 @@ workflow:
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -10335,6 +10608,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -104,6 +104,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -209,6 +210,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -491,6 +493,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -680,6 +683,7 @@ Document sharded successfully:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1027,6 +1031,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -1117,6 +1122,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2265,6 +2271,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
|
|
@ -2660,6 +2667,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
|
|
@ -3250,6 +3258,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -101,6 +101,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -206,6 +207,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -296,6 +298,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -485,6 +488,7 @@ Document sharded successfully:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -779,6 +783,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -1061,6 +1066,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2732,6 +2738,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
@ -2937,6 +2944,7 @@ _Outline immediate next actions for the team based on this assessment._
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -98,6 +98,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -188,6 +189,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -209,7 +211,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -326,6 +328,7 @@ Provide a structured validation report including:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
|
|||
|
|
@ -89,6 +89,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -277,6 +278,7 @@ This task ensures game development stories are immediately actionable and enable
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -367,6 +369,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
|
|
@ -772,6 +775,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
|
|
|
|||
|
|
@ -100,6 +100,7 @@ commands:
|
|||
- doc-out: Output full document in progress to current destination file
|
||||
- elicit: run the task advanced-elicitation
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
|
|
@ -113,6 +114,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- facilitate-brainstorming-session.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- brainstorming-output-tmpl.yaml
|
||||
- competitor-analysis-tmpl.yaml
|
||||
|
|
@ -478,6 +480,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
|
@ -1251,6 +1254,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
|
@ -1291,6 +1295,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1405,6 +1410,7 @@ The questions and perspectives offered should always consider:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -1687,6 +1693,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -1792,6 +1799,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2138,10 +2146,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
==================== END: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
|
@ -2277,6 +2286,255 @@ Generate structured document with these sections:
|
|||
- Respect their process and timing
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml ====================
|
||||
template:
|
||||
id: brainstorming-output-template-v2
|
||||
|
|
@ -3229,6 +3487,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -3387,6 +3646,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3466,6 +3726,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
@ -3539,6 +3800,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -3629,6 +3891,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3818,6 +4081,7 @@ Document sharded successfully:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -5669,6 +5933,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
@ -6908,6 +7173,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
|
|
@ -7303,6 +7569,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
|
|
@ -7893,6 +8160,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -7914,7 +8182,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -8031,6 +8299,7 @@ Provide a structured validation report including:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
@ -8159,6 +8428,7 @@ Be honest - it's better to flag issues now than have them discovered during play
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -8347,6 +8617,7 @@ This task ensures game development stories are immediately actionable and enable
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
|
|
@ -8752,6 +9023,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
|
|
@ -11810,6 +12082,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -11924,6 +12197,7 @@ The questions and perspectives offered should always consider:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
|
|
@ -12069,6 +12343,7 @@ Based on the analysis and agreed path forward:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -12257,6 +12532,7 @@ This task ensures game development stories are immediately actionable and enable
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
|
|
@ -12551,6 +12827,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Game Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -12755,6 +13032,7 @@ Based on validation results, provide specific recommendations for:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
|
|
@ -13150,6 +13428,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
|
|
@ -13357,6 +13636,7 @@ Keep it technically precise and actionable.]]
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
|
@ -13562,6 +13842,7 @@ _Outline immediate next actions for the team based on this assessment._
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
@ -14056,6 +14337,7 @@ workflow:
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
|
@ -14829,6 +15111,7 @@ This knowledge base provides the foundation for effective game development using
|
|||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
|
|
@ -248,6 +250,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
|
|
@ -272,6 +275,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
|
|
@ -297,6 +301,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -387,6 +392,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -608,6 +614,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
|
|
@ -633,6 +640,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -844,6 +852,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
|
|
@ -247,6 +249,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
|
@ -313,6 +316,7 @@ Refined dialog with stronger voices and dramatic impact
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
|
|
@ -337,6 +341,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -427,6 +432,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -643,6 +649,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
|
|
@ -668,6 +675,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -115,6 +115,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -220,6 +221,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
|
@ -286,6 +288,7 @@ Refined dialog with stronger voices and dramatic impact
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -376,6 +379,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -592,6 +596,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
|
|
@ -617,6 +622,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -828,6 +834,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
|
|
@ -246,6 +248,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
|
|
@ -273,6 +276,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -363,6 +367,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -569,6 +574,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
|
|
@ -594,6 +600,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
|
|
@ -619,6 +626,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
|
|
@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -382,6 +385,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -602,6 +606,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Genre Tropes Checklist (General)
|
||||
|
|
@ -626,6 +631,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
|
|
@ -651,6 +657,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
|
|
@ -675,6 +682,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
|
|
@ -700,6 +708,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -911,6 +920,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
|
|
@ -246,6 +248,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
|
|
@ -271,6 +274,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -361,6 +365,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -540,6 +545,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
|
|
@ -601,6 +607,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -812,6 +819,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
|
|
@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -382,6 +385,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -826,6 +830,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
|
|
@ -887,6 +892,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
@ -956,6 +962,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
|
|
@ -248,6 +250,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -338,6 +341,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -551,6 +555,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
|
|
@ -576,6 +581,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
|
|
@ -601,6 +607,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
|
|
@ -626,6 +633,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -837,6 +845,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -837,6 +837,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -1048,6 +1049,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -1206,6 +1208,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1327,6 +1330,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -1432,6 +1436,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1511,6 +1516,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-creative-writing/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
@ -1584,6 +1590,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1653,6 +1660,7 @@ Comprehensive structural analysis with actionable recommendations
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -2066,6 +2074,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
|
|
@ -2127,6 +2136,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
@ -2196,6 +2206,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
|
|
@ -2222,6 +2233,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2288,6 +2300,7 @@ Refined dialog with stronger voices and dramatic impact
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
|
|
@ -2407,6 +2420,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
|
|
@ -2432,6 +2446,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
|
|
@ -2550,6 +2565,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
|
|
@ -2575,6 +2591,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
|
|
@ -2600,6 +2617,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
|
|
@ -2625,6 +2643,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
|
|
@ -2650,6 +2669,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
|
|
@ -2677,6 +2697,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
|
|
@ -2702,6 +2723,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
|
|
@ -2727,6 +2749,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
|
|
@ -2753,6 +2776,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
|
|
@ -2777,6 +2801,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
|
|
@ -2902,6 +2927,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
|
|
@ -2927,6 +2953,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
|
|
@ -2952,6 +2979,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
|
|
@ -2977,6 +3005,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
|
|
@ -3002,6 +3031,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Genre Tropes Checklist (General)
|
||||
|
|
@ -3026,6 +3056,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
|
|
@ -3050,6 +3081,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
|
|
@ -3786,6 +3818,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3907,6 +3940,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
|
|
@ -3932,6 +3966,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
|
|
@ -4001,6 +4036,7 @@ Comprehensive structural analysis with actionable recommendations
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/assemble-kdp-package.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/assemble-kdp-package.md
|
||||
|
|
@ -4032,6 +4068,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/brainstorm-premise.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Brainstorm Premise
|
||||
|
|
@ -4057,6 +4094,7 @@ steps:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
|
|
@ -4083,6 +4121,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
|
|
@ -4107,6 +4146,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -4212,6 +4252,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/create-draft-section.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Create Draft Section (Chapter)
|
||||
|
|
@ -4240,6 +4281,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
|
|
@ -4266,6 +4308,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -4356,6 +4399,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/expand-premise.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 7. Expand Premise (Snowflake Step 2)
|
||||
|
|
@ -4381,6 +4425,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/expand-synopsis.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 8. Expand Synopsis (Snowflake Step 4)
|
||||
|
|
@ -4406,6 +4451,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
|
|
@ -4431,6 +4477,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-cover-brief.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/generate-cover-brief.md
|
||||
|
|
@ -4458,6 +4505,7 @@ steps:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-cover-prompts.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/generate-cover-prompts.md
|
||||
|
|
@ -4486,6 +4534,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
|
|
@ -4511,6 +4560,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
|
|
@ -4538,6 +4588,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
|
|
@ -4563,6 +4614,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
|
|
@ -4589,6 +4641,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/publish-chapter.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Publish Chapter
|
||||
|
|
@ -4614,6 +4667,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
|
|
@ -4638,6 +4692,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/select-next-arc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Select Next Arc (Serial)
|
||||
|
|
@ -4663,6 +4718,7 @@ inputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
|
@ -4729,6 +4785,7 @@ Refined dialog with stronger voices and dramatic impact
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
|
|
@ -4754,6 +4811,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
|
|
@ -4779,6 +4837,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
|
|
@ -4804,6 +4863,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/cyberpunk-aesthetic-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 24. Cyberpunk Aesthetic Consistency Checklist
|
||||
|
|
@ -4829,6 +4889,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/ebook-formatting-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. eBook Formatting Checklist
|
||||
|
|
@ -4852,6 +4913,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/epic-poetry-meter-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 22. Epic Poetry Meter & Form Checklist
|
||||
|
|
@ -4877,6 +4939,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
|
|
@ -4902,6 +4965,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/foreshadowing-payoff-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Foreshadowing & Payoff Checklist
|
||||
|
|
@ -4926,6 +4990,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/historical-accuracy-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 18. Historical Accuracy Checklist
|
||||
|
|
@ -4951,6 +5016,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/horror-suspense-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Horror Suspense & Scare Checklist
|
||||
|
|
@ -4976,6 +5042,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/kdp-cover-ready-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# checklists/kdp-cover-ready-checklist.md
|
||||
|
|
@ -5003,6 +5070,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
|
|
@ -5028,6 +5096,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/marketing-copy-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Marketing Copy Checklist
|
||||
|
|
@ -5053,6 +5122,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/mystery-clue-trail-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Mystery Clue Trail Checklist
|
||||
|
|
@ -5078,6 +5148,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/orbital-mechanics-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 21. Hard‑Science Orbital Mechanics Checklist
|
||||
|
|
@ -5103,6 +5174,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
|
|
@ -5164,6 +5236,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
|
|
@ -5189,6 +5262,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
|
|
@ -5214,6 +5288,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/scene-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Scene Quality Checklist
|
||||
|
|
@ -5239,6 +5314,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
|
|
@ -5263,6 +5339,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/sensitivity-representation-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 7. Sensitivity & Representation Checklist
|
||||
|
|
@ -5288,6 +5365,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
|
|
@ -5313,6 +5391,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/thriller-pacing-stakes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 19. Thriller Pacing & Stakes Checklist
|
||||
|
|
@ -5338,6 +5417,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/timeline-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 8. Timeline & Continuity Checklist
|
||||
|
|
@ -5363,6 +5443,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
|
|
@ -5388,6 +5469,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/checklists/ya-appropriateness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 20. YA Appropriateness Checklist
|
||||
|
|
@ -5413,6 +5495,7 @@ items:
|
|||
|
||||
==================== START: .bmad-creative-writing/workflows/book-cover-design-workflow.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Book Cover Design Assets
|
||||
|
||||
# ============================================================
|
||||
|
|
@ -6147,6 +6230,7 @@ outputs:
|
|||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -6358,6 +6442,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
|||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
|
|
|||
|
|
@ -55,10 +55,7 @@ agent:
|
|||
id: game-qa
|
||||
title: Game Test Architect & TDD Enforcer (Godot)
|
||||
icon: 🎮🧪
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement,
|
||||
performance validation, and gameplay quality assurance. Ensures all code is
|
||||
test-first, performance targets are met, and player experience is validated.
|
||||
Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement, performance validation, and gameplay quality assurance. Ensures all code is test-first, performance targets are met, and player experience is validated. Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
customization: null
|
||||
persona:
|
||||
role: Game Test Architect & TDD Champion for Godot Development
|
||||
|
|
|
|||
|
|
@ -558,10 +558,7 @@ agent:
|
|||
id: game-qa
|
||||
title: Game Test Architect & TDD Enforcer (Godot)
|
||||
icon: 🎮🧪
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement,
|
||||
performance validation, and gameplay quality assurance. Ensures all code is
|
||||
test-first, performance targets are met, and player experience is validated.
|
||||
Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement, performance validation, and gameplay quality assurance. Ensures all code is test-first, performance targets are met, and player experience is validated. Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
customization: null
|
||||
persona:
|
||||
role: Game Test Architect & TDD Champion for Godot Development
|
||||
|
|
|
|||
|
|
@ -102,6 +102,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -207,6 +208,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/review-infrastructure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Review Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -370,6 +372,7 @@ REPEAT by Asking the user if they would like to perform another Reflective, Elic
|
|||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/validate-infrastructure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Validation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1588,6 +1591,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-infrastructure-devops/checklists/infrastructure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Change Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for validating infrastructure changes before deployment to production. The DevOps/Platform Engineer should systematically work through each item, ensuring the infrastructure is secure, compliant, resilient, and properly implemented according to organizational standards.
|
||||
|
|
@ -2076,6 +2080,7 @@ This checklist serves as a comprehensive framework for validating infrastructure
|
|||
|
||||
==================== START: .bmad-infrastructure-devops/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -309,6 +309,7 @@ persona:
|
|||
focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Numbered Options - Always use numbered lists when presenting choices to the user
|
||||
|
|
@ -353,10 +354,7 @@ agent:
|
|||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
|
|
@ -409,6 +407,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -530,6 +529,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -635,6 +635,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -714,6 +715,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -816,6 +818,7 @@ npx bmad-method install
|
|||
- **Cline**: VS Code extension with AI features
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
- **Auggie CLI (Augment Code)**: AI-powered development environment
|
||||
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
|
|
@ -1524,6 +1527,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -1682,6 +1686,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
@ -1755,6 +1760,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -1829,6 +1835,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -1919,6 +1926,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2108,6 +2116,7 @@ Document sharded successfully:
|
|||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2129,7 +2138,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -2387,6 +2396,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
|
|
@ -2573,6 +2583,7 @@ Keep it action-oriented and forward-looking.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
|
|
@ -3009,6 +3020,7 @@ After presenting the report, ask if the user wants:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3125,6 +3137,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
|||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Draft Checklist
|
||||
|
||||
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
|
||||
|
|
@ -3282,6 +3295,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
|||
|
||||
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# apply-qa-fixes
|
||||
|
||||
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
|
||||
|
|
@ -3434,6 +3448,7 @@ Fix plan:
|
|||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
|
@ -3532,6 +3547,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
|||
|
||||
==================== START: .bmad-core/tasks/nfr-assess.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
|
|
@ -3879,6 +3895,7 @@ performance_deep_dive:
|
|||
|
||||
==================== START: .bmad-core/tasks/qa-gate.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
|
|
@ -4044,6 +4061,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
|||
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# review-story
|
||||
|
||||
Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
|
||||
|
|
@ -4362,6 +4380,7 @@ After review:
|
|||
|
||||
==================== START: .bmad-core/tasks/risk-profile.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
|
|
@ -4719,6 +4738,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
|
|||
|
||||
==================== START: .bmad-core/tasks/test-design.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
|
|
@ -4897,6 +4917,7 @@ Before finalizing, verify:
|
|||
|
||||
==================== START: .bmad-core/tasks/trace-requirements.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
|
|
@ -5271,6 +5292,7 @@ optional_fields_examples:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
|
|||
|
|
@ -226,6 +226,7 @@ commands:
|
|||
- doc-out: Output full document in progress to current destination file
|
||||
- elicit: run the task advanced-elicitation
|
||||
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
|
|
@ -239,6 +240,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- facilitate-brainstorming-session.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- brainstorming-output-tmpl.yaml
|
||||
- competitor-analysis-tmpl.yaml
|
||||
|
|
@ -288,6 +290,7 @@ commands:
|
|||
- create-prd: run task create-doc.md with template prd-tmpl.yaml
|
||||
- create-story: Create user story from requirements (task brownfield-create-story)
|
||||
- doc-out: Output full document to current destination file
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
|
||||
- yolo: Toggle Yolo Mode
|
||||
- exit: Exit (confirm)
|
||||
|
|
@ -304,6 +307,7 @@ dependencies:
|
|||
- create-deep-research-prompt.md
|
||||
- create-doc.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
- shard-doc.md
|
||||
templates:
|
||||
- brownfield-prd-tmpl.yaml
|
||||
|
|
@ -354,7 +358,8 @@ commands:
|
|||
- 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
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
- research-prompt {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
|
||||
|
|
@ -368,6 +373,7 @@ dependencies:
|
|||
- create-doc.md
|
||||
- document-project.md
|
||||
- execute-checklist.md
|
||||
- request-research.md
|
||||
templates:
|
||||
- architecture-tmpl.yaml
|
||||
- brownfield-architecture-tmpl.yaml
|
||||
|
|
@ -437,6 +443,7 @@ dependencies:
|
|||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -558,6 +565,7 @@ Choose a number (0-8) or 9 to proceed:
|
|||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
|
@ -663,6 +671,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -742,6 +751,7 @@ Or ask me about anything else related to BMad-Method!
|
|||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
|
@ -844,6 +854,7 @@ npx bmad-method install
|
|||
- **Cline**: VS Code extension with AI features
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
- **Auggie CLI (Augment Code)**: AI-powered development environment
|
||||
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
|
|
@ -1552,6 +1563,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
|
@ -1710,6 +1722,7 @@ Use the **expansion-creator** pack to build your own:
|
|||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
|
@ -1783,6 +1796,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
|||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# 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.
|
||||
|
|
@ -2065,6 +2079,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
|||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
|
@ -2411,10 +2426,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
|||
==================== END: .bmad-core/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
|
@ -2550,6 +2566,255 @@ Generate structured document with these sections:
|
|||
- Respect their process and timing
|
||||
==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/request-research.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Request Research Task
|
||||
|
||||
## Purpose
|
||||
|
||||
This task provides a unified interface for any agent to request specialized research from the Research Coordinator, which can spawn up to 3 domain-specific researcher agents to attack problems from different angles.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Multi-Perspective Analysis**: Coordinator spawns specialized researchers with different domain expertise
|
||||
- **Web Search Capabilities**: Researchers have access to current information and data
|
||||
- **Adaptive Specialization**: Research agents adapt to specific domains as needed by the requesting context
|
||||
- **Research Logging**: All synthesis results stored in indexed research log to avoid duplicate work
|
||||
- **Configurable Team Size**: Default 3 researchers, configurable based on complexity
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### From Any Agent
|
||||
Any agent can call this task to get specialized research assistance:
|
||||
|
||||
```yaml
|
||||
*task request-research
|
||||
```
|
||||
|
||||
### Common Use Cases
|
||||
|
||||
- **Analyst**: Competitive analysis, market research, industry trends
|
||||
- **Architect**: Technology assessment, scalability analysis, security research
|
||||
- **PM**: Market validation, user research, feasibility studies
|
||||
- **Dev**: Technical implementation research, library comparisons, best practices
|
||||
- **QA**: Testing methodologies, quality standards, compliance requirements
|
||||
|
||||
## Task Process
|
||||
|
||||
### 1. Research Request Specification
|
||||
|
||||
The task will elicit a structured research request with these components:
|
||||
|
||||
#### Research Context
|
||||
- **Requesting Agent**: Which agent is making the request
|
||||
- **Project Context**: Current project phase and relevant background
|
||||
- **Previous Research**: Check research log for related prior work
|
||||
- **Urgency Level**: Timeline constraints and priority
|
||||
|
||||
#### Research Objective
|
||||
- **Primary Goal**: What specific question or problem needs researching
|
||||
- **Success Criteria**: How to measure if research achieved its objective
|
||||
- **Scope Boundaries**: What to include/exclude from research
|
||||
- **Decision Impact**: How results will be used
|
||||
|
||||
#### Domain Specialization Requirements
|
||||
- **Primary Domain**: Main area of expertise needed (technical, market, user, etc.)
|
||||
- **Secondary Domains**: Additional perspectives required
|
||||
- **Specific Expertise**: Particular skills or knowledge areas
|
||||
- **Research Depth**: High-level overview vs deep technical analysis
|
||||
|
||||
#### Output Requirements
|
||||
- **Format**: Executive summary, detailed report, comparison matrix, etc.
|
||||
- **Audience**: Who will consume the research results
|
||||
- **Integration**: How results feed into next steps
|
||||
- **Documentation**: Level of source citation needed
|
||||
|
||||
### 2. Research Coordination
|
||||
|
||||
The Research Coordinator will:
|
||||
|
||||
1. **Check Research Log**: Review `docs/research/research-index.md` for prior related work
|
||||
2. **Design Research Strategy**: Plan multi-perspective approach
|
||||
3. **Spawn Researcher Agents**: Deploy 1-3 specialized researchers with distinct angles
|
||||
4. **Monitor Progress**: Coordinate between researchers to avoid overlap
|
||||
5. **Synthesize Results**: Combine findings into coherent analysis
|
||||
|
||||
### 3. Research Execution
|
||||
|
||||
Each Researcher Agent will:
|
||||
|
||||
1. **Adapt Domain Expertise**: Configure specialization based on assigned perspective
|
||||
2. **Conduct Web Research**: Use search capabilities to gather current information
|
||||
3. **Analyze and Synthesize**: Process information through domain-specific lens
|
||||
4. **Generate Findings**: Create structured report for their perspective
|
||||
5. **Cite Sources**: Document credible sources and evidence
|
||||
|
||||
### 4. Result Delivery
|
||||
|
||||
#### To Requesting Agent
|
||||
- **Executive Summary**: Key findings and recommendations
|
||||
- **Detailed Analysis**: Comprehensive research results
|
||||
- **Source Documentation**: Links and citations for verification
|
||||
- **Next Steps**: Recommended actions or follow-up research
|
||||
|
||||
#### To Research Log
|
||||
- **Research Entry**: Concise summary stored in `docs/research/YYYY-MM-DD-research-topic.md`
|
||||
- **Index Update**: Add entry to `docs/research/research-index.md`
|
||||
- **Tag Classification**: Add searchable tags for future reference
|
||||
|
||||
### 5. Quality Assurance
|
||||
|
||||
- **Source Credibility**: Verify information from reputable sources
|
||||
- **Cross-Perspective Validation**: Ensure consistency across researcher findings
|
||||
- **Bias Detection**: Identify and flag potential biases or limitations
|
||||
- **Completeness Check**: Confirm all research objectives addressed
|
||||
|
||||
## Research Request Template
|
||||
|
||||
When executing this task, use this structure for research requests:
|
||||
|
||||
```yaml
|
||||
research_request:
|
||||
metadata:
|
||||
requesting_agent: "[agent-id]"
|
||||
request_date: "[YYYY-MM-DD]"
|
||||
priority: "[high|medium|low]"
|
||||
timeline: "[timeframe needed]"
|
||||
|
||||
context:
|
||||
project_phase: "[planning|development|validation|etc]"
|
||||
background: "[relevant project context]"
|
||||
related_docs: "[PRD, architecture, stories, etc]"
|
||||
previous_research: "[check research log references]"
|
||||
|
||||
objective:
|
||||
primary_goal: "[specific research question]"
|
||||
success_criteria: "[how to measure success]"
|
||||
scope: "[boundaries and limitations]"
|
||||
decision_impact: "[how results will be used]"
|
||||
|
||||
specialization:
|
||||
primary_domain: "[technical|market|user|competitive|regulatory|etc]"
|
||||
secondary_domains: "[additional perspectives needed]"
|
||||
specific_expertise: "[particular skills required]"
|
||||
research_depth: "[overview|detailed|comprehensive]"
|
||||
|
||||
team_config:
|
||||
researcher_count: "[1-3, default 3]"
|
||||
perspective_1: "[domain and focus area]"
|
||||
perspective_2: "[domain and focus area]"
|
||||
perspective_3: "[domain and focus area]"
|
||||
|
||||
output:
|
||||
format: "[executive_summary|detailed_report|comparison_matrix|etc]"
|
||||
audience: "[who will use results]"
|
||||
integration: "[how results feed into workflow]"
|
||||
citation_level: "[minimal|standard|comprehensive]"
|
||||
```
|
||||
|
||||
## Integration with Existing Agents
|
||||
|
||||
### Adding Research Capability to Agents
|
||||
|
||||
To add research capabilities to existing agents, add this dependency:
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- request-research.md
|
||||
```
|
||||
|
||||
Then add a research command:
|
||||
|
||||
```yaml
|
||||
commands:
|
||||
- research {topic}: Request specialized research analysis using task request-research
|
||||
```
|
||||
|
||||
### Research Command Examples
|
||||
|
||||
- `*research "competitor API pricing models"` (from PM)
|
||||
- `*research "microservices vs monolith for our scale"` (from Architect)
|
||||
- `*research "React vs Vue for dashboard components"` (from Dev)
|
||||
- `*research "automated testing strategies for ML models"` (from QA)
|
||||
|
||||
## Research Log Structure
|
||||
|
||||
### Research Index (`docs/research/research-index.md`)
|
||||
```markdown
|
||||
# Research Index
|
||||
|
||||
## Recent Research
|
||||
- [2024-01-15: AI Model Comparison](2024-01-15-ai-model-comparison.md) - Technical analysis of LLM options
|
||||
- [2024-01-12: Payment Gateway Analysis](2024-01-12-payment-gateway-analysis.md) - Market comparison of payment solutions
|
||||
|
||||
## Research by Category
|
||||
### Technical Research
|
||||
- AI/ML Models
|
||||
- Architecture Decisions
|
||||
- Technology Stacks
|
||||
|
||||
### Market Research
|
||||
- Competitive Analysis
|
||||
- User Behavior
|
||||
- Industry Trends
|
||||
```
|
||||
|
||||
### Individual Research Files (`docs/research/YYYY-MM-DD-topic.md`)
|
||||
```markdown
|
||||
# Research: [Topic]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Requested by**: [agent-name]
|
||||
**Research Team**: [perspectives used]
|
||||
|
||||
## Executive Summary
|
||||
[Key findings and recommendations]
|
||||
|
||||
## Research Objective
|
||||
[What was being researched and why]
|
||||
|
||||
## Key Findings
|
||||
[Main insights from all perspectives]
|
||||
|
||||
## Recommendations
|
||||
[Actionable next steps]
|
||||
|
||||
## Research Team Perspectives
|
||||
### Perspective 1: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 2: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
### Perspective 3: [Domain]
|
||||
[Key insights from this angle]
|
||||
|
||||
## Sources and References
|
||||
[Credible sources cited by research team]
|
||||
|
||||
## Tags
|
||||
[Searchable tags for future reference]
|
||||
```
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Research Log Maintenance**: Research Coordinator automatically maintains the research index
|
||||
- **Duplicate Prevention**: Always check existing research before launching new requests
|
||||
- **Source Quality**: Prioritize credible, recent sources with proper attribution
|
||||
- **Perspective Diversity**: Ensure research angles provide genuinely different viewpoints
|
||||
- **Synthesis Quality**: Coordinator must reconcile conflicting findings and highlight uncertainties
|
||||
- **Integration Focus**: All research should provide actionable insights for decision-making
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Web Search Failures**: Graceful degradation to available information
|
||||
- **Conflicting Research**: Document disagreements and uncertainty levels
|
||||
- **Incomplete Coverage**: Flag areas needing additional research
|
||||
- **Source Quality Issues**: Clearly mark uncertain or low-confidence findings
|
||||
==================== END: .bmad-core/tasks/request-research.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
template:
|
||||
id: brainstorming-output-template-v2
|
||||
|
|
@ -3502,6 +3767,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
|
@ -3542,6 +3808,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3706,6 +3973,7 @@ The epic creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3857,6 +4125,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -3931,6 +4200,7 @@ The story creation is successful when:
|
|||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
|
|
@ -4021,6 +4291,7 @@ The LLM will:
|
|||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -4700,6 +4971,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
|
|
@ -4886,6 +5158,7 @@ Keep it action-oriented and forward-looking.]]
|
|||
|
||||
==================== START: .bmad-core/checklists/pm-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
|
||||
|
|
@ -5260,6 +5533,7 @@ After presenting the report, ask if the user wants:
|
|||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
|
@ -6031,8 +6305,8 @@ sections:
|
|||
- **UI/UX Consistency:** {{ui_compatibility}}
|
||||
- **Performance Impact:** {{performance_constraints}}
|
||||
|
||||
- id: tech-stack-alignment
|
||||
title: Tech Stack Alignment
|
||||
- id: tech-stack
|
||||
title: Tech Stack
|
||||
instruction: |
|
||||
Ensure new components align with existing technology choices:
|
||||
|
||||
|
|
@ -6194,8 +6468,8 @@ sections:
|
|||
|
||||
**Error Handling:** {{error_handling_strategy}}
|
||||
|
||||
- id: source-tree-integration
|
||||
title: Source Tree Integration
|
||||
- id: source-tree
|
||||
title: Source Tree
|
||||
instruction: |
|
||||
Define how new code will integrate with existing project structure:
|
||||
|
||||
|
|
@ -6264,7 +6538,7 @@ sections:
|
|||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
|
|
@ -7450,6 +7724,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
|
||||
|
|
@ -7892,6 +8167,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
|||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
|
@ -7913,7 +8189,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
|
|||
|
||||
### 1. Template Completeness Validation
|
||||
|
||||
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
|
||||
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
|
||||
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
|
||||
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
|
||||
- **Agent section verification**: Confirm all sections from template exist for future agent use
|
||||
|
|
@ -8171,6 +8447,7 @@ sections:
|
|||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
|
|
@ -8722,7 +8999,7 @@ workflow:
|
|||
- Dev Agent (New Chat): Address remaining items
|
||||
- Return to QA for final approval
|
||||
|
||||
- repeat_development_cycle:
|
||||
- step: repeat_development_cycle
|
||||
action: continue_for_all_stories
|
||||
notes: |
|
||||
Repeat story cycle (SM → Dev → QA) for all epic stories
|
||||
|
|
@ -8739,7 +9016,7 @@ workflow:
|
|||
- Validate epic was completed correctly
|
||||
- Document learnings and improvements
|
||||
|
||||
- workflow_end:
|
||||
- step: workflow_end
|
||||
action: project_complete
|
||||
notes: |
|
||||
All stories implemented and reviewed!
|
||||
|
|
@ -8924,7 +9201,7 @@ workflow:
|
|||
- Dev Agent (New Chat): Address remaining items
|
||||
- Return to QA for final approval
|
||||
|
||||
- repeat_development_cycle:
|
||||
- step: repeat_development_cycle
|
||||
action: continue_for_all_stories
|
||||
notes: |
|
||||
Repeat story cycle (SM → Dev → QA) for all epic stories
|
||||
|
|
@ -8941,7 +9218,7 @@ workflow:
|
|||
- Validate epic was completed correctly
|
||||
- Document learnings and improvements
|
||||
|
||||
- workflow_end:
|
||||
- step: workflow_end
|
||||
action: project_complete
|
||||
notes: |
|
||||
All stories implemented and reviewed!
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue