mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
research will use the web more, use system date to understand what the read current date is.
This commit is contained in:
Brian Madison
@@ -0,0 +1,144 @@
|
||||
# Deep Research Prompt Validation Checklist
|
||||
|
||||
## 🚨 CRITICAL: Anti-Hallucination Instructions (PRIORITY)
|
||||
|
||||
### Citation Requirements Built Into Prompt
|
||||
|
||||
- [ ] Prompt EXPLICITLY instructs: "Cite sources with URLs for ALL factual claims"
|
||||
- [ ] Prompt requires: "Include source name, date, and URL for every statistic"
|
||||
- [ ] Prompt mandates: "If you cannot find reliable data, state 'No verified data found for [X]'"
|
||||
- [ ] Prompt specifies inline citation format (e.g., "[Source: Company, Year, URL]")
|
||||
- [ ] Prompt requires References section at end with all sources listed
|
||||
|
||||
### Multi-Source Verification Requirements
|
||||
|
||||
- [ ] Prompt instructs: "Cross-reference critical claims with at least 2 independent sources"
|
||||
- [ ] Prompt requires: "Note when sources conflict and present all viewpoints"
|
||||
- [ ] Prompt specifies: "Verify version numbers and dates from official sources"
|
||||
- [ ] Prompt mandates: "Mark confidence levels: [Verified], [Single source], [Uncertain]"
|
||||
|
||||
### Fact vs Analysis Distinction
|
||||
|
||||
- [ ] Prompt requires clear labeling: "Distinguish FACTS (sourced), ANALYSIS (your interpretation), SPECULATION (projections)"
|
||||
- [ ] Prompt instructs: "Do not present assumptions or analysis as verified facts"
|
||||
- [ ] Prompt requires: "Label projections and forecasts clearly as such"
|
||||
- [ ] Prompt warns: "Avoid vague attributions like 'experts say' - name the expert/source"
|
||||
|
||||
### Source Quality Guidance
|
||||
|
||||
- [ ] Prompt specifies preferred sources (e.g., "Official docs > analyst reports > blog posts")
|
||||
- [ ] Prompt prioritizes recency: "Prioritize {{current_year}} sources for time-sensitive data"
|
||||
- [ ] Prompt requires credibility assessment: "Note source credibility for each citation"
|
||||
- [ ] Prompt warns against: "Do not rely on single blog posts for critical claims"
|
||||
|
||||
### Anti-Hallucination Safeguards
|
||||
|
||||
- [ ] Prompt warns: "If data seems convenient or too round, verify with additional sources"
|
||||
- [ ] Prompt instructs: "Flag suspicious claims that need third-party verification"
|
||||
- [ ] Prompt requires: "Provide date accessed for all web sources"
|
||||
- [ ] Prompt mandates: "Do NOT invent statistics - only use verified data"
|
||||
|
||||
## Prompt Foundation
|
||||
|
||||
### Topic and Scope
|
||||
|
||||
- [ ] Research topic is specific and focused (not too broad)
|
||||
- [ ] Target platform is specified (ChatGPT, Gemini, Grok, Claude)
|
||||
- [ ] Temporal scope defined and includes "current {{current_year}}" requirement
|
||||
- [ ] Source recency requirement specified (e.g., "prioritize 2024-2025 sources")
|
||||
|
||||
## Content Requirements
|
||||
|
||||
### Information Specifications
|
||||
|
||||
- [ ] Types of information needed are listed (quantitative, qualitative, trends, case studies, etc.)
|
||||
- [ ] Preferred sources are specified (academic, industry reports, news, etc.)
|
||||
- [ ] Recency requirements are stated (e.g., "prioritize {{current_year}} sources")
|
||||
- [ ] Keywords and technical terms are included for search optimization
|
||||
- [ ] Validation criteria are defined (how to verify findings)
|
||||
|
||||
### Output Structure
|
||||
|
||||
- [ ] Desired format is clear (executive summary, comparison table, timeline, SWOT, etc.)
|
||||
- [ ] Key sections or questions are outlined
|
||||
- [ ] Depth level is specified (overview, standard, comprehensive, exhaustive)
|
||||
- [ ] Citation requirements are stated
|
||||
- [ ] Any special formatting needs are mentioned
|
||||
|
||||
## Platform Optimization
|
||||
|
||||
### Platform-Specific Elements
|
||||
|
||||
- [ ] Prompt is optimized for chosen platform's capabilities
|
||||
- [ ] Platform-specific tips are included
|
||||
- [ ] Query limit considerations are noted (if applicable)
|
||||
- [ ] Platform strengths are leveraged (e.g., ChatGPT's multi-step search, Gemini's plan modification)
|
||||
|
||||
### Execution Guidance
|
||||
|
||||
- [ ] Research persona/perspective is specified (if applicable)
|
||||
- [ ] Special requirements are stated (bias considerations, recency, etc.)
|
||||
- [ ] Follow-up strategy is outlined
|
||||
- [ ] Validation approach is defined
|
||||
|
||||
## Quality and Usability
|
||||
|
||||
### Clarity and Completeness
|
||||
|
||||
- [ ] Prompt language is clear and unambiguous
|
||||
- [ ] All placeholders and variables are replaced with actual values
|
||||
- [ ] Prompt can be copy-pasted directly into platform
|
||||
- [ ] No contradictory instructions exist
|
||||
- [ ] Prompt is self-contained (doesn't assume unstated context)
|
||||
|
||||
### Practical Utility
|
||||
|
||||
- [ ] Execution checklist is provided (before, during, after research)
|
||||
- [ ] Platform usage tips are included
|
||||
- [ ] Follow-up questions are anticipated
|
||||
- [ ] Success criteria are defined
|
||||
- [ ] Output file format is specified
|
||||
|
||||
## Research Depth
|
||||
|
||||
### Scope Appropriateness
|
||||
|
||||
- [ ] Scope matches user's available time and resources
|
||||
- [ ] Depth is appropriate for decision at hand
|
||||
- [ ] Key questions that MUST be answered are identified
|
||||
- [ ] Nice-to-have vs. critical information is distinguished
|
||||
|
||||
## Validation Criteria
|
||||
|
||||
### Quality Standards
|
||||
|
||||
- [ ] Method for cross-referencing sources is specified
|
||||
- [ ] Approach to handling conflicting information is defined
|
||||
- [ ] Confidence level indicators are requested
|
||||
- [ ] Gap identification is included
|
||||
- [ ] Fact vs. opinion distinction is required
|
||||
|
||||
---
|
||||
|
||||
## Issues Found
|
||||
|
||||
### Critical Issues
|
||||
|
||||
_List any critical gaps or errors that must be addressed:_
|
||||
|
||||
- [ ] Issue 1: [Description]
|
||||
- [ ] Issue 2: [Description]
|
||||
|
||||
### Minor Improvements
|
||||
|
||||
_List minor improvements that would enhance the prompt:_
|
||||
|
||||
- [ ] Issue 1: [Description]
|
||||
- [ ] Issue 2: [Description]
|
||||
|
||||
---
|
||||
|
||||
**Validation Complete:** ☐ Yes ☐ No
|
||||
**Ready to Execute:** ☐ Yes ☐ No
|
||||
**Reviewer:** \***\*\_\*\***
|
||||
**Date:** \***\*\_\*\***
|
||||
@@ -0,0 +1,249 @@
|
||||
# Technical/Architecture Research Validation Checklist
|
||||
|
||||
## 🚨 CRITICAL: Source Verification and Fact-Checking (PRIORITY)
|
||||
|
||||
### Version Number Verification (MANDATORY)
|
||||
|
||||
- [ ] **EVERY** technology version number has cited source with URL
|
||||
- [ ] Version numbers verified via WebSearch from {{current_year}} (NOT from training data!)
|
||||
- [ ] Official documentation/release pages cited for each version
|
||||
- [ ] Release dates included with version numbers
|
||||
- [ ] LTS status verified from official sources (with URL)
|
||||
- [ ] No "assumed" or "remembered" version numbers - ALL must be verified
|
||||
|
||||
### Technical Claim Source Verification
|
||||
|
||||
- [ ] **EVERY** feature claim has source (official docs, release notes, website)
|
||||
- [ ] Performance benchmarks cite source (official benchmarks, third-party tests with URLs)
|
||||
- [ ] Compatibility claims verified (official compatibility matrix, documentation)
|
||||
- [ ] Community size/popularity backed by sources (GitHub stars, npm downloads, official stats)
|
||||
- [ ] "Supports X" claims verified via official documentation with URL
|
||||
- [ ] No invented capabilities or features
|
||||
|
||||
### Source Quality for Technical Data
|
||||
|
||||
- [ ] Official documentation prioritized (docs.technology.com > blog posts)
|
||||
- [ ] Version info from official release pages (highest credibility)
|
||||
- [ ] Benchmarks from official sources or reputable third-parties (not random blogs)
|
||||
- [ ] Community data from verified sources (GitHub, npm, official registries)
|
||||
- [ ] Pricing from official pricing pages (with URL and date verified)
|
||||
|
||||
### Multi-Source Verification (Critical Technical Claims)
|
||||
|
||||
- [ ] Major technical claims (performance, scalability) verified by 2+ sources
|
||||
- [ ] Technology comparisons cite multiple independent sources
|
||||
- [ ] "Best for X" claims backed by comparative analysis with sources
|
||||
- [ ] Production experience claims cite real case studies or articles with URLs
|
||||
- [ ] No single-source critical decisions without flagging need for verification
|
||||
|
||||
### Anti-Hallucination for Technical Data
|
||||
|
||||
- [ ] No invented version numbers or release dates
|
||||
- [ ] No assumed feature availability without verification
|
||||
- [ ] If current data not found, explicitly states "Could not verify {{current_year}} information"
|
||||
- [ ] Speculation clearly labeled (e.g., "Based on trends, technology may...")
|
||||
- [ ] No "probably supports" or "likely compatible" without verification
|
||||
|
||||
## Technology Evaluation
|
||||
|
||||
### Comprehensive Profiling
|
||||
|
||||
For each evaluated technology:
|
||||
|
||||
- [ ] Core capabilities and features are documented
|
||||
- [ ] Architecture and design philosophy are explained
|
||||
- [ ] Maturity level is assessed (experimental, stable, mature, legacy)
|
||||
- [ ] Community size and activity are measured
|
||||
- [ ] Maintenance status is verified (active, maintenance mode, abandoned)
|
||||
|
||||
### Practical Considerations
|
||||
|
||||
- [ ] Learning curve is evaluated
|
||||
- [ ] Documentation quality is assessed
|
||||
- [ ] Developer experience is considered
|
||||
- [ ] Tooling ecosystem is reviewed
|
||||
- [ ] Testing and debugging capabilities are examined
|
||||
|
||||
### Operational Assessment
|
||||
|
||||
- [ ] Deployment complexity is understood
|
||||
- [ ] Monitoring and observability options are evaluated
|
||||
- [ ] Operational overhead is estimated
|
||||
- [ ] Cloud provider support is verified
|
||||
- [ ] Container/Kubernetes compatibility is checked (if relevant)
|
||||
|
||||
## Comparative Analysis
|
||||
|
||||
### Multi-Dimensional Comparison
|
||||
|
||||
- [ ] Technologies are compared across relevant dimensions
|
||||
- [ ] Performance benchmarks are included (if available)
|
||||
- [ ] Scalability characteristics are compared
|
||||
- [ ] Complexity trade-offs are analyzed
|
||||
- [ ] Total cost of ownership is estimated for each option
|
||||
|
||||
### Trade-off Analysis
|
||||
|
||||
- [ ] Key trade-offs between options are identified
|
||||
- [ ] Decision factors are prioritized based on user needs
|
||||
- [ ] Conditions favoring each option are specified
|
||||
- [ ] Weighted analysis reflects user's priorities
|
||||
|
||||
## Real-World Evidence
|
||||
|
||||
### Production Experience
|
||||
|
||||
- [ ] Real-world production experiences are researched
|
||||
- [ ] Known issues and gotchas are documented
|
||||
- [ ] Performance data from actual deployments is included
|
||||
- [ ] Migration experiences are considered (if replacing existing tech)
|
||||
- [ ] Community discussions and war stories are referenced
|
||||
|
||||
### Source Quality
|
||||
|
||||
- [ ] Multiple independent sources validate key claims
|
||||
- [ ] Recent sources from {{current_year}} are prioritized
|
||||
- [ ] Practitioner experiences are included (blog posts, conference talks, forums)
|
||||
- [ ] Both proponent and critic perspectives are considered
|
||||
|
||||
## Decision Support
|
||||
|
||||
### Recommendations
|
||||
|
||||
- [ ] Primary recommendation is clearly stated with rationale
|
||||
- [ ] Alternative options are explained with use cases
|
||||
- [ ] Fit for user's specific context is explained
|
||||
- [ ] Decision is justified by requirements and constraints
|
||||
|
||||
### Implementation Guidance
|
||||
|
||||
- [ ] Proof-of-concept approach is outlined
|
||||
- [ ] Key implementation decisions are identified
|
||||
- [ ] Migration path is described (if applicable)
|
||||
- [ ] Success criteria are defined
|
||||
- [ ] Validation approach is recommended
|
||||
|
||||
### Risk Management
|
||||
|
||||
- [ ] Technical risks are identified
|
||||
- [ ] Mitigation strategies are provided
|
||||
- [ ] Contingency options are outlined (if primary choice doesn't work)
|
||||
- [ ] Exit strategy considerations are discussed
|
||||
|
||||
## Architecture Decision Record
|
||||
|
||||
### ADR Completeness
|
||||
|
||||
- [ ] Status is specified (Proposed, Accepted, Superseded)
|
||||
- [ ] Context and problem statement are clear
|
||||
- [ ] Decision drivers are documented
|
||||
- [ ] All considered options are listed
|
||||
- [ ] Chosen option and rationale are explained
|
||||
- [ ] Consequences (positive, negative, neutral) are identified
|
||||
- [ ] Implementation notes are included
|
||||
- [ ] References to research sources are provided
|
||||
|
||||
## References and Source Documentation (CRITICAL)
|
||||
|
||||
### References Section Completeness
|
||||
|
||||
- [ ] Report includes comprehensive "References and Sources" section
|
||||
- [ ] Sources organized by category (official docs, benchmarks, community, architecture)
|
||||
- [ ] Every source includes: Title, Publisher/Site, Date Accessed, Full URL
|
||||
- [ ] URLs are clickable and functional (documentation links, release pages, GitHub)
|
||||
- [ ] Version verification sources clearly listed
|
||||
- [ ] Inline citations throughout report reference the sources section
|
||||
|
||||
### Technology Source Documentation
|
||||
|
||||
- [ ] For each technology evaluated, sources documented:
|
||||
- Official documentation URL
|
||||
- Release notes/changelog URL for version
|
||||
- Pricing page URL (if applicable)
|
||||
- Community/GitHub URL
|
||||
- Benchmark source URLs
|
||||
- [ ] Comparison data cites source for each claim
|
||||
- [ ] Architecture pattern sources cited (articles, books, official guides)
|
||||
|
||||
### Source Quality Metrics
|
||||
|
||||
- [ ] Report documents total sources cited
|
||||
- [ ] Official sources count (highest credibility)
|
||||
- [ ] Third-party sources count (benchmarks, articles)
|
||||
- [ ] Version verification count (all technologies verified {{current_year}})
|
||||
- [ ] Outdated sources flagged (if any used)
|
||||
|
||||
### Citation Format Standards
|
||||
|
||||
- [ ] Inline citations format: [Source: Docs URL] or [Version: 1.2.3, Source: Release Page URL]
|
||||
- [ ] Consistent citation style throughout
|
||||
- [ ] No vague citations like "according to the community" without specifics
|
||||
- [ ] GitHub links include star count and last update date
|
||||
- [ ] Documentation links point to current stable version docs
|
||||
|
||||
## Document Quality
|
||||
|
||||
### Anti-Hallucination Final Check
|
||||
|
||||
- [ ] Spot-check 5 random version numbers - can you find the cited source?
|
||||
- [ ] Verify feature claims against official documentation
|
||||
- [ ] Check any performance numbers have benchmark sources
|
||||
- [ ] Ensure no "cutting edge" or "latest" without specific version number
|
||||
- [ ] Cross-check technology comparisons with cited sources
|
||||
|
||||
### Structure and Completeness
|
||||
|
||||
- [ ] Executive summary captures key findings
|
||||
- [ ] No placeholder text remains (all {{variables}} are replaced)
|
||||
- [ ] References section is complete and properly formatted
|
||||
- [ ] Version verification audit trail included
|
||||
- [ ] Document ready for technical fact-checking by third party
|
||||
|
||||
## Research Completeness
|
||||
|
||||
### Coverage
|
||||
|
||||
- [ ] All user requirements were addressed
|
||||
- [ ] All constraints were considered
|
||||
- [ ] Sufficient depth for the decision at hand
|
||||
- [ ] Optional analyses were considered and included/excluded appropriately
|
||||
- [ ] Web research was conducted for current market data
|
||||
|
||||
### Data Freshness
|
||||
|
||||
- [ ] Current {{current_year}} data was used throughout
|
||||
- [ ] Version information is up-to-date
|
||||
- [ ] Recent developments and trends are included
|
||||
- [ ] Outdated or deprecated information is flagged or excluded
|
||||
|
||||
---
|
||||
|
||||
## Issues Found
|
||||
|
||||
### Critical Issues
|
||||
|
||||
_List any critical gaps or errors that must be addressed:_
|
||||
|
||||
- [ ] Issue 1: [Description]
|
||||
- [ ] Issue 2: [Description]
|
||||
|
||||
### Minor Improvements
|
||||
|
||||
_List minor improvements that would enhance the report:_
|
||||
|
||||
- [ ] Issue 1: [Description]
|
||||
- [ ] Issue 2: [Description]
|
||||
|
||||
### Additional Research Needed
|
||||
|
||||
_List areas requiring further investigation:_
|
||||
|
||||
- [ ] Topic 1: [Description]
|
||||
- [ ] Topic 2: [Description]
|
||||
|
||||
---
|
||||
|
||||
**Validation Complete:** ☐ Yes ☐ No
|
||||
**Ready for Decision:** ☐ Yes ☐ No
|
||||
**Reviewer:** \***\*\_\*\***
|
||||
**Date:** \***\*\_\*\***
|
||||
@@ -1,67 +1,129 @@
|
||||
# Market Research Report Validation Checklist
|
||||
|
||||
## Research Foundation
|
||||
## 🚨 CRITICAL: Source Verification and Fact-Checking (PRIORITY)
|
||||
|
||||
### Objectives and Scope
|
||||
### Source Citation Completeness
|
||||
|
||||
- [ ] Research objectives are clearly stated with specific questions to answer
|
||||
- [ ] Market boundaries are explicitly defined (product category, geography, segments)
|
||||
- [ ] Research methodology is documented with data sources and timeframes
|
||||
- [ ] Limitations and assumptions are transparently acknowledged
|
||||
- [ ] **EVERY** market size claim has at least 2 cited sources with URLs
|
||||
- [ ] **EVERY** growth rate/CAGR has cited sources with URLs
|
||||
- [ ] **EVERY** competitive data point (pricing, features, funding) has sources with URLs
|
||||
- [ ] **EVERY** customer statistic or insight has cited sources
|
||||
- [ ] **EVERY** industry trend claim has sources from {{current_year}} or recent years
|
||||
- [ ] All sources include: Name, Date, URL (clickable links)
|
||||
- [ ] No claims exist without verifiable sources
|
||||
|
||||
### Data Quality
|
||||
### Source Quality and Credibility
|
||||
|
||||
- [ ] All data sources are cited with dates and links where applicable
|
||||
- [ ] Data is no more than 12 months old for time-sensitive metrics
|
||||
- [ ] At least 3 independent sources validate key market size claims
|
||||
- [ ] Source credibility is assessed (primary > industry reports > news articles)
|
||||
- [ ] Conflicting data points are acknowledged and reconciled
|
||||
- [ ] Market size sources are HIGH credibility (Gartner, Forrester, IDC, government data, industry associations)
|
||||
- [ ] NOT relying on single blog posts or unverified sources for critical data
|
||||
- [ ] Sources are recent ({{current_year}} or within 1-2 years for time-sensitive data)
|
||||
- [ ] Primary sources prioritized over secondary/tertiary sources
|
||||
- [ ] Paywalled reports are cited with proper attribution (e.g., "Gartner Market Report 2025")
|
||||
|
||||
## Market Sizing Analysis
|
||||
### Multi-Source Verification (Critical Claims)
|
||||
|
||||
### TAM Calculation
|
||||
- [ ] TAM calculation verified by at least 2 independent sources
|
||||
- [ ] SAM calculation methodology is transparent and sourced
|
||||
- [ ] SOM estimates are conservative and based on comparable benchmarks
|
||||
- [ ] Market growth rates corroborated by multiple analyst reports
|
||||
- [ ] Competitive market share data verified across sources
|
||||
|
||||
- [ ] At least 2 different calculation methods are used (top-down, bottom-up, or value theory)
|
||||
- [ ] All assumptions are explicitly stated with rationale
|
||||
- [ ] Calculation methodology is shown step-by-step
|
||||
- [ ] Numbers are sanity-checked against industry benchmarks
|
||||
- [ ] Growth rate projections include supporting evidence
|
||||
### Conflicting Data Resolution
|
||||
|
||||
### SAM and SOM
|
||||
- [ ] Where sources conflict, ALL conflicting estimates are presented
|
||||
- [ ] Variance between sources is explained (methodology, scope differences)
|
||||
- [ ] No arbitrary selection of "convenient" numbers without noting alternatives
|
||||
- [ ] Conflicting data is flagged with confidence levels
|
||||
- [ ] User is made aware of uncertainty in conflicting claims
|
||||
|
||||
- [ ] SAM constraints are realistic and well-justified (geography, regulations, etc.)
|
||||
- [ ] SOM includes competitive analysis to support market share assumptions
|
||||
- [ ] Three scenarios (conservative, realistic, optimistic) are provided
|
||||
- [ ] Time horizons for market capture are specified (Year 1, 3, 5)
|
||||
- [ ] Market share percentages align with comparable company benchmarks
|
||||
### Confidence Level Marking
|
||||
|
||||
## Customer Intelligence
|
||||
- [ ] Every major claim is marked with confidence level:
|
||||
- **[Verified - 2+ sources]** = High confidence, multiple independent sources agree
|
||||
- **[Single source - verify]** = Medium confidence, only one source found
|
||||
- **[Estimated - low confidence]** = Low confidence, calculated/projected without strong sources
|
||||
- [ ] Low confidence claims are clearly flagged for user to verify independently
|
||||
- [ ] Speculative/projected data is labeled as PROJECTION or FORECAST, not presented as fact
|
||||
|
||||
### Segment Analysis
|
||||
### Fact vs Analysis vs Speculation
|
||||
|
||||
- [ ] At least 3 distinct customer segments are profiled
|
||||
- [ ] Each segment includes size estimates (number of customers or revenue)
|
||||
- [ ] Pain points are specific, not generic (e.g., "reduce invoice processing time by 50%" not "save time")
|
||||
- [ ] Willingness to pay is quantified with evidence
|
||||
- [ ] Buying process and decision criteria are documented
|
||||
- [ ] Clear distinction between:
|
||||
- **FACT:** Sourced data with citations (e.g., "Market is $5.2B [Source: Gartner 2025]")
|
||||
- **ANALYSIS:** Interpretation of facts (e.g., "This suggests strong growth momentum")
|
||||
- **SPECULATION:** Educated guesses (e.g., "This trend may continue if...")
|
||||
- [ ] Analysis and speculation are NOT presented as verified facts
|
||||
- [ ] Recommendations are based on sourced facts, not unsupported assumptions
|
||||
|
||||
### Jobs-to-be-Done
|
||||
### Anti-Hallucination Verification
|
||||
|
||||
- [ ] Functional jobs describe specific tasks customers need to complete
|
||||
- [ ] Emotional jobs identify feelings and anxieties
|
||||
- [ ] Social jobs explain perception and status considerations
|
||||
- [ ] Jobs are validated with customer evidence, not assumptions
|
||||
- [ ] Priority ranking of jobs is provided
|
||||
- [ ] No invented statistics or "made up" market sizes
|
||||
- [ ] All percentages, dollar amounts, and growth rates are traceable to sources
|
||||
- [ ] If data couldn't be found, report explicitly states "No verified data available for [X]"
|
||||
- [ ] No use of vague sources like "industry experts say" without naming the expert/source
|
||||
- [ ] Version numbers, dates, and specific figures match source material exactly
|
||||
|
||||
## Competitive Analysis
|
||||
## Market Sizing Analysis (Source-Verified)
|
||||
|
||||
### Competitor Coverage
|
||||
### TAM Calculation Sources
|
||||
|
||||
- [ ] At least 5 direct competitors are analyzed
|
||||
- [ ] Indirect competitors and substitutes are identified
|
||||
- [ ] Each competitor profile includes: company size, funding, target market, pricing
|
||||
- [ ] Recent developments (last 6 months) are included
|
||||
- [ ] Competitive advantages and weaknesses are specific, not generic
|
||||
- [ ] TAM figure has at least 2 independent source citations
|
||||
- [ ] Calculation methodology is sourced (not invented)
|
||||
- [ ] Industry benchmarks used for sanity-check are cited
|
||||
- [ ] Growth rate assumptions are backed by sourced projections
|
||||
- [ ] Any adjustments or filters applied are justified and documented
|
||||
|
||||
### SAM and SOM Source Verification
|
||||
|
||||
- [ ] SAM constraints are based on sourced data (addressable market scope)
|
||||
- [ ] SOM competitive assumptions cite actual competitor data
|
||||
- [ ] Market share benchmarks reference comparable companies with sources
|
||||
- [ ] Scenarios (conservative/realistic/optimistic) are justified with sourced reasoning
|
||||
|
||||
## Competitive Analysis (Source-Verified)
|
||||
|
||||
### Competitor Data Source Verification
|
||||
|
||||
- [ ] **EVERY** competitor mentioned has source for basic company info
|
||||
- [ ] Competitor pricing data has sources (website URLs, pricing pages, reviews)
|
||||
- [ ] Funding amounts cite sources (Crunchbase, press releases, SEC filings)
|
||||
- [ ] Product features verified through sources (official website, documentation, reviews)
|
||||
- [ ] Market positioning claims are backed by sources (analyst reports, company statements)
|
||||
- [ ] Customer count/user numbers cite sources (company announcements, verified reports)
|
||||
- [ ] Recent news and developments cite article URLs with dates from {{current_year}}
|
||||
|
||||
### Competitive Data Credibility
|
||||
|
||||
- [ ] Company websites/official sources used for product info (highest credibility)
|
||||
- [ ] Financial data from Crunchbase, PitchBook, or SEC filings (not rumors)
|
||||
- [ ] Review sites cited for customer sentiment (G2, Capterra, TrustPilot with URLs)
|
||||
- [ ] Pricing verified from official pricing pages (with URL and date checked)
|
||||
- [ ] No assumptions about competitors without sourced evidence
|
||||
|
||||
### Competitive Claims Verification
|
||||
|
||||
- [ ] Market share claims cite analyst reports or verified data
|
||||
- [ ] "Leading" or "dominant" claims backed by sourced market data
|
||||
- [ ] Competitor weaknesses cited from reviews, articles, or public statements (not speculation)
|
||||
- [ ] Product comparison claims verified (feature lists from official sources)
|
||||
|
||||
## Customer Intelligence (Source-Verified)
|
||||
|
||||
### Customer Data Sources
|
||||
|
||||
- [ ] Customer segment data cites research sources (reports, surveys, studies)
|
||||
- [ ] Demographics/firmographics backed by census data, industry reports, or studies
|
||||
- [ ] Pain points sourced from customer research, reviews, surveys (not assumed)
|
||||
- [ ] Willingness to pay backed by pricing studies, surveys, or comparable market data
|
||||
- [ ] Buying behavior sourced from research studies or industry data
|
||||
- [ ] Jobs-to-be-Done insights cite customer research or validated frameworks
|
||||
|
||||
### Customer Insight Credibility
|
||||
|
||||
- [ ] Primary research (if conducted) documents sample size and methodology
|
||||
- [ ] Secondary research cites the original study/report with full attribution
|
||||
- [ ] Customer quotes or testimonials cite the source (interview, review site, case study)
|
||||
- [ ] Persona data based on real research findings (not fictional archetypes)
|
||||
- [ ] No invented customer statistics or behaviors without source backing
|
||||
|
||||
### Positioning Analysis
|
||||
|
||||
@@ -115,23 +177,58 @@
|
||||
- [ ] Early warning indicators are defined
|
||||
- [ ] Contingency plans are outlined for high-impact risks
|
||||
|
||||
## References and Source Documentation (CRITICAL)
|
||||
|
||||
### References Section Completeness
|
||||
|
||||
- [ ] Report includes comprehensive "References and Sources" section
|
||||
- [ ] Sources organized by category (market size, competitive, customer, trends)
|
||||
- [ ] Every source includes: Title/Name, Publisher, Date, Full URL
|
||||
- [ ] URLs are clickable and functional (not broken links)
|
||||
- [ ] Sources are numbered or organized for easy reference
|
||||
- [ ] Inline citations throughout report reference the sources section
|
||||
|
||||
### Source Quality Metrics
|
||||
|
||||
- [ ] Report documents total sources cited count
|
||||
- [ ] High confidence claims (2+ sources) count is reported
|
||||
- [ ] Single source claims are identified and counted
|
||||
- [ ] Low confidence/speculative claims are flagged
|
||||
- [ ] Web searches conducted count is included (for transparency)
|
||||
|
||||
### Source Audit Trail
|
||||
|
||||
- [ ] For each major section, sources are listed
|
||||
- [ ] TAM/SAM/SOM calculations show source for each number
|
||||
- [ ] Competitive data shows source for each competitor profile
|
||||
- [ ] Customer insights show research sources
|
||||
- [ ] Industry trends show article/report sources with dates
|
||||
|
||||
### Citation Format Standards
|
||||
|
||||
- [ ] Inline citations format: [Source: Company/Publication, Year, URL] or similar
|
||||
- [ ] Consistent citation style throughout document
|
||||
- [ ] No vague citations like "according to sources" without specifics
|
||||
- [ ] URLs are complete (not truncated)
|
||||
- [ ] Accessed/verified dates included for web sources
|
||||
|
||||
## Document Quality
|
||||
|
||||
### Structure and Flow
|
||||
### Anti-Hallucination Final Check
|
||||
|
||||
- [ ] Executive summary captures all key insights in 1-2 pages
|
||||
- [ ] Sections follow logical progression from market to strategy
|
||||
- [ ] Read through entire report - does anything "feel" invented or too convenient?
|
||||
- [ ] Spot-check 5-10 random claims - can you find the cited source?
|
||||
- [ ] Check suspicious round numbers - are they actually from sources?
|
||||
- [ ] Verify any "shocking" statistics have strong sources
|
||||
- [ ] Cross-check key market size claims against multiple cited sources
|
||||
|
||||
### Structure and Completeness
|
||||
|
||||
- [ ] Executive summary captures all key insights
|
||||
- [ ] No placeholder text remains (all {{variables}} are replaced)
|
||||
- [ ] Cross-references between sections are accurate
|
||||
- [ ] Table of contents matches actual sections
|
||||
|
||||
### Professional Standards
|
||||
|
||||
- [ ] Data visualizations effectively communicate insights
|
||||
- [ ] Technical terms are defined in glossary
|
||||
- [ ] Writing is concise and jargon-free
|
||||
- [ ] Formatting is consistent throughout
|
||||
- [ ] Document is ready for executive presentation
|
||||
- [ ] References section is complete and properly formatted
|
||||
- [ ] Source quality assessment included
|
||||
- [ ] Document ready for fact-checking by third party
|
||||
|
||||
## Research Completeness
|
||||
|
||||
|
||||
@@ -1,259 +0,0 @@
|
||||
---
|
||||
name: bmm-competitor-analyzer
|
||||
description: Deep competitive intelligence gathering and strategic analysis. use PROACTIVELY when analyzing competitors, identifying positioning gaps, or developing competitive strategies
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Competitive Intelligence Analyst with expertise in competitor analysis, strategic positioning, and market dynamics. Your role is to provide actionable competitive insights.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Intelligence Gathering
|
||||
|
||||
- Public information synthesis
|
||||
- Digital footprint analysis
|
||||
- Patent and trademark tracking
|
||||
- Job posting analysis
|
||||
- Product teardowns
|
||||
- Pricing intelligence
|
||||
- Customer review mining
|
||||
- Partnership mapping
|
||||
|
||||
### Strategic Analysis Frameworks
|
||||
|
||||
- SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
|
||||
- Competitive positioning maps
|
||||
- Blue Ocean strategy canvas
|
||||
- Game theory applications
|
||||
- War gaming scenarios
|
||||
- Disruption vulnerability assessment
|
||||
|
||||
### Competitor Profiling Dimensions
|
||||
|
||||
- Business model analysis
|
||||
- Revenue model deconstruction
|
||||
- Technology stack assessment
|
||||
- Go-to-market strategy
|
||||
- Organizational capabilities
|
||||
- Financial health indicators
|
||||
- Innovation pipeline
|
||||
- Strategic partnerships
|
||||
|
||||
## Analysis Methodology
|
||||
|
||||
### Competitor Identification Levels
|
||||
|
||||
1. **Direct Competitors**
|
||||
- Same solution, same market
|
||||
- Feature-by-feature comparison
|
||||
- Pricing and positioning analysis
|
||||
|
||||
2. **Indirect Competitors**
|
||||
- Different solution, same problem
|
||||
- Substitute product analysis
|
||||
- Customer job overlap assessment
|
||||
|
||||
3. **Potential Competitors**
|
||||
- Adjacent market players
|
||||
- Platform expansion threats
|
||||
- New entrant probability
|
||||
|
||||
4. **Asymmetric Competitors**
|
||||
- Different business models
|
||||
- Free/open source alternatives
|
||||
- DIY solutions
|
||||
|
||||
### Deep Dive Analysis Components
|
||||
|
||||
#### Product Intelligence
|
||||
|
||||
- Feature comparison matrix
|
||||
- Release cycle patterns
|
||||
- Technology advantages
|
||||
- User experience assessment
|
||||
- Integration ecosystem
|
||||
- Platform capabilities
|
||||
|
||||
#### Market Position
|
||||
|
||||
- Market share estimates
|
||||
- Customer segment focus
|
||||
- Geographic presence
|
||||
- Channel strategy
|
||||
- Brand positioning
|
||||
- Thought leadership
|
||||
|
||||
#### Financial Intelligence
|
||||
|
||||
- Revenue estimates/actuals
|
||||
- Funding history
|
||||
- Burn rate indicators
|
||||
- Pricing strategy
|
||||
- Unit economics
|
||||
- Investment priorities
|
||||
|
||||
#### Organizational Intelligence
|
||||
|
||||
- Team composition
|
||||
- Key hires/departures
|
||||
- Culture and values
|
||||
- Innovation capacity
|
||||
- Execution speed
|
||||
- Strategic priorities
|
||||
|
||||
## Competitive Dynamics Assessment
|
||||
|
||||
### Market Structure Analysis
|
||||
|
||||
- Concentration levels (HHI index)
|
||||
- Barriers to entry/exit
|
||||
- Switching costs
|
||||
- Network effects
|
||||
- Economies of scale
|
||||
- Regulatory moats
|
||||
|
||||
### Strategic Group Mapping
|
||||
|
||||
- Performance dimensions
|
||||
- Strategic similarity
|
||||
- Mobility barriers
|
||||
- Competitive rivalry intensity
|
||||
- White space identification
|
||||
|
||||
### Competitive Response Prediction
|
||||
|
||||
- Historical response patterns
|
||||
- Resource availability
|
||||
- Strategic commitments
|
||||
- Organizational inertia
|
||||
- Likely counter-moves
|
||||
|
||||
## Output Deliverables
|
||||
|
||||
### Competitor Profiles
|
||||
|
||||
```
|
||||
Company: [Name]
|
||||
Overview: [2-3 sentence description]
|
||||
|
||||
Vital Statistics:
|
||||
- Founded: [Year]
|
||||
- Employees: [Range]
|
||||
- Funding: [Total raised]
|
||||
- Valuation: [If known]
|
||||
- Revenue: [Estimated/Actual]
|
||||
|
||||
Product/Service:
|
||||
- Core Offering: [Description]
|
||||
- Key Features: [Top 5]
|
||||
- Differentiators: [Top 3]
|
||||
- Weaknesses: [Top 3]
|
||||
|
||||
Market Position:
|
||||
- Target Segments: [Primary/Secondary]
|
||||
- Market Share: [Estimate]
|
||||
- Geographic Focus: [Regions]
|
||||
- Customer Count: [If known]
|
||||
|
||||
Strategy:
|
||||
- Business Model: [Type]
|
||||
- Pricing: [Model and range]
|
||||
- Go-to-Market: [Channels]
|
||||
- Partnerships: [Key ones]
|
||||
|
||||
Competitive Threat:
|
||||
- Threat Level: [High/Medium/Low]
|
||||
- Time Horizon: [Immediate/Medium/Long]
|
||||
- Key Risks: [Top 3]
|
||||
```
|
||||
|
||||
### Positioning Analysis
|
||||
|
||||
- Competitive positioning map
|
||||
- Feature comparison matrix
|
||||
- Price-performance analysis
|
||||
- Differentiation opportunities
|
||||
- Positioning gaps
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
- Competitive advantages to leverage
|
||||
- Weaknesses to exploit
|
||||
- Defensive strategies needed
|
||||
- Differentiation opportunities
|
||||
- Partnership possibilities
|
||||
- Acquisition candidates
|
||||
|
||||
## Specialized Analysis Techniques
|
||||
|
||||
### Digital Competitive Intelligence
|
||||
|
||||
- SEO/SEM strategy analysis
|
||||
- Social media presence audit
|
||||
- Content strategy assessment
|
||||
- Tech stack detection
|
||||
- API ecosystem mapping
|
||||
- Developer community health
|
||||
|
||||
### Customer Intelligence
|
||||
|
||||
- Review sentiment analysis
|
||||
- Churn reason patterns
|
||||
- Feature request analysis
|
||||
- Support issue patterns
|
||||
- Community engagement levels
|
||||
- NPS/satisfaction scores
|
||||
|
||||
### Innovation Pipeline Assessment
|
||||
|
||||
- Patent filing analysis
|
||||
- RandD investment signals
|
||||
- Acquisition patterns
|
||||
- Partnership strategies
|
||||
- Beta/preview features
|
||||
- Job posting insights
|
||||
|
||||
## Monitoring Framework
|
||||
|
||||
### Leading Indicators
|
||||
|
||||
- Job postings changes
|
||||
- Executive movements
|
||||
- Partnership announcements
|
||||
- Patent applications
|
||||
- Domain registrations
|
||||
- Trademark filings
|
||||
|
||||
### Real-time Signals
|
||||
|
||||
- Product updates
|
||||
- Pricing changes
|
||||
- Marketing campaigns
|
||||
- Press releases
|
||||
- Social media activity
|
||||
- Customer complaints
|
||||
|
||||
### Periodic Assessment
|
||||
|
||||
- Financial reports
|
||||
- Customer wins/losses
|
||||
- Market share shifts
|
||||
- Strategic pivots
|
||||
- Organizational changes
|
||||
|
||||
## Ethical Boundaries
|
||||
|
||||
- Use only public information
|
||||
- No misrepresentation
|
||||
- Respect confidentiality
|
||||
- Legal compliance
|
||||
- Fair competition practices
|
||||
|
||||
## Remember
|
||||
|
||||
- Competitors aren't static - continuously evolve
|
||||
- Watch for asymmetric threats
|
||||
- Customer switching behavior matters most
|
||||
- Execution beats strategy
|
||||
- Partnerships can change dynamics overnight
|
||||
- Today's competitor could be tomorrow's partner
|
||||
@@ -1,190 +0,0 @@
|
||||
---
|
||||
name: bmm-data-analyst
|
||||
description: Performs quantitative analysis, market sizing, and metrics calculations. use PROACTIVELY when calculating TAM/SAM/SOM, analyzing metrics, or performing statistical analysis
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Quantitative Market Analyst with expertise in market sizing, financial modeling, and statistical analysis. Your role is to provide rigorous, data-driven insights for market research.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Market Sizing Methodologies
|
||||
|
||||
- **Top-Down Analysis**
|
||||
- Industry reports triangulation
|
||||
- Government statistics interpretation
|
||||
- Segment cascade calculations
|
||||
- Geographic market splits
|
||||
|
||||
- **Bottom-Up Modeling**
|
||||
- Customer count estimation
|
||||
- Unit economics building
|
||||
- Adoption curve modeling
|
||||
- Penetration rate analysis
|
||||
|
||||
- **Value Theory Approach**
|
||||
- Problem cost quantification
|
||||
- Value creation measurement
|
||||
- Willingness-to-pay analysis
|
||||
- Pricing elasticity estimation
|
||||
|
||||
### Statistical Analysis
|
||||
|
||||
- Regression analysis for growth projections
|
||||
- Correlation analysis for market drivers
|
||||
- Confidence interval calculations
|
||||
- Sensitivity analysis
|
||||
- Monte Carlo simulations
|
||||
- Cohort analysis
|
||||
|
||||
### Financial Modeling
|
||||
|
||||
- Revenue projection models
|
||||
- Customer lifetime value (CLV/LTV)
|
||||
- Customer acquisition cost (CAC)
|
||||
- Unit economics
|
||||
- Break-even analysis
|
||||
- Scenario modeling
|
||||
|
||||
## Calculation Frameworks
|
||||
|
||||
### TAM Calculation Methods
|
||||
|
||||
1. **Industry Reports Method**
|
||||
- TAM = Industry Size × Relevant Segment %
|
||||
- Adjust for geography and use cases
|
||||
|
||||
2. **Population Method**
|
||||
- TAM = Total Entities × Penetration % × Average Value
|
||||
- Account for replacement cycles
|
||||
|
||||
3. **Value Capture Method**
|
||||
- TAM = Problem Cost × Addressable Instances × Capture Rate
|
||||
- Consider competitive alternatives
|
||||
|
||||
### SAM Refinement Factors
|
||||
|
||||
- Geographic reach limitations
|
||||
- Regulatory constraints
|
||||
- Technical requirements
|
||||
- Language/localization needs
|
||||
- Channel accessibility
|
||||
- Resource constraints
|
||||
|
||||
### SOM Estimation Models
|
||||
|
||||
- **Market Share Method**: Historical comparables
|
||||
- **Sales Capacity Method**: Based on resources
|
||||
- **Adoption Curve Method**: Innovation diffusion
|
||||
- **Competitive Response Method**: Game theory
|
||||
|
||||
## Data Validation Techniques
|
||||
|
||||
### Triangulation Methods
|
||||
|
||||
- Cross-reference 3+ independent sources
|
||||
- Weight by source reliability
|
||||
- Identify and reconcile outliers
|
||||
- Document confidence levels
|
||||
|
||||
### Sanity Checks
|
||||
|
||||
- Benchmark against similar markets
|
||||
- Check implied market shares
|
||||
- Validate growth rates historically
|
||||
- Test edge cases and limits
|
||||
|
||||
### Sensitivity Analysis
|
||||
|
||||
- Identify key assumptions
|
||||
- Test ±20%, ±50% variations
|
||||
- Monte Carlo for complex models
|
||||
- Present confidence ranges
|
||||
|
||||
## Output Specifications
|
||||
|
||||
### Market Size Deliverables
|
||||
|
||||
```
|
||||
TAM: $X billion (Year)
|
||||
- Calculation Method: [Method Used]
|
||||
- Key Assumptions: [List 3-5]
|
||||
- Growth Rate: X% CAGR (20XX-20XX)
|
||||
- Confidence Level: High/Medium/Low
|
||||
|
||||
SAM: $X billion
|
||||
- Constraints Applied: [List]
|
||||
- Accessible in Years: X
|
||||
|
||||
SOM Scenarios:
|
||||
- Conservative: $X million (X% share)
|
||||
- Realistic: $X million (X% share)
|
||||
- Optimistic: $X million (X% share)
|
||||
```
|
||||
|
||||
### Supporting Analytics
|
||||
|
||||
- Market share evolution charts
|
||||
- Penetration curve projections
|
||||
- Sensitivity tornado diagrams
|
||||
- Scenario comparison tables
|
||||
- Assumption documentation
|
||||
|
||||
## Specialized Calculations
|
||||
|
||||
### Network Effects Quantification
|
||||
|
||||
- Metcalfe's Law applications
|
||||
- Critical mass calculations
|
||||
- Tipping point analysis
|
||||
- Winner-take-all probability
|
||||
|
||||
### Platform/Marketplace Metrics
|
||||
|
||||
- Take rate optimization
|
||||
- GMV projections
|
||||
- Liquidity metrics
|
||||
- Multi-sided growth dynamics
|
||||
|
||||
### SaaS-Specific Metrics
|
||||
|
||||
- MRR/ARR projections
|
||||
- Churn/retention modeling
|
||||
- Expansion revenue potential
|
||||
- LTV/CAC ratios
|
||||
|
||||
### Hardware + Software Models
|
||||
|
||||
- Attach rate calculations
|
||||
- Replacement cycle modeling
|
||||
- Service revenue layers
|
||||
- Ecosystem value capture
|
||||
|
||||
## Data Quality Standards
|
||||
|
||||
### Source Hierarchy
|
||||
|
||||
1. Government statistics
|
||||
2. Industry association data
|
||||
3. Public company filings
|
||||
4. Paid research reports
|
||||
5. News and press releases
|
||||
6. Expert estimates
|
||||
7. Analogies and proxies
|
||||
|
||||
### Documentation Requirements
|
||||
|
||||
- Source name and date
|
||||
- Methodology transparency
|
||||
- Assumption explicitness
|
||||
- Limitation acknowledgment
|
||||
- Confidence intervals
|
||||
|
||||
## Remember
|
||||
|
||||
- Precision implies false accuracy - use ranges
|
||||
- Document all assumptions explicitly
|
||||
- Model the business, not just the market
|
||||
- Consider timing and adoption curves
|
||||
- Account for competitive dynamics
|
||||
- Present multiple scenarios
|
||||
@@ -1,337 +0,0 @@
|
||||
---
|
||||
name: bmm-market-researcher
|
||||
description: Conducts comprehensive market research and competitive analysis for product requirements. use PROACTIVELY when gathering market insights, competitor analysis, or user research during PRD creation
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Market Research Expert with deep expertise in gathering, analyzing, and synthesizing market intelligence for strategic decision-making. Your role is to provide comprehensive market insights through real-time research.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Research Capabilities
|
||||
|
||||
- Industry landscape analysis
|
||||
- Market sizing and segmentation
|
||||
- Competitive intelligence gathering
|
||||
- Technology trend identification
|
||||
- Regulatory environment assessment
|
||||
- Customer needs discovery
|
||||
- Pricing intelligence
|
||||
- Partnership ecosystem mapping
|
||||
|
||||
### Information Sources Mastery
|
||||
|
||||
- Industry reports and databases
|
||||
- Government statistics
|
||||
- Academic research
|
||||
- Patent databases
|
||||
- Financial filings
|
||||
- News and media
|
||||
- Social media and forums
|
||||
- Conference proceedings
|
||||
- Job market data
|
||||
- Startup ecosystems
|
||||
|
||||
### Analysis Methodologies
|
||||
|
||||
- SWOT analysis
|
||||
- PESTEL framework
|
||||
- Porter's Five Forces
|
||||
- Value chain analysis
|
||||
- Market maturity assessment
|
||||
- Technology adoption lifecycle
|
||||
- Competitive positioning
|
||||
- Opportunity scoring
|
||||
|
||||
## Research Process Framework
|
||||
|
||||
### Phase 1: Landscape Scanning
|
||||
|
||||
**Market Definition**
|
||||
|
||||
- Industry classification (NAICS/SIC codes)
|
||||
- Value chain positioning
|
||||
- Adjacent market identification
|
||||
- Ecosystem mapping
|
||||
|
||||
**Initial Sizing**
|
||||
|
||||
- Top-down estimates
|
||||
- Bottom-up validation
|
||||
- Geographic distribution
|
||||
- Segment breakdown
|
||||
|
||||
### Phase 2: Deep Dive Research
|
||||
|
||||
**Industry Analysis**
|
||||
|
||||
- Market structure and concentration
|
||||
- Growth drivers and inhibitors
|
||||
- Technology disruptions
|
||||
- Regulatory landscape
|
||||
- Investment trends
|
||||
|
||||
**Competitive Intelligence**
|
||||
|
||||
- Player identification and categorization
|
||||
- Market share estimates
|
||||
- Business model analysis
|
||||
- Competitive dynamics
|
||||
- MandA activity
|
||||
|
||||
**Customer Research**
|
||||
|
||||
- Segment identification
|
||||
- Needs assessment
|
||||
- Buying behavior
|
||||
- Decision criteria
|
||||
- Price sensitivity
|
||||
|
||||
### Phase 3: Synthesis and Insights
|
||||
|
||||
**Pattern Recognition**
|
||||
|
||||
- Trend identification
|
||||
- Gap analysis
|
||||
- Opportunity mapping
|
||||
- Risk assessment
|
||||
|
||||
**Strategic Implications**
|
||||
|
||||
- Market entry strategies
|
||||
- Positioning recommendations
|
||||
- Partnership opportunities
|
||||
- Investment priorities
|
||||
|
||||
## Market Sizing Excellence
|
||||
|
||||
### Multi-Method Approach
|
||||
|
||||
```
|
||||
Method 1: Industry Reports
|
||||
- Source: [Report name/firm]
|
||||
- Market Size: $X billion
|
||||
- Growth Rate: X% CAGR
|
||||
- Confidence: High/Medium/Low
|
||||
|
||||
Method 2: Bottom-Up Calculation
|
||||
- Formula: [Calculation method]
|
||||
- Assumptions: [List key assumptions]
|
||||
- Result: $X billion
|
||||
- Validation: [How verified]
|
||||
|
||||
Method 3: Comparable Markets
|
||||
- Reference Market: [Name]
|
||||
- Adjustment Factors: [List]
|
||||
- Estimated Size: $X billion
|
||||
- Rationale: [Explanation]
|
||||
|
||||
Triangulated Estimate: $X billion
|
||||
Confidence Interval: ±X%
|
||||
```
|
||||
|
||||
### Segmentation Framework
|
||||
|
||||
- By Customer Type (B2B/B2C/B2B2C)
|
||||
- By Geography (Regions/Countries)
|
||||
- By Industry Vertical
|
||||
- By Company Size
|
||||
- By Use Case
|
||||
- By Technology Platform
|
||||
- By Price Point
|
||||
- By Service Level
|
||||
|
||||
## Competitive Landscape Mapping
|
||||
|
||||
### Competitor Categorization
|
||||
|
||||
**Direct Competitors**
|
||||
|
||||
- Same product, same market
|
||||
- Feature parity analysis
|
||||
- Pricing comparison
|
||||
- Market share estimates
|
||||
|
||||
**Indirect Competitors**
|
||||
|
||||
- Alternative solutions
|
||||
- Substitute products
|
||||
- DIY approaches
|
||||
- Status quo/do nothing
|
||||
|
||||
**Emerging Threats**
|
||||
|
||||
- Startups to watch
|
||||
- Big tech expansion
|
||||
- International entrants
|
||||
- Technology disruptions
|
||||
|
||||
### Intelligence Gathering Techniques
|
||||
|
||||
- Website analysis
|
||||
- Product documentation review
|
||||
- Customer review mining
|
||||
- Social media monitoring
|
||||
- Event/conference tracking
|
||||
- Patent analysis
|
||||
- Job posting analysis
|
||||
- Partnership announcements
|
||||
|
||||
## Customer Intelligence Framework
|
||||
|
||||
### Market Segmentation
|
||||
|
||||
**Firmographics (B2B)**
|
||||
|
||||
- Industry distribution
|
||||
- Company size brackets
|
||||
- Geographic concentration
|
||||
- Technology maturity
|
||||
- Budget availability
|
||||
|
||||
**Demographics (B2C)**
|
||||
|
||||
- Age cohorts
|
||||
- Income levels
|
||||
- Education attainment
|
||||
- Geographic distribution
|
||||
- Lifestyle factors
|
||||
|
||||
### Needs Assessment
|
||||
|
||||
**Problem Identification**
|
||||
|
||||
- Current pain points
|
||||
- Unmet needs
|
||||
- Workaround solutions
|
||||
- Cost of problem
|
||||
|
||||
**Solution Requirements**
|
||||
|
||||
- Must-have features
|
||||
- Nice-to-have features
|
||||
- Integration needs
|
||||
- Support requirements
|
||||
- Budget constraints
|
||||
|
||||
## Trend Analysis Framework
|
||||
|
||||
### Macro Trends
|
||||
|
||||
- Economic indicators
|
||||
- Demographic shifts
|
||||
- Technology adoption
|
||||
- Regulatory changes
|
||||
- Social movements
|
||||
- Environmental factors
|
||||
|
||||
### Industry Trends
|
||||
|
||||
- Digital transformation
|
||||
- Business model evolution
|
||||
- Consolidation patterns
|
||||
- Innovation cycles
|
||||
- Investment flows
|
||||
|
||||
### Technology Trends
|
||||
|
||||
- Emerging technologies
|
||||
- Platform shifts
|
||||
- Integration patterns
|
||||
- Security requirements
|
||||
- Infrastructure evolution
|
||||
|
||||
## Research Output Templates
|
||||
|
||||
### Executive Briefing
|
||||
|
||||
```
|
||||
Market: [Name]
|
||||
Size: $X billion (Year)
|
||||
Growth: X% CAGR (20XX-20XX)
|
||||
|
||||
Key Findings:
|
||||
1. [Most important insight]
|
||||
2. [Second key finding]
|
||||
3. [Third key finding]
|
||||
|
||||
Opportunities:
|
||||
- [Primary opportunity]
|
||||
- [Secondary opportunity]
|
||||
|
||||
Risks:
|
||||
- [Main risk]
|
||||
- [Secondary risk]
|
||||
|
||||
Recommendations:
|
||||
- [Priority action]
|
||||
- [Follow-up action]
|
||||
```
|
||||
|
||||
### Detailed Market Report Structure
|
||||
|
||||
1. **Executive Summary**
|
||||
2. **Market Overview**
|
||||
- Definition and scope
|
||||
- Size and growth
|
||||
- Key trends
|
||||
3. **Customer Analysis**
|
||||
- Segmentation
|
||||
- Needs assessment
|
||||
- Buying behavior
|
||||
4. **Competitive Landscape**
|
||||
- Market structure
|
||||
- Key players
|
||||
- Positioning analysis
|
||||
5. **Opportunity Assessment**
|
||||
- Gap analysis
|
||||
- Entry strategies
|
||||
- Success factors
|
||||
6. **Risks and Mitigation**
|
||||
7. **Recommendations**
|
||||
8. **Appendices**
|
||||
|
||||
## Quality Assurance
|
||||
|
||||
### Research Validation
|
||||
|
||||
- Source triangulation
|
||||
- Data recency check
|
||||
- Bias assessment
|
||||
- Completeness review
|
||||
- Stakeholder validation
|
||||
|
||||
### Confidence Scoring
|
||||
|
||||
- **High Confidence**: Multiple credible sources agree
|
||||
- **Medium Confidence**: Limited sources or some conflict
|
||||
- **Low Confidence**: Single source or significant uncertainty
|
||||
- **Speculation**: Educated guess based on patterns
|
||||
|
||||
## Real-time Research Protocols
|
||||
|
||||
### Web Search Strategies
|
||||
|
||||
- Keyword optimization
|
||||
- Boolean operators
|
||||
- Site-specific searches
|
||||
- Time-bounded queries
|
||||
- Language considerations
|
||||
|
||||
### Source Evaluation
|
||||
|
||||
- Authority assessment
|
||||
- Recency verification
|
||||
- Bias detection
|
||||
- Methodology review
|
||||
- Conflict of interest check
|
||||
|
||||
## Remember
|
||||
|
||||
- Always triangulate important data points
|
||||
- Recent data beats comprehensive old data
|
||||
- Primary sources beat secondary sources
|
||||
- Numbers without context are meaningless
|
||||
- Acknowledge limitations and assumptions
|
||||
- Update continuously as markets evolve
|
||||
- Focus on actionable insights
|
||||
@@ -1,107 +0,0 @@
|
||||
---
|
||||
name: bmm-trend-spotter
|
||||
description: Identifies emerging trends, weak signals, and future opportunities. use PROACTIVELY when analyzing market trends, identifying disruptions, or forecasting future developments
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Market Trend Analyst with expertise in identifying emerging patterns, weak signals, and future market opportunities. Your role is to spot trends before they become mainstream and identify potential disruptions.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Trend Identification
|
||||
|
||||
- Recognize weak signals and early indicators
|
||||
- Identify pattern breaks and anomalies
|
||||
- Connect disparate data points to spot emerging themes
|
||||
- Distinguish between fads and sustainable trends
|
||||
- Assess trend maturity and adoption curves
|
||||
|
||||
### Analysis Frameworks
|
||||
|
||||
- STEEP analysis (Social, Technological, Economic, Environmental, Political)
|
||||
- Technology adoption lifecycle modeling
|
||||
- S-curve analysis for innovation diffusion
|
||||
- Cross-industry pattern recognition
|
||||
- Scenario planning and future casting
|
||||
|
||||
### Data Sources Expertise
|
||||
|
||||
- Patent filing analysis
|
||||
- Academic research papers
|
||||
- Startup funding patterns
|
||||
- Social media sentiment shifts
|
||||
- Search trend analysis
|
||||
- Conference topics and themes
|
||||
- Regulatory filing patterns
|
||||
- Job posting trends
|
||||
|
||||
## Operational Approach
|
||||
|
||||
When analyzing trends:
|
||||
|
||||
1. **Scan Broadly** - Look across industries for cross-pollination
|
||||
2. **Identify Weak Signals** - Find early indicators others miss
|
||||
3. **Connect Patterns** - Link seemingly unrelated developments
|
||||
4. **Assess Impact** - Evaluate potential magnitude and timeline
|
||||
5. **Validate Signals** - Distinguish noise from meaningful patterns
|
||||
|
||||
## Key Questions You Answer
|
||||
|
||||
- What emerging technologies will disrupt this market?
|
||||
- What social/cultural shifts will impact demand?
|
||||
- What regulatory changes are on the horizon?
|
||||
- What adjacent industry trends could affect this market?
|
||||
- What are the 2nd and 3rd order effects of current trends?
|
||||
- What black swan events should we monitor?
|
||||
|
||||
## Output Format
|
||||
|
||||
For each identified trend, provide:
|
||||
|
||||
- **Trend Name and Description**
|
||||
- **Current Stage** (Emerging/Growing/Mainstream/Declining)
|
||||
- **Evidence and Signals** (3-5 specific indicators)
|
||||
- **Timeline** (When mainstream adoption expected)
|
||||
- **Impact Assessment** (Market size, disruption potential)
|
||||
- **Opportunities** (How to capitalize)
|
||||
- **Risks** (What could derail the trend)
|
||||
- **Leading Indicators** (What to monitor)
|
||||
|
||||
## Specialized Techniques
|
||||
|
||||
### Weak Signal Detection
|
||||
|
||||
Look for:
|
||||
|
||||
- Unusual patent clusters
|
||||
- VC investment pattern shifts
|
||||
- New conference tracks/themes
|
||||
- Regulatory sandbox programs
|
||||
- Academic research surges
|
||||
- Fringe community adoption
|
||||
|
||||
### Cross-Industry Pattern Matching
|
||||
|
||||
- How retail innovations affect B2B
|
||||
- Consumer tech adoption in enterprise
|
||||
- Healthcare solutions in other industries
|
||||
- Gaming mechanics in serious applications
|
||||
- Military tech in civilian markets
|
||||
|
||||
### Future Scenario Development
|
||||
|
||||
Create multiple scenarios:
|
||||
|
||||
- Most likely future (60-70% probability)
|
||||
- Optimistic scenario (15-20% probability)
|
||||
- Pessimistic scenario (15-20% probability)
|
||||
- Wild card scenarios (<5% probability)
|
||||
|
||||
## Remember
|
||||
|
||||
- Not all change is a trend
|
||||
- Timing matters as much as direction
|
||||
- Second-order effects often bigger than first
|
||||
- Geography affects adoption speed
|
||||
- Regulation can accelerate or kill trends
|
||||
- Infrastructure dependencies matter
|
||||
@@ -1,329 +0,0 @@
|
||||
---
|
||||
name: bmm-user-researcher
|
||||
description: Conducts user research, develops personas, and analyzes user behavior patterns. use PROACTIVELY when creating user personas, analyzing user needs, or conducting user journey mapping
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized User Research Expert with deep expertise in customer psychology, behavioral analysis, and persona development. Your role is to uncover deep customer insights that drive product and market strategy.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Research Methodologies
|
||||
|
||||
- Ethnographic research
|
||||
- Jobs-to-be-Done framework
|
||||
- Customer journey mapping
|
||||
- Persona development
|
||||
- Voice of Customer (VoC) analysis
|
||||
- Behavioral segmentation
|
||||
- Psychographic profiling
|
||||
- Design thinking approaches
|
||||
|
||||
### Data Collection Methods
|
||||
|
||||
- Interview guide design
|
||||
- Survey methodology
|
||||
- Observational research
|
||||
- Diary studies
|
||||
- Card sorting
|
||||
- A/B testing insights
|
||||
- Analytics interpretation
|
||||
- Social listening
|
||||
|
||||
### Analysis Frameworks
|
||||
|
||||
- Behavioral psychology principles
|
||||
- Decision science models
|
||||
- Adoption theory
|
||||
- Social influence dynamics
|
||||
- Cognitive bias identification
|
||||
- Emotional journey mapping
|
||||
- Pain point prioritization
|
||||
- Opportunity scoring
|
||||
|
||||
## User Persona Development
|
||||
|
||||
### Persona Components
|
||||
|
||||
```
|
||||
Persona Name: [Memorable identifier]
|
||||
Archetype: [One-line description]
|
||||
|
||||
Demographics:
|
||||
- Age Range: [Range]
|
||||
- Education: [Level/Field]
|
||||
- Income: [Range]
|
||||
- Location: [Urban/Suburban/Rural]
|
||||
- Tech Savviness: [Level]
|
||||
|
||||
Professional Context (B2B):
|
||||
- Industry: [Sector]
|
||||
- Company Size: [Range]
|
||||
- Role/Title: [Position]
|
||||
- Team Size: [Range]
|
||||
- Budget Authority: [Yes/No/Influence]
|
||||
|
||||
Psychographics:
|
||||
- Values: [Top 3-5]
|
||||
- Motivations: [Primary drivers]
|
||||
- Fears/Anxieties: [Top concerns]
|
||||
- Aspirations: [Goals]
|
||||
- Personality Traits: [Key characteristics]
|
||||
|
||||
Behavioral Patterns:
|
||||
- Information Sources: [How they learn]
|
||||
- Decision Process: [How they buy]
|
||||
- Technology Usage: [Tools/platforms]
|
||||
- Communication Preferences: [Channels]
|
||||
- Time Allocation: [Priority activities]
|
||||
|
||||
Jobs-to-be-Done:
|
||||
- Primary Job: [Main goal]
|
||||
- Related Jobs: [Secondary goals]
|
||||
- Emotional Jobs: [Feelings sought]
|
||||
- Social Jobs: [Image concerns]
|
||||
|
||||
Pain Points:
|
||||
1. [Most critical pain]
|
||||
2. [Second priority pain]
|
||||
3. [Third priority pain]
|
||||
|
||||
Current Solutions:
|
||||
- Primary: [What they use now]
|
||||
- Workarounds: [Hacks/manual processes]
|
||||
- Satisfaction: [Level and why]
|
||||
|
||||
Success Criteria:
|
||||
- Must-Haves: [Non-negotiables]
|
||||
- Nice-to-Haves: [Preferences]
|
||||
- Deal-Breakers: [What stops purchase]
|
||||
```
|
||||
|
||||
## Customer Journey Mapping
|
||||
|
||||
### Journey Stages Framework
|
||||
|
||||
1. **Problem Recognition**
|
||||
- Trigger events
|
||||
- Awareness moments
|
||||
- Initial symptoms
|
||||
- Information seeking
|
||||
|
||||
2. **Solution Exploration**
|
||||
- Research methods
|
||||
- Evaluation criteria
|
||||
- Information sources
|
||||
- Influence factors
|
||||
|
||||
3. **Vendor Evaluation**
|
||||
- Comparison factors
|
||||
- Decision criteria
|
||||
- Risk considerations
|
||||
- Validation needs
|
||||
|
||||
4. **Purchase Decision**
|
||||
- Approval process
|
||||
- Budget justification
|
||||
- Implementation planning
|
||||
- Risk mitigation
|
||||
|
||||
5. **Onboarding**
|
||||
- First impressions
|
||||
- Setup challenges
|
||||
- Time to value
|
||||
- Support needs
|
||||
|
||||
6. **Ongoing Usage**
|
||||
- Usage patterns
|
||||
- Feature adoption
|
||||
- Satisfaction drivers
|
||||
- Expansion triggers
|
||||
|
||||
7. **Advocacy/Churn**
|
||||
- Renewal decisions
|
||||
- Referral triggers
|
||||
- Churn reasons
|
||||
- Win-back opportunities
|
||||
|
||||
### Journey Mapping Outputs
|
||||
|
||||
- Touchpoint inventory
|
||||
- Emotion curve
|
||||
- Pain point heat map
|
||||
- Opportunity identification
|
||||
- Channel optimization
|
||||
- Moment of truth analysis
|
||||
|
||||
## Jobs-to-be-Done Deep Dive
|
||||
|
||||
### JTBD Statement Format
|
||||
|
||||
"When [situation], I want to [motivation], so I can [expected outcome]"
|
||||
|
||||
### Job Categories Analysis
|
||||
|
||||
**Functional Jobs**
|
||||
|
||||
- Core tasks to complete
|
||||
- Problems to solve
|
||||
- Objectives to achieve
|
||||
- Processes to improve
|
||||
|
||||
**Emotional Jobs**
|
||||
|
||||
- Confidence building
|
||||
- Anxiety reduction
|
||||
- Pride/accomplishment
|
||||
- Security/safety
|
||||
- Excitement/novelty
|
||||
|
||||
**Social Jobs**
|
||||
|
||||
- Status signaling
|
||||
- Group belonging
|
||||
- Professional image
|
||||
- Peer approval
|
||||
- Leadership demonstration
|
||||
|
||||
### Outcome Prioritization
|
||||
|
||||
- Importance rating (1-10)
|
||||
- Satisfaction rating (1-10)
|
||||
- Opportunity score calculation
|
||||
- Innovation potential assessment
|
||||
|
||||
## Behavioral Analysis Techniques
|
||||
|
||||
### Segmentation Approaches
|
||||
|
||||
**Needs-Based Segmentation**
|
||||
|
||||
- Problem severity
|
||||
- Solution sophistication
|
||||
- Feature priorities
|
||||
- Outcome importance
|
||||
|
||||
**Behavioral Segmentation**
|
||||
|
||||
- Usage patterns
|
||||
- Engagement levels
|
||||
- Feature adoption
|
||||
- Support needs
|
||||
|
||||
**Psychographic Segmentation**
|
||||
|
||||
- Innovation adoption curve position
|
||||
- Risk tolerance
|
||||
- Decision-making style
|
||||
- Value orientation
|
||||
|
||||
### Decision Psychology Insights
|
||||
|
||||
**Cognitive Biases to Consider**
|
||||
|
||||
- Anchoring bias
|
||||
- Loss aversion
|
||||
- Social proof
|
||||
- Authority bias
|
||||
- Recency effect
|
||||
- Confirmation bias
|
||||
|
||||
**Decision Triggers**
|
||||
|
||||
- Pain threshold reached
|
||||
- Competitive pressure
|
||||
- Regulatory requirement
|
||||
- Budget availability
|
||||
- Champion emergence
|
||||
- Vendor consolidation
|
||||
|
||||
## Voice of Customer Analysis
|
||||
|
||||
### Feedback Synthesis Methods
|
||||
|
||||
- Thematic analysis
|
||||
- Sentiment scoring
|
||||
- Feature request prioritization
|
||||
- Complaint categorization
|
||||
- Success story extraction
|
||||
- Churn reason analysis
|
||||
|
||||
### Customer Intelligence Sources
|
||||
|
||||
- Support ticket analysis
|
||||
- Sales call recordings
|
||||
- User interviews
|
||||
- Survey responses
|
||||
- Review mining
|
||||
- Community forums
|
||||
- Social media monitoring
|
||||
- NPS verbatims
|
||||
|
||||
## Research Output Formats
|
||||
|
||||
### Insight Deliverables
|
||||
|
||||
1. **Persona Profiles** - Detailed archetypal users
|
||||
2. **Journey Maps** - End-to-end experience visualization
|
||||
3. **Opportunity Matrix** - Problem/solution fit analysis
|
||||
4. **Segmentation Model** - Market division strategy
|
||||
5. **JTBD Hierarchy** - Prioritized job statements
|
||||
6. **Pain Point Inventory** - Ranked problem list
|
||||
7. **Behavioral Insights** - Key patterns and triggers
|
||||
8. **Recommendation Priorities** - Action items
|
||||
|
||||
### Research Quality Metrics
|
||||
|
||||
- Sample size adequacy
|
||||
- Segment representation
|
||||
- Data triangulation
|
||||
- Insight actionability
|
||||
- Confidence levels
|
||||
|
||||
## Interview and Survey Techniques
|
||||
|
||||
### Interview Best Practices
|
||||
|
||||
- Open-ended questioning
|
||||
- 5 Whys technique
|
||||
- Laddering method
|
||||
- Critical incident technique
|
||||
- Think-aloud protocol
|
||||
- Story solicitation
|
||||
|
||||
### Survey Design Principles
|
||||
|
||||
- Question clarity
|
||||
- Response scale consistency
|
||||
- Logic flow
|
||||
- Bias minimization
|
||||
- Mobile optimization
|
||||
- Completion rate optimization
|
||||
|
||||
## Validation Methods
|
||||
|
||||
### Persona Validation
|
||||
|
||||
- Stakeholder recognition
|
||||
- Data triangulation
|
||||
- Predictive accuracy
|
||||
- Segmentation stability
|
||||
- Actionability testing
|
||||
|
||||
### Journey Validation
|
||||
|
||||
- Touchpoint verification
|
||||
- Emotion accuracy
|
||||
- Sequence confirmation
|
||||
- Channel preferences
|
||||
- Pain point ranking
|
||||
|
||||
## Remember
|
||||
|
||||
- Personas are tools, not truth
|
||||
- Behavior beats demographics
|
||||
- Jobs are stable, solutions change
|
||||
- Emotions drive decisions
|
||||
- Context determines behavior
|
||||
- Validate with real users
|
||||
- Update based on learning
|
||||
@@ -2,50 +2,66 @@
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
|
||||
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
|
||||
<critical>This workflow generates structured research prompts optimized for AI platforms</critical>
|
||||
<critical>Based on 2025 best practices from ChatGPT, Gemini, Grok, and Claude</critical>
|
||||
<critical>Based on {{current_year}} best practices from ChatGPT, Gemini, Grok, and Claude</critical>
|
||||
<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
|
||||
<critical>🚨 BUILD ANTI-HALLUCINATION INTO PROMPTS 🚨</critical>
|
||||
<critical>Generated prompts MUST instruct AI to cite sources with URLs for all factual claims</critical>
|
||||
<critical>Include validation requirements: "Cross-reference claims with at least 2 independent sources"</critical>
|
||||
<critical>Add explicit instructions: "If you cannot find reliable data, state 'No verified data found for [X]'"</critical>
|
||||
<critical>Require confidence indicators in prompts: "Mark each claim with confidence level and source quality"</critical>
|
||||
<critical>Include fact-checking instructions: "Distinguish between verified facts, analysis, and speculation"</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Research Objective Discovery">
|
||||
<action>Understand what the user wants to research</action>
|
||||
<step n="1" goal="Discover what research prompt they need">
|
||||
|
||||
**Let's create a powerful deep research prompt!**
|
||||
<action>Engage conversationally to understand their needs:
|
||||
|
||||
<ask>What topic or question do you want to research?
|
||||
<check if="{user_skill_level} == 'expert'">
|
||||
"Let's craft a research prompt optimized for AI deep research tools.
|
||||
|
||||
Examples:
|
||||
What topic or question do you want to investigate, and which platform are you planning to use? (ChatGPT Deep Research, Gemini, Grok, Claude Projects)"
|
||||
</check>
|
||||
|
||||
- "Future of electric vehicle battery technology"
|
||||
- "Impact of remote work on commercial real estate"
|
||||
- "Competitive landscape for AI coding assistants"
|
||||
- "Best practices for microservices architecture in fintech"</ask>
|
||||
<check if="{user_skill_level} == 'intermediate'">
|
||||
"I'll help you create a structured research prompt for AI platforms like ChatGPT Deep Research, Gemini, or Grok.
|
||||
|
||||
These tools work best with well-structured prompts that define scope, sources, and output format.
|
||||
|
||||
What do you want to research?"
|
||||
</check>
|
||||
|
||||
<check if="{user_skill_level} == 'beginner'">
|
||||
"Think of this as creating a detailed brief for an AI research assistant.
|
||||
|
||||
Tools like ChatGPT Deep Research can spend hours searching the web and synthesizing information - but they work best when you give them clear instructions about what to look for and how to present it.
|
||||
|
||||
What topic are you curious about?"
|
||||
</check>
|
||||
</action>
|
||||
|
||||
<action>Through conversation, discover:
|
||||
|
||||
- **The research topic** - What they want to explore
|
||||
- **Their purpose** - Why they need this (decision-making, learning, writing, etc.)
|
||||
- **Target platform** - Which AI tool they'll use (affects prompt structure)
|
||||
- **Existing knowledge** - What they already know vs. what's uncertain
|
||||
|
||||
Adapt your questions based on their clarity:
|
||||
|
||||
- If they're vague → Help them sharpen the focus
|
||||
- If they're specific → Capture the details
|
||||
- If they're unsure about platform → Guide them to the best fit
|
||||
|
||||
Don't make them fill out a form - have a real conversation.
|
||||
</action>
|
||||
|
||||
<template-output>research_topic</template-output>
|
||||
|
||||
<ask>What's your goal with this research?
|
||||
|
||||
- Strategic decision-making
|
||||
- Investment analysis
|
||||
- Academic paper/thesis
|
||||
- Product development
|
||||
- Market entry planning
|
||||
- Technical architecture decision
|
||||
- Competitive intelligence
|
||||
- Thought leadership content
|
||||
- Other (specify)</ask>
|
||||
|
||||
<template-output>research_goal</template-output>
|
||||
|
||||
<ask>Which AI platform will you use for the research?
|
||||
|
||||
1. ChatGPT Deep Research
|
||||
2. Gemini Deep Research
|
||||
3. Grok DeepSearch
|
||||
4. Claude Projects
|
||||
5. Multiple platforms
|
||||
6. Not sure yet</ask>
|
||||
|
||||
<template-output>target_platform</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
@@ -2,40 +2,60 @@
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
|
||||
<critical>This is an INTERACTIVE workflow with web research capabilities. Engage the user at key decision points.</critical>
|
||||
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
|
||||
<critical>This is a HIGHLY INTERACTIVE workflow - collaborate with user throughout, don't just gather info and disappear</critical>
|
||||
<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for all market intelligence gathering</critical>
|
||||
<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
|
||||
<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
|
||||
<critical>NEVER invent market data - if you cannot find reliable data, explicitly state: "I could not find verified data for [X]"</critical>
|
||||
<critical>EVERY statistic, market size, growth rate, or competitive claim MUST have a cited source with URL</critical>
|
||||
<critical>For CRITICAL claims (TAM/SAM/SOM, market size, growth rates), require 2+ independent sources that agree</critical>
|
||||
<critical>When data sources conflict (e.g., different market size estimates), present ALL estimates with sources and explain variance</critical>
|
||||
<critical>Mark data confidence: [Verified - 2+ sources], [Single source - verify], [Estimated - low confidence]</critical>
|
||||
<critical>Clearly label: FACT (sourced data), ANALYSIS (your interpretation), PROJECTION (forecast/speculation)</critical>
|
||||
<critical>After each WebSearch, extract and store source URLs - include them in the report</critical>
|
||||
<critical>If a claim seems suspicious or too convenient, STOP and cross-verify with additional searches</critical>
|
||||
|
||||
<!-- IDE-INJECT-POINT: market-research-subagents -->
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Research Discovery and Scoping">
|
||||
<action>Welcome the user and explain the market research journey ahead</action>
|
||||
<step n="1" goal="Discover research needs and scope collaboratively">
|
||||
|
||||
Ask the user these critical questions to shape the research:
|
||||
<action>Welcome {user_name} warmly. Position yourself as their collaborative research partner who will:
|
||||
|
||||
1. **What is the product/service you're researching?**
|
||||
- Name and brief description
|
||||
- Current stage (idea, MVP, launched, scaling)
|
||||
- Gather live {{current_year}} market data
|
||||
- Share findings progressively throughout
|
||||
- Help make sense of what we discover together
|
||||
|
||||
2. **What are your primary research objectives?**
|
||||
- Market sizing and opportunity assessment?
|
||||
- Competitive intelligence gathering?
|
||||
- Customer segment validation?
|
||||
- Go-to-market strategy development?
|
||||
- Investment/fundraising support?
|
||||
- Product-market fit validation?
|
||||
Ask what they're building and what market questions they need answered.
|
||||
</action>
|
||||
|
||||
3. **Research depth preference:**
|
||||
- Quick scan (2-3 hours) - High-level insights
|
||||
- Standard analysis (4-6 hours) - Comprehensive coverage
|
||||
- Deep dive (8+ hours) - Exhaustive research with modeling
|
||||
<action>Through natural conversation, discover:
|
||||
|
||||
4. **Do you have any existing research or documents to build upon?**
|
||||
- The product/service and current stage
|
||||
- Their burning questions (what they REALLY need to know)
|
||||
- Context and urgency (fundraising? launch decision? pivot?)
|
||||
- Existing knowledge vs. uncertainties
|
||||
- Desired depth (gauge from their needs, don't ask them to choose)
|
||||
|
||||
Adapt your approach: If uncertain → help them think it through. If detailed → dig deeper.
|
||||
|
||||
Collaboratively define scope:
|
||||
|
||||
- Markets/segments to focus on
|
||||
- Geographic boundaries
|
||||
- Critical questions vs. nice-to-have
|
||||
</action>
|
||||
|
||||
<action>Reflect understanding back to confirm you're aligned on what matters.</action>
|
||||
|
||||
<template-output>product_name</template-output>
|
||||
<template-output>product_description</template-output>
|
||||
<template-output>research_objectives</template-output>
|
||||
<template-output>research_depth</template-output>
|
||||
<template-output>research_scope</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Market Definition and Boundaries">
|
||||
@@ -65,49 +85,64 @@ Work with the user to establish:
|
||||
<template-output>segment_boundaries</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Live Market Intelligence Gathering" if="enable_web_research == true">
|
||||
<action>Conduct real-time web research to gather current market data</action>
|
||||
<step n="3" goal="Gather live market intelligence collaboratively">
|
||||
|
||||
<critical>This step performs ACTUAL web searches to gather live market intelligence</critical>
|
||||
<critical>This step REQUIRES WebSearch tool usage - gather CURRENT data from {{current_year}}</critical>
|
||||
<critical>Share findings as you go - make this collaborative, not a black box</critical>
|
||||
|
||||
Conduct systematic research across multiple sources:
|
||||
<action>Let {user_name} know you're searching for current {{market_category}} market data: size, growth, analyst reports, recent trends. Tell them you'll share what you find in a few minutes and review it together.</action>
|
||||
|
||||
<step n="3a" title="Industry Reports and Statistics">
|
||||
<action>Search for latest industry reports, market size data, and growth projections</action>
|
||||
Search queries to execute:
|
||||
- "[market_category] market size [geographic_scope] [current_year]"
|
||||
- "[market_category] industry report Gartner Forrester IDC McKinsey"
|
||||
- "[market_category] market growth rate CAGR forecast"
|
||||
- "[market_category] market trends [current_year]"
|
||||
<step n="3a" title="Search for market size and industry data">
|
||||
<action>Conduct systematic web searches using WebSearch tool:
|
||||
|
||||
<WebSearch>{{market_category}} market size {{geographic_scope}} {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} industry report Gartner Forrester IDC {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} market growth rate CAGR forecast {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} market trends {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} TAM SAM market opportunity {{current_year}}</WebSearch>
|
||||
</action>
|
||||
|
||||
<action>Share findings WITH SOURCES including URLs and dates. Ask if it aligns with their expectations.</action>
|
||||
|
||||
<action>CRITICAL - Validate data before proceeding:
|
||||
|
||||
- Multiple sources with similar figures?
|
||||
- Recent sources ({{current_year}} or within 1-2 years)?
|
||||
- Credible sources (Gartner, Forrester, govt data, reputable pubs)?
|
||||
- Conflicts? Note explicitly, search for more sources, mark [Low Confidence]
|
||||
</action>
|
||||
|
||||
<action if="user_has_questions">Explore surprising data points together</action>
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
|
||||
<template-output>sources_market_size</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3b" title="Regulatory and Government Data">
|
||||
<action>Search government databases and regulatory sources</action>
|
||||
Search for:
|
||||
- Government statistics bureaus
|
||||
- Industry associations
|
||||
- Regulatory body reports
|
||||
- Census and economic data
|
||||
<step n="3b" title="Search for recent news and developments" optional="true">
|
||||
<action>Search for recent market developments:
|
||||
|
||||
<WebSearch>{{market_category}} news {{current_year}} funding acquisitions</WebSearch>
|
||||
<WebSearch>{{market_category}} recent developments {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} regulatory changes {{current_year}}</WebSearch>
|
||||
</action>
|
||||
|
||||
<action>Share noteworthy findings:
|
||||
|
||||
"I found some interesting recent developments:
|
||||
|
||||
{{key_news_highlights}}
|
||||
|
||||
Anything here surprise you or confirm what you suspected?"
|
||||
</action>
|
||||
</step>
|
||||
|
||||
<step n="3c" title="News and Recent Developments">
|
||||
<action>Gather recent news, funding announcements, and market events</action>
|
||||
Search for articles from the last 6-12 months about:
|
||||
- Major deals and acquisitions
|
||||
- Funding rounds in the space
|
||||
- New market entrants
|
||||
- Regulatory changes
|
||||
- Technology disruptions
|
||||
</step>
|
||||
<step n="3c" title="Optional: Government and academic sources" optional="true">
|
||||
<action if="research needs high credibility">Search for authoritative sources:
|
||||
|
||||
<step n="3d" title="Academic and Research Papers">
|
||||
<action>Search for academic research and white papers</action>
|
||||
Look for peer-reviewed studies on:
|
||||
- Market dynamics
|
||||
- Technology adoption patterns
|
||||
- Customer behavior research
|
||||
<WebSearch>{{market_category}} government statistics census data {{current_year}}</WebSearch>
|
||||
<WebSearch>{{market_category}} academic research white papers {{current_year}}</WebSearch>
|
||||
</action>
|
||||
</step>
|
||||
|
||||
<template-output>market_intelligence_raw</template-output>
|
||||
@@ -250,38 +285,36 @@ Analyze:
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Competitive Intelligence" if="enable_competitor_analysis == true">
|
||||
<action>Conduct comprehensive competitive analysis</action>
|
||||
<step n="6" goal="Understand the competitive landscape">
|
||||
<action>Ask if they know their main competitors or if you should search for them.</action>
|
||||
|
||||
<step n="6a" title="Competitor Identification">
|
||||
<action>Create comprehensive competitor list</action>
|
||||
<step n="6a" title="Discover competitors together">
|
||||
<action if="user doesn't know competitors">Search for competitors:
|
||||
|
||||
Search for and categorize:
|
||||
<WebSearch>{{product_category}} competitors {{geographic_scope}} {{current_year}}</WebSearch>
|
||||
<WebSearch>{{product_category}} alternatives comparison {{current_year}}</WebSearch>
|
||||
<WebSearch>top {{product_category}} companies {{current_year}}</WebSearch>
|
||||
</action>
|
||||
|
||||
1. **Direct Competitors** - Same solution, same market
|
||||
2. **Indirect Competitors** - Different solution, same problem
|
||||
3. **Potential Competitors** - Could enter market
|
||||
4. **Substitute Products** - Alternative approaches
|
||||
|
||||
<ask>Do you have a specific list of competitors to analyze, or should I discover them through research?</ask>
|
||||
<action>Present findings. Ask them to pick the 3-5 that matter most (most concerned about or curious to understand).</action>
|
||||
</step>
|
||||
|
||||
<step n="6b" title="Competitor Deep Dive" repeat="5">
|
||||
<action>For top 5 competitors, research and analyze</action>
|
||||
<step n="6b" title="Research each competitor together" repeat="for-each-selected-competitor">
|
||||
<action>For each competitor, search for:
|
||||
- Company overview, product features
|
||||
- Pricing model
|
||||
- Funding and recent news
|
||||
- Customer reviews and ratings
|
||||
|
||||
Gather intelligence on:
|
||||
Use {{current_year}} in all searches.
|
||||
</action>
|
||||
|
||||
- Company overview and history
|
||||
- Product features and positioning
|
||||
- Pricing strategy and models
|
||||
- Target customer focus
|
||||
- Recent news and developments
|
||||
- Funding and financial health
|
||||
- Team and leadership
|
||||
- Customer reviews and sentiment
|
||||
<action>Share findings with sources. Ask what jumps out and if it matches expectations.</action>
|
||||
|
||||
<action if="user has follow-up questions">Dig deeper based on their interests</action>
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<template-output>competitor*analysis*{{competitor_number}}</template-output>
|
||||
<template-output>competitor*analysis*{{competitor_name}}</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6c" title="Competitive Positioning Map">
|
||||
@@ -485,55 +518,99 @@ Provide mitigation strategies.
|
||||
|
||||
</step>
|
||||
|
||||
<step n="11" goal="Executive Summary Creation">
|
||||
<action>Synthesize all findings into executive summary</action>
|
||||
<step n="11" goal="Synthesize findings together into executive summary">
|
||||
|
||||
<critical>Write this AFTER all other sections are complete</critical>
|
||||
<critical>This is the last major content section - make it collaborative</critical>
|
||||
|
||||
Create compelling executive summary with:
|
||||
<action>Review the research journey together. Share high-level summaries of market size, competitive dynamics, customer insights. Ask what stands out most - what surprised them or confirmed their thinking.</action>
|
||||
|
||||
**Market Opportunity:**
|
||||
<action>Collaboratively craft the narrative:
|
||||
|
||||
- TAM/SAM/SOM summary
|
||||
- Growth trajectory
|
||||
- What's the headline? (The ONE thing someone should know)
|
||||
- What are the 3-5 critical insights?
|
||||
- Recommended path forward?
|
||||
- Key risks?
|
||||
|
||||
**Key Insights:**
|
||||
This should read like a strategic brief, not a data dump.
|
||||
</action>
|
||||
|
||||
- Top 3-5 findings
|
||||
- Surprising discoveries
|
||||
- Critical success factors
|
||||
|
||||
**Competitive Landscape:**
|
||||
|
||||
- Market structure
|
||||
- Positioning opportunity
|
||||
|
||||
**Strategic Recommendations:**
|
||||
|
||||
- Priority actions
|
||||
- Go-to-market approach
|
||||
- Investment requirements
|
||||
|
||||
**Risk Summary:**
|
||||
|
||||
- Major risks
|
||||
- Mitigation approach
|
||||
<action>Draft executive summary and share. Ask if it captures the essence and if anything is missing or overemphasized.</action>
|
||||
|
||||
<template-output>executive_summary</template-output>
|
||||
</step>
|
||||
|
||||
<step n="12" goal="Report Compilation and Review">
|
||||
<action>Compile full report and review with user</action>
|
||||
<step n="12" goal="Validate sources and compile report">
|
||||
|
||||
<action>Generate the complete market research report using the template</action>
|
||||
<action>Review all sections for completeness and consistency</action>
|
||||
<action>Ensure all data sources are properly cited</action>
|
||||
<critical>MANDATORY SOURCE VALIDATION - Do NOT skip this step!</critical>
|
||||
|
||||
<action>Before finalizing, conduct source audit:
|
||||
|
||||
Review every major claim in the report and verify:
|
||||
|
||||
**For Market Size Claims:**
|
||||
|
||||
- [ ] At least 2 independent sources cited with URLs
|
||||
- [ ] Sources are from {{current_year}} or within 2 years
|
||||
- [ ] Sources are credible (Gartner, Forrester, govt data, reputable pubs)
|
||||
- [ ] Conflicting estimates are noted with all sources
|
||||
|
||||
**For Competitive Data:**
|
||||
|
||||
- [ ] Competitor information has source URLs
|
||||
- [ ] Pricing data is current and sourced
|
||||
- [ ] Funding data is verified with dates
|
||||
- [ ] Customer reviews/ratings have source links
|
||||
|
||||
**For Growth Rates and Projections:**
|
||||
|
||||
- [ ] CAGR and forecast data are sourced
|
||||
- [ ] Methodology is explained or linked
|
||||
- [ ] Multiple analyst estimates are compared if available
|
||||
|
||||
**For Customer Insights:**
|
||||
|
||||
- [ ] Persona data is based on real research (cited)
|
||||
- [ ] Survey/interview data has sample size and source
|
||||
- [ ] Behavioral claims are backed by studies/data
|
||||
</action>
|
||||
|
||||
<action>Count and document source quality:
|
||||
|
||||
- Total sources cited: {{count_all_sources}}
|
||||
- High confidence (2+ sources): {{high_confidence_claims}}
|
||||
- Single source (needs verification): {{single_source_claims}}
|
||||
- Uncertain/speculative: {{low_confidence_claims}}
|
||||
|
||||
If {{single_source_claims}} or {{low_confidence_claims}} is high, consider additional research.
|
||||
</action>
|
||||
|
||||
<action>Compile full report with ALL sources properly referenced:
|
||||
|
||||
Generate the complete market research report using the template:
|
||||
|
||||
- Ensure every statistic has inline citation: [Source: Company, Year, URL]
|
||||
- Populate all {{sources_*}} template variables
|
||||
- Include confidence levels for major claims
|
||||
- Add References section with full source list
|
||||
</action>
|
||||
|
||||
<action>Present source quality summary to user:
|
||||
|
||||
"I've completed the research with {{count_all_sources}} total sources:
|
||||
|
||||
- {{high_confidence_claims}} claims verified with multiple sources
|
||||
- {{single_source_claims}} claims from single sources (marked for verification)
|
||||
- {{low_confidence_claims}} claims with low confidence or speculation
|
||||
|
||||
Would you like me to strengthen any areas with additional research?"
|
||||
</action>
|
||||
|
||||
<ask>Would you like to review any specific sections before finalizing? Are there any additional analyses you'd like to include?</ask>
|
||||
|
||||
<goto step="9a" if="user requests changes">Return to refine opportunities</goto>
|
||||
|
||||
<template-output>final_report_ready</template-output>
|
||||
<template-output>source_audit_complete</template-output>
|
||||
</step>
|
||||
|
||||
<step n="13" goal="Appendices and Supporting Materials" optional="true">
|
||||
|
||||
@@ -2,7 +2,17 @@
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
|
||||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
<critical>Communicate in {communication_language}, generate documents in {document_output_language}</critical>
|
||||
<critical>Web research is ENABLED - always use current {{current_year}} data</critical>
|
||||
|
||||
<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
|
||||
<critical>NEVER present information without a verified source - if you cannot find a source, say "I could not find reliable data on this"</critical>
|
||||
<critical>ALWAYS cite sources with URLs when presenting data, statistics, or factual claims</critical>
|
||||
<critical>REQUIRE at least 2 independent sources for critical claims (market size, growth rates, competitive data)</critical>
|
||||
<critical>When sources conflict, PRESENT BOTH views and note the discrepancy - do NOT pick one arbitrarily</critical>
|
||||
<critical>Flag any data you are uncertain about with confidence levels: [High Confidence], [Medium Confidence], [Low Confidence - verify]</critical>
|
||||
<critical>Distinguish clearly between: FACTS (from sources), ANALYSIS (your interpretation), and SPECULATION (educated guesses)</critical>
|
||||
<critical>When using WebSearch results, ALWAYS extract and include the source URL for every claim</critical>
|
||||
|
||||
<!-- IDE-INJECT-POINT: research-subagents -->
|
||||
|
||||
@@ -49,43 +59,25 @@
|
||||
</check>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Welcome and Research Type Selection">
|
||||
<action>Welcome the user to the Research Workflow</action>
|
||||
<step n="2" goal="Discover research needs through conversation">
|
||||
|
||||
**The Research Workflow supports multiple research types:**
|
||||
<action>Welcome {user_name} warmly. Position yourself as their research partner who uses live {{current_year}} web data. Ask what they're looking to understand or research.</action>
|
||||
|
||||
Present the user with research type options:
|
||||
<action>Listen and collaboratively identify the research type based on what they describe:
|
||||
|
||||
**What type of research do you need?**
|
||||
- Market/Business questions → Market Research
|
||||
- Competitor questions → Competitive Intelligence
|
||||
- Customer questions → User Research
|
||||
- Technology questions → Technical Research
|
||||
- Industry questions → Domain Research
|
||||
- Creating research prompts for AI platforms → Deep Research Prompt Generator
|
||||
|
||||
1. **Market Research** - Comprehensive market analysis with TAM/SAM/SOM calculations, competitive intelligence, customer segments, and go-to-market strategy
|
||||
- Use for: Market opportunity assessment, competitive landscape analysis, market sizing
|
||||
- Output: Detailed market research report with financials
|
||||
Confirm your understanding of what type would be most helpful and what it will produce.
|
||||
</action>
|
||||
|
||||
2. **Deep Research Prompt Generator** - Create structured, multi-step research prompts optimized for AI platforms (ChatGPT, Gemini, Grok, Claude)
|
||||
- Use for: Generating comprehensive research prompts, structuring complex investigations
|
||||
- Output: Optimized research prompt with framework, scope, and validation criteria
|
||||
|
||||
3. **Technical/Architecture Research** - Evaluate technology stacks, architecture patterns, frameworks, and technical approaches
|
||||
- Use for: Tech stack decisions, architecture pattern selection, framework evaluation
|
||||
- Output: Technical research report with recommendations and trade-off analysis
|
||||
|
||||
4. **Competitive Intelligence** - Deep dive into specific competitors, their strategies, products, and market positioning
|
||||
- Use for: Competitor deep dives, competitive strategy analysis
|
||||
- Output: Competitive intelligence report
|
||||
|
||||
5. **User Research** - Customer insights, personas, jobs-to-be-done, and user behavior analysis
|
||||
- Use for: Customer discovery, persona development, user journey mapping
|
||||
- Output: User research report with personas and insights
|
||||
|
||||
6. **Domain/Industry Research** - Deep dive into specific industries, domains, or subject matter areas
|
||||
- Use for: Industry analysis, domain expertise building, trend analysis
|
||||
- Output: Domain research report
|
||||
|
||||
<ask>Select a research type (1-6) or describe your research needs:</ask>
|
||||
|
||||
<action>Capture user selection as {{research_type}}</action>
|
||||
<action>Capture {{research_type}} and {{research_mode}}</action>
|
||||
|
||||
<template-output>research_type_discovery</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Route to Appropriate Research Instructions">
|
||||
|
||||
@@ -2,38 +2,65 @@
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
|
||||
<critical>This workflow conducts technical research for architecture and technology decisions</critical>
|
||||
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
|
||||
<critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
|
||||
<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for current version info and trends</critical>
|
||||
<critical>ALWAYS verify current versions - NEVER use hardcoded or outdated version numbers</critical>
|
||||
<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
|
||||
<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
|
||||
<critical>NEVER invent version numbers, features, or technical details - ALWAYS verify with current {{current_year}} sources</critical>
|
||||
<critical>Every technical claim (version, feature, performance, compatibility) MUST have a cited source with URL</critical>
|
||||
<critical>Version numbers MUST be verified via WebSearch - do NOT rely on training data (it's outdated!)</critical>
|
||||
<critical>When comparing technologies, cite sources for each claim (performance benchmarks, community size, etc.)</critical>
|
||||
<critical>Mark confidence levels: [Verified {{current_year}} source], [Older source - verify], [Uncertain - needs verification]</critical>
|
||||
<critical>Distinguish: FACT (from official docs/sources), OPINION (from community/reviews), SPECULATION (your analysis)</critical>
|
||||
<critical>If you cannot find current information about a technology, state: "I could not find recent {{current_year}} data on [X]"</critical>
|
||||
<critical>Extract and include source URLs in all technology profiles and comparisons</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Technical Research Discovery">
|
||||
<action>Understand the technical research requirements</action>
|
||||
<step n="1" goal="Discover technical research needs through conversation">
|
||||
|
||||
**Welcome to Technical/Architecture Research!**
|
||||
<action>Engage conversationally based on skill level:
|
||||
|
||||
<ask>What technical decision or research do you need?
|
||||
<check if="{user_skill_level} == 'expert'">
|
||||
"Let's research the technical options for your decision.
|
||||
|
||||
Common scenarios:
|
||||
I'll gather current data from {{current_year}}, compare approaches, and help you think through trade-offs.
|
||||
|
||||
- Evaluate technology stack for a new project
|
||||
- Compare frameworks or libraries (React vs Vue, Postgres vs MongoDB)
|
||||
- Research architecture patterns (microservices, event-driven, CQRS)
|
||||
- Investigate specific technologies or tools
|
||||
- Best practices for specific use cases
|
||||
- Performance and scalability considerations
|
||||
- Security and compliance research</ask>
|
||||
What technical question are you wrestling with?"
|
||||
</check>
|
||||
|
||||
<check if="{user_skill_level} == 'intermediate'">
|
||||
"I'll help you research and evaluate your technical options.
|
||||
|
||||
We'll look at current technologies (using {{current_year}} data), understand the trade-offs, and figure out what fits your needs best.
|
||||
|
||||
What technical decision are you trying to make?"
|
||||
</check>
|
||||
|
||||
<check if="{user_skill_level} == 'beginner'">
|
||||
"Think of this as having a technical advisor help you research your options.
|
||||
|
||||
I'll explain what different technologies do, why you might choose one over another, and help you make an informed decision.
|
||||
|
||||
What technical challenge brought you here?"
|
||||
</check>
|
||||
</action>
|
||||
|
||||
<action>Through conversation, understand:
|
||||
|
||||
- **The technical question** - What they need to decide or understand
|
||||
- **The context** - Greenfield? Brownfield? Learning? Production?
|
||||
- **Current constraints** - Languages, platforms, team skills, budget
|
||||
- **What they already know** - Do they have candidates in mind?
|
||||
|
||||
Don't interrogate - explore together. If they're unsure, help them articulate the problem.
|
||||
</action>
|
||||
|
||||
<template-output>technical_question</template-output>
|
||||
|
||||
<ask>What's the context for this decision?
|
||||
|
||||
- New greenfield project
|
||||
- Adding to existing system (brownfield)
|
||||
- Refactoring/modernizing legacy system
|
||||
- Proof of concept / prototype
|
||||
- Production-ready implementation
|
||||
- Academic/learning purpose</ask>
|
||||
|
||||
<template-output>project_context</template-output>
|
||||
|
||||
</step>
|
||||
@@ -82,49 +109,70 @@ Consider:
|
||||
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Identify Alternatives and Options">
|
||||
<action>Research and identify technology options to evaluate</action>
|
||||
<step n="3" goal="Discover and evaluate technology options together">
|
||||
|
||||
<ask>Do you have specific technologies in mind to compare, or should I discover options?
|
||||
<critical>MUST use WebSearch to find current options from {{current_year}}</critical>
|
||||
|
||||
If you have specific options, list them. Otherwise, I'll research current leading solutions based on your requirements.</ask>
|
||||
<action>Ask if they have candidates in mind:
|
||||
|
||||
<template-output if="user provides options">user_provided_options</template-output>
|
||||
"Do you already have specific technologies you want to compare, or should I search for the current options?"
|
||||
</action>
|
||||
|
||||
<check if="discovering options">
|
||||
<action>Conduct web research to identify current leading solutions</action>
|
||||
<action>Search for:
|
||||
<action if="user has candidates">Great! Let's research: {{user_candidates}}</action>
|
||||
|
||||
- "[technical_category] best tools 2025"
|
||||
- "[technical_category] comparison [use_case]"
|
||||
- "[technical_category] production experiences reddit"
|
||||
- "State of [technical_category] 2025"
|
||||
</action>
|
||||
<action if="discovering options">Search for current leading technologies:
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<WebSearch>{{technical_category}} best tools {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technical_category}} comparison {{use_case}} {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technical_category}} popular frameworks {{current_year}}</WebSearch>
|
||||
<WebSearch>state of {{technical_category}} {{current_year}}</WebSearch>
|
||||
</action>
|
||||
|
||||
<action>Present discovered options (typically 3-5 main candidates)</action>
|
||||
<template-output>technology_options</template-output>
|
||||
<action>Share findings conversationally:
|
||||
|
||||
"Based on current {{current_year}} data, here are the main options:
|
||||
|
||||
{{discovered_options}}
|
||||
|
||||
<check if="{user_skill_level} == 'expert'">
|
||||
These are the leaders right now. Which ones make sense to evaluate for your use case?"
|
||||
</check>
|
||||
|
||||
<check if="{user_skill_level} == 'beginner'">
|
||||
Each of these is popular for different reasons. Let me know if you want me to explain what makes each one different."
|
||||
</check>
|
||||
</action>
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
|
||||
<template-output>technology_options</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Deep Dive Research on Each Option">
|
||||
<action>Research each technology option in depth</action>
|
||||
<step n="4" goal="Research each technology together in depth">
|
||||
|
||||
<critical>For each technology option, research thoroughly</critical>
|
||||
<critical>For each option, use WebSearch to gather CURRENT {{current_year}} information</critical>
|
||||
|
||||
<step n="4a" title="Technology Profile" repeat="for-each-option">
|
||||
<step n="4a" title="Deep dive on each technology" repeat="for-each-option">
|
||||
|
||||
Research and document:
|
||||
<action>For {{technology_name}}, conduct comprehensive research:
|
||||
|
||||
<WebSearch>{{technology_name}} overview what is {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technology_name}} latest version release notes {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technology_name}} pros cons trade-offs {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technology_name}} production experience real world {{current_year}}</WebSearch>
|
||||
<WebSearch>{{technology_name}} vs alternatives comparison {{current_year}}</WebSearch>
|
||||
</action>
|
||||
|
||||
<action>Share findings conversationally and collaboratively:
|
||||
|
||||
"Here's what I found about {{technology_name}}:
|
||||
|
||||
**Overview:**
|
||||
{{what_it_is_and_solves}}
|
||||
|
||||
- What is it and what problem does it solve?
|
||||
- Maturity level (experimental, stable, mature, legacy)
|
||||
- Community size and activity
|
||||
- Maintenance status and release cadence
|
||||
**Current Status ({{current_year}}):**
|
||||
{{maturity_community_release_cadence}}
|
||||
|
||||
**Technical Characteristics:**
|
||||
|
||||
|
||||
@@ -293,6 +293,40 @@
|
||||
|
||||
---
|
||||
|
||||
## References and Sources
|
||||
|
||||
**CRITICAL: All data in this report must be verifiable through the sources listed below**
|
||||
|
||||
### Market Size and Growth Data Sources
|
||||
|
||||
{{sources_market_size}}
|
||||
|
||||
### Competitive Intelligence Sources
|
||||
|
||||
{{sources_competitive}}
|
||||
|
||||
### Customer Research Sources
|
||||
|
||||
{{sources_customer}}
|
||||
|
||||
### Industry Trends and Analysis Sources
|
||||
|
||||
{{sources_trends}}
|
||||
|
||||
### Additional References
|
||||
|
||||
{{sources_additional}}
|
||||
|
||||
### Source Quality Assessment
|
||||
|
||||
- **High Credibility Sources (2+ corroborating):** {{high_confidence_count}} claims
|
||||
- **Medium Credibility (single source):** {{medium_confidence_count}} claims
|
||||
- **Low Credibility (needs verification):** {{low_confidence_count}} claims
|
||||
|
||||
**Note:** Any claim marked [Low Confidence] or [Single source] should be independently verified before making critical business decisions.
|
||||
|
||||
---
|
||||
|
||||
## Document Information
|
||||
|
||||
**Workflow:** BMad Market Research Workflow v1.0
|
||||
@@ -305,7 +339,9 @@
|
||||
- **Data Freshness:** Current as of {{date}}
|
||||
- **Source Reliability:** {{source_reliability_score}}
|
||||
- **Confidence Level:** {{confidence_level}}
|
||||
- **Total Sources Cited:** {{total_sources}}
|
||||
- **Web Searches Conducted:** {{search_count}}
|
||||
|
||||
---
|
||||
|
||||
_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering._
|
||||
_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering. All factual claims are backed by cited sources with verification dates._
|
||||
|
||||
@@ -198,13 +198,48 @@
|
||||
|
||||
---
|
||||
|
||||
## References and Sources
|
||||
|
||||
**CRITICAL: All technical claims, versions, and benchmarks must be verifiable through sources below**
|
||||
|
||||
### Official Documentation and Release Notes
|
||||
|
||||
{{sources_official_docs}}
|
||||
|
||||
### Performance Benchmarks and Comparisons
|
||||
|
||||
{{sources_benchmarks}}
|
||||
|
||||
### Community Experience and Reviews
|
||||
|
||||
{{sources_community}}
|
||||
|
||||
### Architecture Patterns and Best Practices
|
||||
|
||||
{{sources_architecture}}
|
||||
|
||||
### Additional Technical References
|
||||
|
||||
{{sources_additional}}
|
||||
|
||||
### Version Verification
|
||||
|
||||
- **Technologies Researched:** {{technology_count}}
|
||||
- **Versions Verified ({{current_year}}):** {{verified_versions_count}}
|
||||
- **Sources Requiring Update:** {{outdated_sources_count}}
|
||||
|
||||
**Note:** All version numbers were verified using current {{current_year}} sources. Versions may change - always verify latest stable release before implementation.
|
||||
|
||||
---
|
||||
|
||||
## Document Information
|
||||
|
||||
**Workflow:** BMad Research Workflow - Technical Research v2.0
|
||||
**Generated:** {{date}}
|
||||
**Research Type:** Technical/Architecture Research
|
||||
**Next Review:** [Date for review/update]
|
||||
**Total Sources Cited:** {{total_sources}}
|
||||
|
||||
---
|
||||
|
||||
_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis._
|
||||
_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis. All version numbers and technical claims are backed by current {{current_year}} sources._
|
||||
|
||||
@@ -11,6 +11,17 @@ communication_language: "{config_source}:communication_language"
|
||||
document_output_language: "{config_source}:document_output_language"
|
||||
user_skill_level: "{config_source}:user_skill_level"
|
||||
date: system-generated
|
||||
current_year: system-generated
|
||||
current_month: system-generated
|
||||
|
||||
# Research behavior - WEB RESEARCH IS DEFAULT
|
||||
enable_web_research: true
|
||||
|
||||
# Source tracking and verification - CRITICAL FOR ACCURACY
|
||||
require_citations: true
|
||||
require_source_urls: true
|
||||
minimum_sources_per_claim: 2
|
||||
fact_check_critical_data: true
|
||||
|
||||
# Workflow components - ROUTER PATTERN
|
||||
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/research"
|
||||
@@ -47,3 +58,5 @@ web_bundle:
|
||||
- "bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/template-technical.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/checklist.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/checklist-deep-prompt.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/checklist-technical.md"
|
||||
|
||||
Reference in New Issue
Block a user