Ignore and untrack BMad directories
This commit is contained in:
Max
@@ -1,137 +0,0 @@
|
||||
# Domain Research Step 1: Domain Research Scope Confirmation
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user confirmation
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach
|
||||
- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
|
||||
- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
|
||||
- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- ⚠️ Present [C] continue option after scope confirmation
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Research type = "domain" is already set
|
||||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on industry/domain analysis with web research
|
||||
- Web search is required to verify and supplement your knowledge with current facts
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind.
|
||||
|
||||
## DOMAIN SCOPE CONFIRMATION:
|
||||
|
||||
### 1. Begin Scope Confirmation
|
||||
|
||||
Start with domain scope understanding:
|
||||
"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
|
||||
|
||||
**Domain Research Scope:**
|
||||
|
||||
- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape
|
||||
- **Regulatory Environment**: Compliance requirements, regulations, and standards
|
||||
- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation
|
||||
- **Economic Factors**: Market size, growth trends, and economic impact
|
||||
- **Supply Chain**: Value chain analysis and ecosystem relationships
|
||||
|
||||
**Research Approach:**
|
||||
|
||||
- All claims verified against current public sources
|
||||
- Multi-source validation for critical domain claims
|
||||
- Confidence levels for uncertain domain information
|
||||
- Comprehensive domain coverage with industry-specific insights
|
||||
|
||||
### 2. Scope Confirmation
|
||||
|
||||
Present clear scope confirmation:
|
||||
"**Domain Research Scope Confirmation:**
|
||||
|
||||
For **{{research_topic}}**, I will research:
|
||||
|
||||
✅ **Industry Analysis** - market structure, key players, competitive dynamics
|
||||
✅ **Regulatory Requirements** - compliance standards, legal frameworks
|
||||
✅ **Technology Trends** - innovation patterns, digital transformation
|
||||
✅ **Economic Factors** - market size, growth projections, economic impact
|
||||
✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
|
||||
|
||||
**All claims verified against current public sources.**
|
||||
|
||||
**Does this domain research scope and approach align with your goals?**
|
||||
[C] Continue - Begin domain research with this scope
|
||||
|
||||
### 3. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-domain-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append scope confirmation:
|
||||
|
||||
```markdown
|
||||
## Domain Research Scope Confirmation
|
||||
|
||||
**Research Topic:** {{research_topic}}
|
||||
**Research Goals:** {{research_goals}}
|
||||
|
||||
**Domain Research Scope:**
|
||||
|
||||
- Industry Analysis - market structure, competitive landscape
|
||||
- Regulatory Environment - compliance requirements, legal frameworks
|
||||
- Technology Trends - innovation patterns, digital transformation
|
||||
- Economic Factors - market size, growth projections
|
||||
- Supply Chain Analysis - value chain, ecosystem relationships
|
||||
|
||||
**Research Methodology:**
|
||||
|
||||
- All claims verified against current public sources
|
||||
- Multi-source validation for critical domain claims
|
||||
- Confidence level framework for uncertain information
|
||||
- Comprehensive domain coverage with industry-specific insights
|
||||
|
||||
**Scope Confirmed:** {{date}}
|
||||
```
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Domain research scope clearly confirmed with user
|
||||
✅ All domain analysis areas identified and explained
|
||||
✅ Research methodology emphasized
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Scope confirmation documented when user proceeds
|
||||
✅ Proper routing to next domain research step
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not clearly confirming domain research scope with user
|
||||
❌ Missing critical domain analysis areas
|
||||
❌ Not explaining that web search is required for current facts
|
||||
❌ Not presenting [C] continue option
|
||||
❌ Proceeding without user scope confirmation
|
||||
❌ Not routing to next domain research step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
|
||||
@@ -1,229 +0,0 @@
|
||||
# Domain Research Step 2: Industry Analysis
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
|
||||
- 💬 FOCUS on market size, growth, and industry dynamics
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after industry analysis content generation
|
||||
- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from step-01 are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on market size, growth, and industry dynamics
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts.
|
||||
|
||||
## INDUSTRY ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Industry Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
|
||||
|
||||
Start with industry research approach:
|
||||
"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
|
||||
|
||||
**Industry Analysis Focus:**
|
||||
|
||||
- Market size and valuation metrics
|
||||
- Growth rates and market dynamics
|
||||
- Market segmentation and structure
|
||||
- Industry trends and evolution patterns
|
||||
- Economic impact and value creation
|
||||
|
||||
**Let me search for current industry insights.**"
|
||||
|
||||
### 2. Parallel Industry Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} market size value"
|
||||
Search the web: "{{research_topic}} market growth rate dynamics"
|
||||
Search the web: "{{research_topic}} market segmentation structure"
|
||||
Search the web: "{{research_topic}} industry trends evolution"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent market research reports and industry analyses
|
||||
- Search for authoritative sources (market research firms, industry associations)
|
||||
- Identify market size, growth rates, and segmentation data
|
||||
- Research industry trends and evolution patterns
|
||||
- Analyze economic impact and value creation metrics
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Market size and valuation analysis
|
||||
- Growth rates and market dynamics
|
||||
- Market segmentation and structure
|
||||
- Industry trends and evolution patterns
|
||||
|
||||
**Cross-Industry Analysis:**
|
||||
[Identify patterns connecting market dynamics, segmentation, and trends]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Industry Analysis Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare industry analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Industry Analysis
|
||||
|
||||
### Market Size and Valuation
|
||||
|
||||
[Market size analysis with source citations]
|
||||
_Total Market Size: [Current market valuation]_
|
||||
_Growth Rate: [CAGR and market growth projections]_
|
||||
_Market Segments: [Size and value of key market segments]_
|
||||
_Economic Impact: [Economic contribution and value creation]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Dynamics and Growth
|
||||
|
||||
[Market dynamics analysis with source citations]
|
||||
_Growth Drivers: [Key factors driving market growth]_
|
||||
_Growth Barriers: [Factors limiting market expansion]_
|
||||
_Cyclical Patterns: [Industry seasonality and cycles]_
|
||||
_Market Maturity: [Life cycle stage and development phase]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Structure and Segmentation
|
||||
|
||||
[Market structure analysis with source citations]
|
||||
_Primary Segments: [Key market segments and their characteristics]_
|
||||
_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
|
||||
_Geographic Distribution: [Regional market variations and concentrations]_
|
||||
_Vertical Integration: [Supply chain and value chain structure]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Trends and Evolution
|
||||
|
||||
[Industry trends analysis with source citations]
|
||||
_Emerging Trends: [Current industry developments and transformations]_
|
||||
_Historical Evolution: [Industry development over recent years]_
|
||||
_Technology Integration: [How technology is changing the industry]_
|
||||
_Future Outlook: [Projected industry developments and changes]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Dynamics
|
||||
|
||||
[Competitive dynamics analysis with source citations]
|
||||
_Market Concentration: [Level of market consolidation and competition]_
|
||||
_Competitive Intensity: [Degree of competition and rivalry]_
|
||||
_Barriers to Entry: [Obstacles for new market entrants]_
|
||||
_Innovation Pressure: [Rate of innovation and change]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **industry analysis** for {{research_topic}}.
|
||||
|
||||
**Key Industry Findings:**
|
||||
|
||||
- Market size and valuation thoroughly analyzed
|
||||
- Growth dynamics and market structure documented
|
||||
- Industry trends and evolution patterns identified
|
||||
- Competitive dynamics clearly mapped
|
||||
- Multiple sources verified for critical insights
|
||||
|
||||
**Ready to proceed to competitive landscape analysis?**
|
||||
[C] Continue - Save this to document and proceed to competitive landscape
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-competitive-landscape.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Market size and valuation thoroughly analyzed
|
||||
✅ Growth dynamics and market structure documented
|
||||
✅ Industry trends and evolution patterns identified
|
||||
✅ Competitive dynamics clearly mapped
|
||||
✅ Multiple sources verified for critical insights
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (competitive landscape)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical market size or growth data
|
||||
❌ Incomplete market structure analysis
|
||||
❌ Not identifying key industry trends
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to competitive landscape step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## INDUSTRY RESEARCH PROTOCOLS:
|
||||
|
||||
- Research market research reports and industry analyses
|
||||
- Use authoritative sources (market research firms, industry associations)
|
||||
- Analyze market size, growth rates, and segmentation data
|
||||
- Study industry trends and evolution patterns
|
||||
- Search the web to verify facts
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## INDUSTRY ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative industry research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable industry insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and search the web to verify facts!
|
||||
@@ -1,238 +0,0 @@
|
||||
# Domain Research Step 3: Competitive Landscape
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
|
||||
- 💬 FOCUS on key players, market share, and competitive dynamics
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after competitive analysis content generation
|
||||
- 📝 WRITE COMPETITIVE ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on key players, market share, and competitive dynamics
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics. Search the web to verify and supplement current facts.
|
||||
|
||||
## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Competitive Landscape Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
|
||||
|
||||
Start with competitive research approach:
|
||||
"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
|
||||
|
||||
**Competitive Landscape Focus:**
|
||||
|
||||
- Key players and market leaders
|
||||
- Market share and competitive positioning
|
||||
- Competitive strategies and differentiation
|
||||
- Business models and value propositions
|
||||
- Entry barriers and competitive dynamics
|
||||
|
||||
**Let me search for current competitive insights.**"
|
||||
|
||||
### 2. Parallel Competitive Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} key players market leaders"
|
||||
Search the web: "{{research_topic}} market share competitive landscape"
|
||||
Search the web: "{{research_topic}} competitive strategies differentiation"
|
||||
Search the web: "{{research_topic}} entry barriers competitive dynamics"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent competitive intelligence reports and market analyses
|
||||
- Search for company websites, annual reports, and investor presentations
|
||||
- Research market share data and competitive positioning
|
||||
- Analyze competitive strategies and differentiation approaches
|
||||
- Study entry barriers and competitive dynamics
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Key players and market leaders analysis
|
||||
- Market share and competitive positioning assessment
|
||||
- Competitive strategies and differentiation mapping
|
||||
- Entry barriers and competitive dynamics evaluation
|
||||
|
||||
**Cross-Competitive Analysis:**
|
||||
[Identify patterns connecting players, strategies, and market dynamics]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Competitive Landscape Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare competitive landscape analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Competitive Landscape
|
||||
|
||||
### Key Players and Market Leaders
|
||||
|
||||
[Key players analysis with source citations]
|
||||
_Market Leaders: [Dominant players and their market positions]_
|
||||
_Major Competitors: [Significant competitors and their specialties]_
|
||||
_Emerging Players: [New entrants and innovative companies]_
|
||||
_Global vs Regional: [Geographic distribution of key players]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Share and Competitive Positioning
|
||||
|
||||
[Market share analysis with source citations]
|
||||
_Market Share Distribution: [Current market share breakdown]_
|
||||
_Competitive Positioning: [How players position themselves in the market]_
|
||||
_Value Proposition Mapping: [Different value propositions across players]_
|
||||
_Customer Segments Served: [Different customer bases by competitor]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Strategies and Differentiation
|
||||
|
||||
[Competitive strategies analysis with source citations]
|
||||
_Cost Leadership Strategies: [Players competing on price and efficiency]_
|
||||
_Differentiation Strategies: [Players competing on unique value]_
|
||||
_Focus/Niche Strategies: [Players targeting specific segments]_
|
||||
_Innovation Approaches: [How different players innovate]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Business Models and Value Propositions
|
||||
|
||||
[Business models analysis with source citations]
|
||||
_Primary Business Models: [How competitors make money]_
|
||||
_Revenue Streams: [Different approaches to monetization]_
|
||||
_Value Chain Integration: [Vertical integration vs partnership models]_
|
||||
_Customer Relationship Models: [How competitors build customer loyalty]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Dynamics and Entry Barriers
|
||||
|
||||
[Competitive dynamics analysis with source citations]
|
||||
_Barriers to Entry: [Obstacles facing new market entrants]_
|
||||
_Competitive Intensity: [Level of rivalry and competitive pressure]_
|
||||
_Market Consolidation Trends: [M&A activity and market concentration]_
|
||||
_Switching Costs: [Costs for customers to switch between providers]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Ecosystem and Partnership Analysis
|
||||
|
||||
[Ecosystem analysis with source citations]
|
||||
_Supplier Relationships: [Key supplier partnerships and dependencies]_
|
||||
_Distribution Channels: [How competitors reach customers]_
|
||||
_Technology Partnerships: [Strategic technology alliances]_
|
||||
_Ecosystem Control: [Who controls key parts of the value chain]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **competitive landscape analysis** for {{research_topic}}.
|
||||
|
||||
**Key Competitive Findings:**
|
||||
|
||||
- Key players and market leaders thoroughly identified
|
||||
- Market share and competitive positioning clearly mapped
|
||||
- Competitive strategies and differentiation analyzed
|
||||
- Business models and value propositions documented
|
||||
- Competitive dynamics and entry barriers evaluated
|
||||
|
||||
**Ready to proceed to regulatory focus analysis?**
|
||||
[C] Continue - Save this to document and proceed to regulatory focus
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-regulatory-focus.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Key players and market leaders thoroughly identified
|
||||
✅ Market share and competitive positioning clearly mapped
|
||||
✅ Competitive strategies and differentiation analyzed
|
||||
✅ Business models and value propositions documented
|
||||
✅ Competitive dynamics and entry barriers evaluated
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (regulatory focus)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical key players or market leaders
|
||||
❌ Incomplete market share or positioning analysis
|
||||
❌ Not identifying competitive strategies
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to regulatory focus step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## COMPETITIVE RESEARCH PROTOCOLS:
|
||||
|
||||
- Research competitive intelligence reports and market analyses
|
||||
- Use company websites, annual reports, and investor presentations
|
||||
- Analyze market share data and competitive positioning
|
||||
- Study competitive strategies and differentiation approaches
|
||||
- Search the web to verify facts
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## COMPETITIVE ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative competitive intelligence sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable competitive insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and search the web to verify facts!
|
||||
@@ -1,206 +0,0 @@
|
||||
# Domain Research Step 4: Regulatory Focus
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A REGULATORY ANALYST, not content generator
|
||||
- 💬 FOCUS on compliance requirements and regulatory landscape
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after regulatory content generation
|
||||
- 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY save when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on regulatory and compliance requirements for the domain
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct focused regulatory and compliance analysis with emphasis on requirements that impact {{research_topic}}. Search the web to verify and supplement current facts.
|
||||
|
||||
## REGULATORY FOCUS SEQUENCE:
|
||||
|
||||
### 1. Begin Regulatory Analysis
|
||||
|
||||
Start with regulatory research approach:
|
||||
"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
|
||||
|
||||
**Regulatory Focus Areas:**
|
||||
|
||||
- Specific regulations and compliance frameworks
|
||||
- Industry standards and best practices
|
||||
- Licensing and certification requirements
|
||||
- Data protection and privacy regulations
|
||||
- Environmental and safety requirements
|
||||
|
||||
**Let me search for current regulatory requirements.**"
|
||||
|
||||
### 2. Web Search for Specific Regulations
|
||||
|
||||
Search for current regulatory information:
|
||||
Search the web: "{{research_topic}} regulations compliance requirements"
|
||||
|
||||
**Regulatory focus:**
|
||||
|
||||
- Specific regulations applicable to the domain
|
||||
- Compliance frameworks and standards
|
||||
- Recent regulatory changes or updates
|
||||
- Enforcement agencies and oversight bodies
|
||||
|
||||
### 3. Web Search for Industry Standards
|
||||
|
||||
Search for current industry standards:
|
||||
Search the web: "{{research_topic}} standards best practices"
|
||||
|
||||
**Standards focus:**
|
||||
|
||||
- Industry-specific technical standards
|
||||
- Best practices and guidelines
|
||||
- Certification requirements
|
||||
- Quality assurance frameworks
|
||||
|
||||
### 4. Web Search for Data Privacy Requirements
|
||||
|
||||
Search for current privacy regulations:
|
||||
Search the web: "data privacy regulations {{research_topic}}"
|
||||
|
||||
**Privacy focus:**
|
||||
|
||||
- GDPR, CCPA, and other data protection laws
|
||||
- Industry-specific privacy requirements
|
||||
- Data governance and security standards
|
||||
- User consent and data handling requirements
|
||||
|
||||
### 5. Generate Regulatory Analysis Content
|
||||
|
||||
Prepare regulatory content with source citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Regulatory Requirements
|
||||
|
||||
### Applicable Regulations
|
||||
|
||||
[Specific regulations analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Standards and Best Practices
|
||||
|
||||
[Industry standards analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Compliance Frameworks
|
||||
|
||||
[Compliance frameworks analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Protection and Privacy
|
||||
|
||||
[Privacy requirements analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Licensing and Certification
|
||||
|
||||
[Licensing requirements analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Considerations
|
||||
|
||||
[Practical implementation considerations with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Assessment
|
||||
|
||||
[Regulatory and compliance risk assessment]
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Continue Option
|
||||
|
||||
Show the generated regulatory analysis and present continue option:
|
||||
"I've completed **regulatory requirements analysis** for {{research_topic}}.
|
||||
|
||||
**Key Regulatory Findings:**
|
||||
|
||||
- Specific regulations and frameworks identified
|
||||
- Industry standards and best practices mapped
|
||||
- Compliance requirements clearly documented
|
||||
- Implementation considerations provided
|
||||
- Risk assessment completed
|
||||
|
||||
**Ready to proceed to technical trends?**
|
||||
[C] Continue - Save this to the document and move to technical trends
|
||||
|
||||
### 7. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Load: `./step-05-technical-trends.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 5. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Applicable regulations identified with current citations
|
||||
✅ Industry standards and best practices documented
|
||||
✅ Compliance frameworks clearly mapped
|
||||
✅ Data protection requirements analyzed
|
||||
✅ Implementation considerations provided
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical regulatory requirements for the domain
|
||||
❌ Not providing implementation considerations for compliance
|
||||
❌ Not completing risk assessment for regulatory compliance
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## REGULATORY RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for specific regulations by name and number
|
||||
- Identify regulatory bodies and enforcement agencies
|
||||
- Research recent regulatory changes and updates
|
||||
- Map industry standards to regulatory requirements
|
||||
- Consider regional and jurisdictional differences
|
||||
|
||||
## SOURCE VERIFICATION:
|
||||
|
||||
- Always cite regulatory agency websites
|
||||
- Use official government and industry association sources
|
||||
- Note effective dates and implementation timelines
|
||||
- Present compliance requirement levels and obligations
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
|
||||
|
||||
Remember: Search the web to verify regulatory facts and provide practical implementation considerations!
|
||||
@@ -1,234 +0,0 @@
|
||||
# Domain Research Step 5: Technical Trends
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator
|
||||
- 💬 FOCUS on emerging technologies and innovation patterns
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after technical trends content generation
|
||||
- 📝 WRITE TECHNICAL TRENDS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on emerging technologies and innovation patterns in the domain
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive technical trends analysis using current web data with emphasis on innovations and emerging technologies impacting {{research_topic}}.
|
||||
|
||||
## TECHNICAL TRENDS SEQUENCE:
|
||||
|
||||
### 1. Begin Technical Trends Analysis
|
||||
|
||||
Start with technology research approach:
|
||||
"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
|
||||
|
||||
**Technical Trends Focus:**
|
||||
|
||||
- Emerging technologies and innovations
|
||||
- Digital transformation impacts
|
||||
- Automation and efficiency improvements
|
||||
- New business models enabled by technology
|
||||
- Future technology projections and roadmaps
|
||||
|
||||
**Let me search for current technology developments.**"
|
||||
|
||||
### 2. Web Search for Emerging Technologies
|
||||
|
||||
Search for current technology information:
|
||||
Search the web: "{{research_topic}} emerging technologies innovations"
|
||||
|
||||
**Technology focus:**
|
||||
|
||||
- AI, machine learning, and automation impacts
|
||||
- Digital transformation trends
|
||||
- New technologies disrupting the industry
|
||||
- Innovation patterns and breakthrough developments
|
||||
|
||||
### 3. Web Search for Digital Transformation
|
||||
|
||||
Search for current transformation trends:
|
||||
Search the web: "{{research_topic}} digital transformation trends"
|
||||
|
||||
**Transformation focus:**
|
||||
|
||||
- Digital adoption trends and rates
|
||||
- Business model evolution
|
||||
- Customer experience innovations
|
||||
- Operational efficiency improvements
|
||||
|
||||
### 4. Web Search for Future Outlook
|
||||
|
||||
Search for future projections:
|
||||
Search the web: "{{research_topic}} future outlook trends"
|
||||
|
||||
**Future focus:**
|
||||
|
||||
- Technology roadmaps and projections
|
||||
- Market evolution predictions
|
||||
- Innovation pipelines and R&D trends
|
||||
- Long-term industry transformation
|
||||
|
||||
### 5. Generate Technical Trends Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare technical analysis with source citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Technical Trends and Innovation
|
||||
|
||||
### Emerging Technologies
|
||||
|
||||
[Emerging technologies analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Digital Transformation
|
||||
|
||||
[Digital transformation analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Innovation Patterns
|
||||
|
||||
[Innovation patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Future Outlook
|
||||
|
||||
[Future outlook and projections with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Opportunities
|
||||
|
||||
[Implementation opportunity analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Challenges and Risks
|
||||
|
||||
[Challenges and risks assessment with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
## Recommendations
|
||||
|
||||
### Technology Adoption Strategy
|
||||
|
||||
[Technology adoption recommendations]
|
||||
|
||||
### Innovation Roadmap
|
||||
|
||||
[Innovation roadmap suggestions]
|
||||
|
||||
### Risk Mitigation
|
||||
|
||||
[Risk mitigation strategies]
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Complete Option
|
||||
|
||||
Show the generated technical analysis and present complete option:
|
||||
"I've completed **technical trends and innovation analysis** for {{research_topic}}.
|
||||
|
||||
**Technical Highlights:**
|
||||
|
||||
- Emerging technologies and innovations identified
|
||||
- Digital transformation trends mapped
|
||||
- Future outlook and projections analyzed
|
||||
- Implementation opportunities and challenges documented
|
||||
- Practical recommendations provided
|
||||
|
||||
**Technical Trends Research Completed:**
|
||||
|
||||
- Emerging technologies and innovations identified
|
||||
- Digital transformation trends mapped
|
||||
- Future outlook and projections analyzed
|
||||
- Implementation opportunities and challenges documented
|
||||
|
||||
**Ready to proceed to research synthesis and recommendations?**
|
||||
[C] Continue - Save this to document and proceed to synthesis
|
||||
|
||||
### 7. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
||||
- Load: `./step-06-research-synthesis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 5. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Emerging technologies identified with current data
|
||||
✅ Digital transformation trends clearly documented
|
||||
✅ Future outlook and projections analyzed
|
||||
✅ Implementation opportunities and challenges mapped
|
||||
✅ Strategic recommendations provided
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (research synthesis)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Missing critical emerging technologies in the domain
|
||||
❌ Not providing practical implementation recommendations
|
||||
❌ Not completing strategic recommendations
|
||||
❌ Not presenting completion option for research workflow
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## TECHNICAL RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for cutting-edge technologies and innovations
|
||||
- Identify disruption patterns and game-changers
|
||||
- Research technology adoption timelines and barriers
|
||||
- Consider regional technology variations
|
||||
- Analyze competitive technological advantages
|
||||
|
||||
## RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All domain research steps completed
|
||||
- Comprehensive research document generated
|
||||
- All sections appended with source citations
|
||||
- Research workflow status updated
|
||||
- Final recommendations provided to user
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
Research workflow complete. User may:
|
||||
|
||||
- Use the domain research to inform other workflows (PRD, architecture, etc.)
|
||||
- Conduct additional research on specific topics if needed
|
||||
- Move forward with product development based on research insights
|
||||
|
||||
Congratulations on completing comprehensive domain research! 🎉
|
||||
@@ -1,443 +0,0 @@
|
||||
# Domain Research Step 6: Research Synthesis and Completion
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on comprehensive synthesis and authoritative conclusions
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after synthesis content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - comprehensive domain analysis
|
||||
- **Research goals = "{{research_goals}}"** - achieved through exhaustive research
|
||||
- All domain research sections have been completed (analysis, regulatory, technical)
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final synthesis step producing the complete research document
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Produce a comprehensive, authoritative research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive domain research.
|
||||
|
||||
## COMPREHENSIVE DOCUMENT SYNTHESIS:
|
||||
|
||||
### 1. Document Structure Planning
|
||||
|
||||
**Complete Research Document Structure:**
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]: Comprehensive {{research_topic}} Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Brief compelling overview of key findings and implications]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- Research Introduction and Methodology
|
||||
- Industry Overview and Market Dynamics
|
||||
- Technology Trends and Innovation Landscape
|
||||
- Regulatory Framework and Compliance Requirements
|
||||
- Competitive Landscape and Key Players
|
||||
- Strategic Insights and Recommendations
|
||||
- Implementation Considerations and Risk Assessment
|
||||
- Future Outlook and Strategic Opportunities
|
||||
- Research Methodology and Source Documentation
|
||||
- Appendices and Additional Resources
|
||||
```
|
||||
|
||||
### 2. Generate Compelling Narrative Introduction
|
||||
|
||||
**Introduction Requirements:**
|
||||
|
||||
- Hook reader with compelling opening about {{research_topic}}
|
||||
- Establish research significance and timeliness
|
||||
- Outline comprehensive research methodology
|
||||
- Preview key findings and strategic implications
|
||||
- Set professional, authoritative tone
|
||||
|
||||
**Web Search for Introduction Context:**
|
||||
Search the web: "{{research_topic}} significance importance"
|
||||
|
||||
### 3. Synthesize All Research Sections
|
||||
|
||||
**Section-by-Section Integration:**
|
||||
|
||||
- Combine industry analysis from step-02
|
||||
- Integrate regulatory focus from step-03
|
||||
- Incorporate technical trends from step-04
|
||||
- Add cross-sectional insights and connections
|
||||
- Ensure comprehensive coverage with no gaps
|
||||
|
||||
### 4. Generate Complete Document Content
|
||||
|
||||
#### Final Document Structure:
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]: Comprehensive {{research_topic}} Domain Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive current research]
|
||||
|
||||
**Key Findings:**
|
||||
|
||||
- [Most significant market dynamics]
|
||||
- [Critical regulatory considerations]
|
||||
- [Important technology trends]
|
||||
- [Strategic implications]
|
||||
|
||||
**Strategic Recommendations:**
|
||||
|
||||
- [Top 3-5 actionable recommendations based on research]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. Research Introduction and Methodology
|
||||
2. {{research_topic}} Industry Overview and Market Dynamics
|
||||
3. Technology Landscape and Innovation Trends
|
||||
4. Regulatory Framework and Compliance Requirements
|
||||
5. Competitive Landscape and Ecosystem Analysis
|
||||
6. Strategic Insights and Domain Opportunities
|
||||
7. Implementation Considerations and Risk Assessment
|
||||
8. Future Outlook and Strategic Planning
|
||||
9. Research Methodology and Source Verification
|
||||
10. Appendices and Additional Resources
|
||||
|
||||
## 1. Research Introduction and Methodology
|
||||
|
||||
### Research Significance
|
||||
|
||||
[Compelling narrative about why {{research_topic}} research is critical right now]
|
||||
_Why this research matters now: [Strategic importance with current context]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Research Methodology
|
||||
|
||||
[Comprehensive description of research approach including:]
|
||||
|
||||
- **Research Scope**: [Comprehensive coverage areas]
|
||||
- **Data Sources**: [Authoritative sources and verification approach]
|
||||
- **Analysis Framework**: [Structured analysis methodology]
|
||||
- **Time Period**: [current focus and historical context]
|
||||
- **Geographic Coverage**: [Regional/global scope]
|
||||
|
||||
### Research Goals and Objectives
|
||||
|
||||
**Original Goals:** {{research_goals}}
|
||||
|
||||
**Achieved Objectives:**
|
||||
|
||||
- [Goal 1 achievement with supporting evidence]
|
||||
- [Goal 2 achievement with supporting evidence]
|
||||
- [Additional insights discovered during research]
|
||||
|
||||
## 2. {{research_topic}} Industry Overview and Market Dynamics
|
||||
|
||||
### Market Size and Growth Projections
|
||||
|
||||
[Comprehensive market analysis synthesized from step-02 with current data]
|
||||
_Market Size: [Current market valuation]_
|
||||
_Growth Rate: [CAGR and projections]_
|
||||
_Market Drivers: [Key growth factors]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Structure and Value Chain
|
||||
|
||||
[Complete industry structure analysis]
|
||||
_Value Chain Components: [Detailed breakdown]_
|
||||
_Industry Segments: [Market segmentation analysis]_
|
||||
_Economic Impact: [Industry economic significance]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Technology Landscape and Innovation Trends
|
||||
|
||||
### Current Technology Adoption
|
||||
|
||||
[Technology trends analysis from step-04 with current context]
|
||||
_Emerging Technologies: [Key technologies affecting {{research_topic}}]_
|
||||
_Adoption Patterns: [Technology adoption rates and patterns]_
|
||||
_Innovation Drivers: [Factors driving technology change]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Digital Transformation Impact
|
||||
|
||||
[Comprehensive analysis of technology's impact on {{research_topic}}]
|
||||
_Transformation Trends: [Major digital transformation patterns]_
|
||||
_Disruption Opportunities: [Technology-driven opportunities]_
|
||||
_Future Technology Outlook: [Emerging technologies and timelines]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Regulatory Framework and Compliance Requirements
|
||||
|
||||
### Current Regulatory Landscape
|
||||
|
||||
[Regulatory analysis from step-03 with current updates]
|
||||
_Key Regulations: [Critical regulatory requirements]_
|
||||
_Compliance Standards: [Industry standards and best practices]_
|
||||
_Recent Changes: [current regulatory updates and implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk and Compliance Considerations
|
||||
|
||||
[Comprehensive risk assessment]
|
||||
_Compliance Risks: [Major regulatory and compliance risks]_
|
||||
_Risk Mitigation Strategies: [Approaches to manage regulatory risks]_
|
||||
_Future Regulatory Trends: [Anticipated regulatory developments]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Competitive Landscape and Ecosystem Analysis
|
||||
|
||||
### Market Positioning and Key Players
|
||||
|
||||
[Competitive analysis with current market positioning]
|
||||
_Market Leaders: [Dominant players and strategies]_
|
||||
_Emerging Competitors: [New entrants and innovative approaches]_
|
||||
_Competitive Dynamics: [Market competition patterns and trends]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Ecosystem and Partnership Landscape
|
||||
|
||||
[Complete ecosystem analysis]
|
||||
_Ecosystem Players: [Key stakeholders and relationships]_
|
||||
_Partnership Opportunities: [Strategic collaboration potential]_
|
||||
_Supply Chain Dynamics: [Supply chain structure and risks]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Strategic Insights and Domain Opportunities
|
||||
|
||||
### Cross-Domain Synthesis
|
||||
|
||||
[Strategic insights from integrating all research sections]
|
||||
_Market-Technology Convergence: [How technology and market forces interact]_
|
||||
_Regulatory-Strategic Alignment: [How regulatory environment shapes strategy]_
|
||||
_Competitive Positioning Opportunities: [Strategic advantages based on research]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Opportunities
|
||||
|
||||
[High-value opportunities identified through comprehensive research]
|
||||
_Market Opportunities: [Specific market entry or expansion opportunities]_
|
||||
_Technology Opportunities: [Technology adoption or innovation opportunities]_
|
||||
_Partnership Opportunities: [Strategic collaboration and partnership potential]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Implementation Considerations and Risk Assessment
|
||||
|
||||
### Implementation Framework
|
||||
|
||||
[Practical implementation guidance based on research findings]
|
||||
_Implementation Timeline: [Recommended phased approach]_
|
||||
_Resource Requirements: [Key resources and capabilities needed]_
|
||||
_Success Factors: [Critical success factors for implementation]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Management and Mitigation
|
||||
|
||||
[Comprehensive risk assessment and mitigation strategies]
|
||||
_Implementation Risks: [Major risks and mitigation approaches]_
|
||||
_Market Risks: [Market-related risks and contingency plans]_
|
||||
_Technology Risks: [Technology adoption and implementation risks]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Future Outlook and Strategic Planning
|
||||
|
||||
### Future Trends and Projections
|
||||
|
||||
[Forward-looking analysis based on comprehensive research]
|
||||
_Near-term Outlook: [1-2 year projections and implications]_
|
||||
_Medium-term Trends: [3-5 year expected developments]_
|
||||
_Long-term Vision: [5+ year strategic outlook for {{research_topic}}]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
[Comprehensive strategic recommendations]
|
||||
_Immediate Actions: [Priority actions for next 6 months]_
|
||||
_Strategic Initiatives: [Key strategic initiatives for 1-2 years]_
|
||||
_Long-term Strategy: [Strategic positioning for 3+ years]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Research Methodology and Source Verification
|
||||
|
||||
### Comprehensive Source Documentation
|
||||
|
||||
[Complete documentation of all research sources]
|
||||
_Primary Sources: [Key authoritative sources used]_
|
||||
_Secondary Sources: [Supporting research and analysis]_
|
||||
_Web Search Queries: [Complete list of search queries used]_
|
||||
|
||||
### Research Quality Assurance
|
||||
|
||||
[Quality assurance and validation approach]
|
||||
_Source Verification: [All factual claims verified with multiple sources]_
|
||||
_Confidence Levels: [Confidence assessments for uncertain data]_
|
||||
_Limitations: [Research limitations and areas for further investigation]_
|
||||
_Methodology Transparency: [Complete transparency about research approach]_
|
||||
|
||||
## 10. Appendices and Additional Resources
|
||||
|
||||
### Detailed Data Tables
|
||||
|
||||
[Comprehensive data tables supporting research findings]
|
||||
_Market Data Tables: [Detailed market size, growth, and segmentation data]_
|
||||
_Technology Adoption Data: [Detailed technology adoption and trend data]_
|
||||
_Regulatory Reference Tables: [Complete regulatory requirements and compliance data]_
|
||||
|
||||
### Additional Resources
|
||||
|
||||
[Valuable resources for continued research and implementation]
|
||||
_Industry Associations: [Key industry organizations and resources]_
|
||||
_Research Organizations: [Authoritative research institutions and reports]_
|
||||
_Government Resources: [Regulatory agencies and official resources]_
|
||||
_Professional Networks: [Industry communities and knowledge sources]_
|
||||
|
||||
---
|
||||
|
||||
## Research Conclusion
|
||||
|
||||
### Summary of Key Findings
|
||||
|
||||
[Comprehensive summary of the most important research findings]
|
||||
|
||||
### Strategic Impact Assessment
|
||||
|
||||
[Assessment of strategic implications for {{research_topic}}]
|
||||
|
||||
### Next Steps Recommendations
|
||||
|
||||
[Specific next steps for leveraging this research]
|
||||
|
||||
---
|
||||
|
||||
**Research Completion Date:** {{date}}
|
||||
**Research Period:** Comprehensive analysis
|
||||
**Document Length:** As needed for comprehensive coverage
|
||||
**Source Verification:** All facts cited with sources
|
||||
**Confidence Level:** High - based on multiple authoritative sources
|
||||
|
||||
_This comprehensive research document serves as an authoritative reference on {{research_topic}} and provides strategic insights for informed decision-making._
|
||||
```
|
||||
|
||||
### 5. Present Complete Document and Final Option
|
||||
|
||||
**Document Completion Presentation:**
|
||||
|
||||
"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
|
||||
|
||||
**Document Features:**
|
||||
|
||||
- **Compelling Narrative Introduction**: Engaging opening that establishes research significance
|
||||
- **Comprehensive Table of Contents**: Complete navigation structure for easy reference
|
||||
- **Exhaustive Research Coverage**: All aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Summary**: Key findings and strategic implications highlighted
|
||||
- **Strategic Recommendations**: Actionable insights based on comprehensive research
|
||||
- **Complete Source Citations**: Every factual claim verified with sources
|
||||
|
||||
**Research Completeness:**
|
||||
|
||||
- Industry analysis and market dynamics fully documented
|
||||
- Technology trends and innovation landscape comprehensively covered
|
||||
- Regulatory framework and compliance requirements detailed
|
||||
- Competitive landscape and ecosystem analysis complete
|
||||
- Strategic insights and implementation guidance provided
|
||||
|
||||
**Document Standards Met:**
|
||||
|
||||
- Exhaustive research with no critical gaps
|
||||
- Professional structure and compelling narrative
|
||||
- As long as needed for comprehensive coverage
|
||||
- Multiple independent sources for all claims
|
||||
- Proper citations throughout
|
||||
|
||||
**Ready to complete this comprehensive research document?**
|
||||
[C] Complete Research - Save final comprehensive document
|
||||
|
||||
### 6. Handle Final Completion
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the complete document to the research file
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
||||
- Complete the domain research workflow
|
||||
- Provide final document delivery confirmation
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the complete comprehensive research document using the full structure above.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Compelling narrative introduction with research significance
|
||||
✅ Comprehensive table of contents with complete document structure
|
||||
✅ Exhaustive research coverage across all domain aspects
|
||||
✅ Executive summary with key findings and strategic implications
|
||||
✅ Strategic recommendations grounded in comprehensive research
|
||||
✅ Complete source verification with citations
|
||||
✅ Professional document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Domain research workflow completed with comprehensive document
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not producing compelling narrative introduction
|
||||
❌ Missing comprehensive table of contents
|
||||
❌ Incomplete research coverage across domain aspects
|
||||
❌ Not providing executive summary with key findings
|
||||
❌ Missing strategic recommendations based on research
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing document without professional structure
|
||||
❌ Not presenting completion option for final document
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## COMPREHENSIVE DOCUMENT STANDARDS:
|
||||
|
||||
This step ensures the final research document:
|
||||
|
||||
- Serves as an authoritative reference on {{research_topic}}
|
||||
- Provides compelling narrative and professional structure
|
||||
- Includes comprehensive coverage with no gaps
|
||||
- Maintains rigorous source verification standards
|
||||
- Delivers strategic insights and actionable recommendations
|
||||
- Meets professional research document quality standards
|
||||
|
||||
## DOMAIN RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All domain research steps completed (1-5)
|
||||
- Comprehensive domain research document generated
|
||||
- Professional document structure with intro, TOC, and summary
|
||||
- All sections appended with source citations
|
||||
- Domain research workflow status updated to complete
|
||||
- Final comprehensive research document delivered to user
|
||||
|
||||
## FINAL DELIVERABLE:
|
||||
|
||||
Complete authoritative research document on {{research_topic}} that:
|
||||
|
||||
- Establishes professional credibility through comprehensive research
|
||||
- Provides strategic insights for informed decision-making
|
||||
- Serves as reference document for continued use
|
||||
- Maintains highest research quality standards
|
||||
|
||||
Congratulations on completing comprehensive domain research! 🎉
|
||||
@@ -1,182 +0,0 @@
|
||||
# Market Research Step 1: Market Research Initialization
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate research content in init step
|
||||
- ✅ ALWAYS confirm understanding of user's research goals
|
||||
- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
|
||||
- 💬 FOCUS on clarifying scope and approach
|
||||
- 🔍 NO WEB RESEARCH in init - that's for later steps
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Confirm research understanding before proceeding
|
||||
- ⚠️ Present [C] continue option after scope clarification
|
||||
- 💾 Write initial scope document immediately
|
||||
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from main workflow discovery are available
|
||||
- Research type = "market" is already set
|
||||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on market research scope clarification
|
||||
- Web search capabilities are enabled for later steps
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
|
||||
|
||||
## MARKET RESEARCH INITIALIZATION:
|
||||
|
||||
### 1. Confirm Research Understanding
|
||||
|
||||
**INITIALIZE - DO NOT RESEARCH YET**
|
||||
|
||||
Start with research confirmation:
|
||||
"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
|
||||
|
||||
**My Understanding of Your Research Needs:**
|
||||
|
||||
- **Research Topic**: {{research_topic}}
|
||||
- **Research Goals**: {{research_goals}}
|
||||
- **Research Type**: Market Research
|
||||
- **Approach**: Comprehensive market analysis with source verification
|
||||
|
||||
**Market Research Areas We'll Cover:**
|
||||
|
||||
- Market size, growth dynamics, and trends
|
||||
- Customer insights and behavior analysis
|
||||
- Competitive landscape and positioning
|
||||
- Strategic recommendations and implementation guidance
|
||||
|
||||
**Does this accurately capture what you're looking for?**"
|
||||
|
||||
### 2. Refine Research Scope
|
||||
|
||||
Gather any clarifications needed:
|
||||
|
||||
#### Scope Clarification Questions:
|
||||
|
||||
- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
|
||||
- "Should we focus on specific geographic regions or global market?"
|
||||
- "Is this for market entry, expansion, product development, or other business purpose?"
|
||||
- "Any competitors or market segments you specifically want us to analyze?"
|
||||
|
||||
### 3. Document Initial Scope
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Write initial research scope to document:
|
||||
|
||||
```markdown
|
||||
# Market Research: {{research_topic}}
|
||||
|
||||
## Research Initialization
|
||||
|
||||
### Research Understanding Confirmed
|
||||
|
||||
**Topic**: {{research_topic}}
|
||||
**Goals**: {{research_goals}}
|
||||
**Research Type**: Market Research
|
||||
**Date**: {{date}}
|
||||
|
||||
### Research Scope
|
||||
|
||||
**Market Analysis Focus Areas:**
|
||||
|
||||
- Market size, growth projections, and dynamics
|
||||
- Customer segments, behavior patterns, and insights
|
||||
- Competitive landscape and positioning analysis
|
||||
- Strategic recommendations and implementation guidance
|
||||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current web data with source verification
|
||||
- Multiple independent sources for critical claims
|
||||
- Confidence level assessment for uncertain data
|
||||
- Comprehensive coverage with no critical gaps
|
||||
|
||||
### Next Steps
|
||||
|
||||
**Research Workflow:**
|
||||
|
||||
1. ✅ Initialization and scope setting (current step)
|
||||
2. Customer Insights and Behavior Analysis
|
||||
3. Competitive Landscape Analysis
|
||||
4. Strategic Synthesis and Recommendations
|
||||
|
||||
**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
|
||||
```
|
||||
|
||||
### 4. Present Confirmation and Continue Option
|
||||
|
||||
Show initial scope document and present continue option:
|
||||
"I've documented our understanding and initial scope for **{{research_topic}}** market research.
|
||||
|
||||
**What I've established:**
|
||||
|
||||
- Research topic and goals confirmed
|
||||
- Market analysis focus areas defined
|
||||
- Research methodology verification
|
||||
- Clear workflow progression
|
||||
|
||||
**Document Status:** Initial scope written to research file for your review
|
||||
|
||||
**Ready to begin detailed market research?**
|
||||
[C] Continue - Confirm scope and proceed to customer insights analysis
|
||||
[Modify] Suggest changes to research scope before proceeding
|
||||
|
||||
### 5. Handle User Response
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Add confirmation note to document: "Scope confirmed by user on {{date}}"
|
||||
- Load: `./step-02-customer-insights.md`
|
||||
|
||||
#### If 'Modify':
|
||||
|
||||
- Gather user changes to scope
|
||||
- Update document with modifications
|
||||
- Re-present updated scope for confirmation
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Research topic and goals accurately understood
|
||||
✅ Market research scope clearly defined
|
||||
✅ Initial scope document written immediately
|
||||
✅ User opportunity to review and modify scope
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Document properly updated with scope confirmation
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not confirming understanding of research topic and goals
|
||||
❌ Generating research content instead of just scope clarification
|
||||
❌ Not writing initial scope document to file
|
||||
❌ Not providing opportunity for user to modify scope
|
||||
❌ Proceeding to next step without user confirmation
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## INITIALIZATION PRINCIPLES:
|
||||
|
||||
This step ensures:
|
||||
|
||||
- Clear mutual understanding of research objectives
|
||||
- Well-defined research scope and approach
|
||||
- Immediate documentation for user review
|
||||
- User control over research direction before detailed work begins
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user confirmation and scope finalization, load `./step-02-customer-insights.md` to begin detailed market research with customer insights analysis.
|
||||
|
||||
Remember: Init steps confirm understanding and scope, not generate research content!
|
||||
@@ -1,237 +0,0 @@
|
||||
# Market Research Step 2: Customer Behavior and Segments
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
|
||||
- 💬 FOCUS on customer behavior patterns and demographic analysis
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after customer behavior content generation
|
||||
- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from step-01 are available
|
||||
- Focus on customer behavior patterns and demographic analysis
|
||||
- Web search capabilities with source verification are enabled
|
||||
- Previous step confirmed research scope and goals
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer behavior and segment analysis with emphasis on patterns and demographics.
|
||||
|
||||
## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Customer Behavior Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer behavior research approach:
|
||||
"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
|
||||
|
||||
**Customer Behavior Focus:**
|
||||
|
||||
- Customer behavior patterns and preferences
|
||||
- Demographic profiles and segmentation
|
||||
- Psychographic characteristics and values
|
||||
- Behavior drivers and influences
|
||||
- Customer interaction patterns and engagement
|
||||
|
||||
**Let me search for current customer behavior insights.**"
|
||||
|
||||
### 2. Parallel Customer Behavior Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} customer behavior patterns"
|
||||
Search the web: "{{research_topic}} customer demographics"
|
||||
Search the web: "{{research_topic}} psychographic profiles"
|
||||
Search the web: "{{research_topic}} customer behavior drivers"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for customer behavior studies and research reports
|
||||
- Search for demographic segmentation and analysis
|
||||
- Research psychographic profiling and value systems
|
||||
- Analyze behavior drivers and influencing factors
|
||||
- Study customer interaction and engagement patterns
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Customer behavior patterns and preferences
|
||||
- Demographic profiles and segmentation
|
||||
- Psychographic characteristics and values
|
||||
- Behavior drivers and influences
|
||||
- Customer interaction patterns and engagement
|
||||
|
||||
**Cross-Behavior Analysis:**
|
||||
[Identify patterns connecting demographics, psychographics, and behaviors]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Customer Behavior Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare customer behavior analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Customer Behavior and Segments
|
||||
|
||||
### Customer Behavior Patterns
|
||||
|
||||
[Customer behavior patterns analysis with source citations]
|
||||
_Behavior Drivers: [Key motivations and patterns from web search]_
|
||||
_Interaction Preferences: [Customer engagement and interaction patterns]_
|
||||
_Decision Habits: [How customers typically make decisions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Demographic Segmentation
|
||||
|
||||
[Demographic analysis with source citations]
|
||||
_Age Demographics: [Age groups and preferences]_
|
||||
_Income Levels: [Income segments and purchasing behavior]_
|
||||
_Geographic Distribution: [Regional/city differences]_
|
||||
_Education Levels: [Education impact on behavior]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Psychographic Profiles
|
||||
|
||||
[Psychographic analysis with source citations]
|
||||
_Values and Beliefs: [Core values driving customer behavior]_
|
||||
_Lifestyle Preferences: [Lifestyle choices and behaviors]_
|
||||
_Attitudes and Opinions: [Customer attitudes toward products/services]_
|
||||
_Personality Traits: [Personality influences on behavior]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Segment Profiles
|
||||
|
||||
[Detailed customer segment profiles with source citations]
|
||||
_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Behavior Drivers and Influences
|
||||
|
||||
[Behavior drivers analysis with source citations]
|
||||
_Emotional Drivers: [Emotional factors influencing behavior]_
|
||||
_Rational Drivers: [Logical decision factors]_
|
||||
_Social Influences: [Social and peer influences]_
|
||||
_Economic Influences: [Economic factors affecting behavior]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Interaction Patterns
|
||||
|
||||
[Customer interaction analysis with source citations]
|
||||
_Research and Discovery: [How customers find and research options]_
|
||||
_Purchase Decision Process: [Steps in purchase decision making]_
|
||||
_Post-Purchase Behavior: [After-purchase engagement patterns]_
|
||||
_Loyalty and Retention: [Factors driving customer loyalty]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
|
||||
|
||||
**Key Customer Behavior Findings:**
|
||||
|
||||
- Customer behavior patterns clearly identified with drivers
|
||||
- Demographic segmentation thoroughly analyzed
|
||||
- Psychographic profiles mapped and documented
|
||||
- Customer interaction patterns captured
|
||||
- Multiple sources verified for critical insights
|
||||
|
||||
**Ready to proceed to customer pain points?**
|
||||
[C] Continue - Save this to document and proceed to pain points analysis
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-customer-pain-points.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer behavior patterns identified with current citations
|
||||
✅ Demographic segmentation thoroughly analyzed
|
||||
✅ Psychographic profiles clearly documented
|
||||
✅ Customer interaction patterns captured
|
||||
✅ Multiple sources verified for critical insights
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (customer pain points)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer behavior patterns
|
||||
❌ Incomplete demographic segmentation analysis
|
||||
❌ Missing psychographic profile documentation
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to customer pain points analysis step
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## CUSTOMER BEHAVIOR RESEARCH PROTOCOLS:
|
||||
|
||||
- Research customer behavior studies and market research
|
||||
- Use demographic data from authoritative sources
|
||||
- Research psychographic profiling and value systems
|
||||
- Analyze customer interaction and engagement patterns
|
||||
- Focus on current behavior data and trends
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## BEHAVIOR ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative customer research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable customer insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification!
|
||||
@@ -1,200 +0,0 @@
|
||||
# Market Research Step 2: Customer Insights
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
|
||||
- 💬 FOCUS on customer behavior and needs analysis
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after customer insights content generation
|
||||
- 💾 ONLY save when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from step-01 are available
|
||||
- Focus on customer behavior and needs analysis
|
||||
- Web search capabilities with source verification are enabled
|
||||
- May need to search for current customer behavior trends
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs.
|
||||
|
||||
## CUSTOMER INSIGHTS SEQUENCE:
|
||||
|
||||
### 1. Begin Customer Insights Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly
|
||||
|
||||
Start with customer research approach:
|
||||
"Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
|
||||
|
||||
**Customer Insights Focus:**
|
||||
|
||||
- Customer behavior patterns and preferences
|
||||
- Pain points and challenges
|
||||
- Decision-making processes
|
||||
- Customer journey mapping
|
||||
- Customer satisfaction drivers
|
||||
- Demographic and psychographic profiles
|
||||
|
||||
**Let me search for current customer insights using parallel web searches for comprehensive coverage.**"
|
||||
|
||||
### 2. Parallel Customer Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "[product/service/market] customer behavior patterns"
|
||||
Search the web: "[product/service/market] customer pain points challenges"
|
||||
Search the web: "[product/service/market] customer decision process"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for customer behavior studies and surveys
|
||||
- Search for customer experience and interaction patterns
|
||||
- Research customer satisfaction methodologies
|
||||
- Note generational and cultural customer variations
|
||||
- Research customer pain points and frustrations
|
||||
- Analyze decision-making processes and criteria
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Customer behavior patterns and preferences
|
||||
- Pain points and challenges
|
||||
- Decision-making processes and journey mapping
|
||||
|
||||
**Cross-Customer Analysis:**
|
||||
[Identify patterns connecting behavior, pain points, and decisions]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Customer Insights Content
|
||||
|
||||
Prepare customer analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Customer Insights
|
||||
|
||||
### Customer Behavior Patterns
|
||||
|
||||
[Customer behavior analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Pain Points and Challenges
|
||||
|
||||
[Pain points analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision-Making Processes
|
||||
|
||||
[Decision-making analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Journey Mapping
|
||||
|
||||
[Customer journey analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Satisfaction Drivers
|
||||
|
||||
[Satisfaction drivers analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Demographic Profiles
|
||||
|
||||
[Demographic profiles analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Psychographic Profiles
|
||||
|
||||
[Psychographic profiles analysis with source citations]
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
Show the generated customer insights and present continue option:
|
||||
"I've completed the **customer insights analysis** for customer behavior and needs.
|
||||
|
||||
**Key Customer Findings:**
|
||||
|
||||
- Customer behavior patterns clearly identified
|
||||
- Pain points and challenges thoroughly documented
|
||||
- Decision-making processes mapped
|
||||
- Customer journey insights captured
|
||||
- Satisfaction and profile data analyzed
|
||||
|
||||
**Ready to proceed to competitive analysis?**
|
||||
[C] Continue - Save this to the document and proceed to competitive analysis
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-05-competitive-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 4.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer behavior patterns identified with current citations
|
||||
✅ Pain points and challenges clearly documented
|
||||
✅ Decision-making processes thoroughly analyzed
|
||||
✅ Customer journey insights captured and mapped
|
||||
✅ Customer satisfaction drivers identified
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer behavior patterns
|
||||
❌ Not identifying key pain points and challenges
|
||||
❌ Incomplete customer journey mapping
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## CUSTOMER RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for customer behavior studies and surveys
|
||||
- Use market research firm and industry association sources
|
||||
- Research customer experience and interaction patterns
|
||||
- Note generational and cultural customer variations
|
||||
- Research customer satisfaction methodologies
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis.
|
||||
|
||||
Remember: Always emphasize current customer data and rigorous source verification!
|
||||
@@ -1,249 +0,0 @@
|
||||
# Market Research Step 3: Customer Pain Points and Needs
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER NEEDS ANALYST, not content generator
|
||||
- 💬 FOCUS on customer pain points, challenges, and unmet needs
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after pain points content generation
|
||||
- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- Customer behavior analysis completed in previous step
|
||||
- Focus on customer pain points, challenges, and unmet needs
|
||||
- Web search capabilities with source verification are enabled
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer pain points and needs analysis with emphasis on challenges and frustrations.
|
||||
|
||||
## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Customer Pain Points Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer pain points research approach:
|
||||
"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
|
||||
|
||||
**Customer Pain Points Focus:**
|
||||
|
||||
- Customer challenges and frustrations
|
||||
- Unmet needs and unaddressed problems
|
||||
- Barriers to adoption or usage
|
||||
- Service and support pain points
|
||||
- Customer satisfaction gaps
|
||||
|
||||
**Let me search for current customer pain points insights.**"
|
||||
|
||||
### 2. Parallel Pain Points Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} customer pain points challenges"
|
||||
Search the web: "{{research_topic}} customer frustrations"
|
||||
Search the web: "{{research_topic}} unmet customer needs"
|
||||
Search the web: "{{research_topic}} customer barriers to adoption"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for customer satisfaction surveys and reports
|
||||
- Search for customer complaints and reviews
|
||||
- Research customer support and service issues
|
||||
- Analyze barriers to customer adoption
|
||||
- Study unmet needs and market gaps
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Customer challenges and frustrations
|
||||
- Unmet needs and unaddressed problems
|
||||
- Barriers to adoption or usage
|
||||
- Service and support pain points
|
||||
|
||||
**Cross-Pain Points Analysis:**
|
||||
[Identify patterns connecting different types of pain points]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Customer Pain Points Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare customer pain points analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Customer Pain Points and Needs
|
||||
|
||||
### Customer Challenges and Frustrations
|
||||
|
||||
[Customer challenges analysis with source citations]
|
||||
_Primary Frustrations: [Major customer frustrations identified]_
|
||||
_Usage Barriers: [Barriers preventing effective usage]_
|
||||
_Service Pain Points: [Customer service and support issues]_
|
||||
_Frequency Analysis: [How often these challenges occur]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Unmet Customer Needs
|
||||
|
||||
[Unmet needs analysis with source citations]
|
||||
_Critical Unmet Needs: [Most important unaddressed needs]_
|
||||
_Solution Gaps: [Opportunities to address unmet needs]_
|
||||
_Market Gaps: [Market opportunities from unmet needs]_
|
||||
_Priority Analysis: [Which needs are most critical]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Barriers to Adoption
|
||||
|
||||
[Adoption barriers analysis with source citations]
|
||||
_Price Barriers: [Cost-related barriers to adoption]_
|
||||
_Technical Barriers: [Complexity or technical barriers]_
|
||||
_Trust Barriers: [Trust and credibility issues]_
|
||||
_Convenience Barriers: [Ease of use or accessibility issues]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Service and Support Pain Points
|
||||
|
||||
[Service pain points analysis with source citations]
|
||||
_Customer Service Issues: [Common customer service problems]_
|
||||
_Support Gaps: [Areas where customer support is lacking]_
|
||||
_Communication Issues: [Communication breakdowns and frustrations]_
|
||||
_Response Time Issues: [Slow response and resolution problems]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Satisfaction Gaps
|
||||
|
||||
[Satisfaction gap analysis with source citations]
|
||||
_Expectation Gaps: [Differences between expectations and reality]_
|
||||
_Quality Gaps: [Areas where quality expectations aren't met]_
|
||||
_Value Perception Gaps: [Perceived value vs actual value]_
|
||||
_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Emotional Impact Assessment
|
||||
|
||||
[Emotional impact analysis with source citations]
|
||||
_Frustration Levels: [Customer frustration severity assessment]_
|
||||
_Loyalty Risks: [How pain points affect customer loyalty]_
|
||||
_Reputation Impact: [Impact on brand or product reputation]_
|
||||
_Customer Retention Risks: [Risk of customer loss from pain points]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Pain Point Prioritization
|
||||
|
||||
[Pain point prioritization with source citations]
|
||||
_High Priority Pain Points: [Most critical pain points to address]_
|
||||
_Medium Priority Pain Points: [Important but less critical pain points]_
|
||||
_Low Priority Pain Points: [Minor pain points with lower impact]_
|
||||
_Opportunity Mapping: [Pain points with highest solution opportunity]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
|
||||
|
||||
**Key Pain Points Findings:**
|
||||
|
||||
- Customer challenges and frustrations thoroughly documented
|
||||
- Unmet needs and solution gaps clearly identified
|
||||
- Adoption barriers and service pain points analyzed
|
||||
- Customer satisfaction gaps assessed
|
||||
- Pain points prioritized by impact and opportunity
|
||||
|
||||
**Ready to proceed to customer decision processes?**
|
||||
[C] Continue - Save this to document and proceed to decision processes analysis
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-customer-decisions.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer challenges and frustrations clearly documented
|
||||
✅ Unmet needs and solution gaps identified
|
||||
✅ Adoption barriers and service pain points analyzed
|
||||
✅ Customer satisfaction gaps assessed
|
||||
✅ Pain points prioritized by impact and opportunity
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (customer decisions)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer challenges or frustrations
|
||||
❌ Not identifying unmet needs or solution gaps
|
||||
❌ Incomplete adoption barriers analysis
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to customer decisions analysis step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## CUSTOMER PAIN POINTS RESEARCH PROTOCOLS:
|
||||
|
||||
- Research customer satisfaction surveys and reviews
|
||||
- Use customer feedback and complaint data
|
||||
- Analyze customer support and service issues
|
||||
- Study barriers to customer adoption
|
||||
- Focus on current pain point data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## PAIN POINTS ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative customer research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable pain point insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current customer pain points data with rigorous source verification!
|
||||
@@ -1,259 +0,0 @@
|
||||
# Market Research Step 4: Customer Decisions and Journey
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER DECISION ANALYST, not content generator
|
||||
- 💬 FOCUS on customer decision processes and journey mapping
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after decision processes content generation
|
||||
- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- Customer behavior and pain points analysis completed in previous steps
|
||||
- Focus on customer decision processes and journey mapping
|
||||
- Web search capabilities with source verification are enabled
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer decision processes and journey analysis with emphasis on decision factors and journey mapping.
|
||||
|
||||
## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Customer Decisions Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer decisions research approach:
|
||||
"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
|
||||
|
||||
**Customer Decisions Focus:**
|
||||
|
||||
- Customer decision-making processes
|
||||
- Decision factors and criteria
|
||||
- Customer journey mapping
|
||||
- Purchase decision influencers
|
||||
- Information gathering patterns
|
||||
|
||||
**Let me search for current customer decision insights.**"
|
||||
|
||||
### 2. Parallel Decisions Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} customer decision process"
|
||||
Search the web: "{{research_topic}} buying criteria factors"
|
||||
Search the web: "{{research_topic}} customer journey mapping"
|
||||
Search the web: "{{research_topic}} decision influencing factors"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for customer decision research studies
|
||||
- Search for buying criteria and factor analysis
|
||||
- Research customer journey mapping methodologies
|
||||
- Analyze decision influence factors and channels
|
||||
- Study information gathering and evaluation patterns
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Customer decision-making processes
|
||||
- Decision factors and criteria
|
||||
- Customer journey mapping
|
||||
- Decision influence factors
|
||||
|
||||
**Cross-Decisions Analysis:**
|
||||
[Identify patterns connecting decision factors and journey stages]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Customer Decisions Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare customer decisions analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Customer Decision Processes and Journey
|
||||
|
||||
### Customer Decision-Making Processes
|
||||
|
||||
[Decision processes analysis with source citations]
|
||||
_Decision Stages: [Key stages in customer decision making]_
|
||||
_Decision Timelines: [Timeframes for different decisions]_
|
||||
_Complexity Levels: [Decision complexity assessment]_
|
||||
_Evaluation Methods: [How customers evaluate options]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision Factors and Criteria
|
||||
|
||||
[Decision factors analysis with source citations]
|
||||
_Primary Decision Factors: [Most important factors in decisions]_
|
||||
_Secondary Decision Factors: [Supporting factors influencing decisions]_
|
||||
_Weighing Analysis: [How different factors are weighed]_
|
||||
_Evoluton Patterns: [How factors change over time]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Journey Mapping
|
||||
|
||||
[Journey mapping analysis with source citations]
|
||||
_Awareness Stage: [How customers become aware of {{research_topic}}]_
|
||||
_Consideration Stage: [Evaluation and comparison process]_
|
||||
_Decision Stage: [Final decision-making process]_
|
||||
_Purchase Stage: [Purchase execution and completion]_
|
||||
_Post-Purchase Stage: [Post-decision evaluation and behavior]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Touchpoint Analysis
|
||||
|
||||
[Touchpoint analysis with source citations]
|
||||
_Digital Touchpoints: [Online and digital interaction points]_
|
||||
_Offline Touchpoints: [Physical and in-person interaction points]_
|
||||
_Information Sources: [Where customers get information]_
|
||||
_Influence Channels: [What influences customer decisions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Information Gathering Patterns
|
||||
|
||||
[Information patterns analysis with source citations]
|
||||
_Research Methods: [How customers research options]_
|
||||
_Information Sources Trusted: [Most trusted information sources]_
|
||||
_Research Duration: [Time spent gathering information]_
|
||||
_Evaluation Criteria: [How customers evaluate information]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision Influencers
|
||||
|
||||
[Decision influencer analysis with source citations]
|
||||
_Peer Influence: [How friends and family influence decisions]_
|
||||
_Expert Influence: [How expert opinions affect decisions]_
|
||||
_Media Influence: [How media and marketing affect decisions]_
|
||||
_Social Proof Influence: [How reviews and testimonials affect decisions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Purchase Decision Factors
|
||||
|
||||
[Purchase decision factors analysis with source citations]
|
||||
_Immediate Purchase Drivers: [Factors triggering immediate purchase]_
|
||||
_Delayed Purchase Drivers: [Factors causing purchase delays]_
|
||||
_Brand Loyalty Factors: [Factors driving repeat purchases]_
|
||||
_Price Sensitivity: [How price affects purchase decisions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Decision Optimizations
|
||||
|
||||
[Decision optimization analysis with source citations]
|
||||
_Friction Reduction: [Ways to make decisions easier]_
|
||||
_Trust Building: [Building customer trust in decisions]_
|
||||
_Conversion Optimization: [Optimizing decision-to-purchase rates]_
|
||||
_Loyalty Building: [Building long-term customer relationships]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
|
||||
|
||||
**Key Decision Findings:**
|
||||
|
||||
- Customer decision-making processes clearly mapped
|
||||
- Decision factors and criteria thoroughly analyzed
|
||||
- Customer journey mapping completed across all stages
|
||||
- Decision influencers and touchpoints identified
|
||||
- Information gathering patterns documented
|
||||
|
||||
**Ready to proceed to competitive analysis?**
|
||||
[C] Continue - Save this to document and proceed to competitive analysis
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Load: `./step-05-competitive-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer decision-making processes clearly mapped
|
||||
✅ Decision factors and criteria thoroughly analyzed
|
||||
✅ Customer journey mapping completed across all stages
|
||||
✅ Decision influencers and touchpoints identified
|
||||
✅ Information gathering patterns documented
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (competitive analysis)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical decision-making process stages
|
||||
❌ Not identifying key decision factors
|
||||
❌ Incomplete customer journey mapping
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to competitive analysis step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## CUSTOMER DECISIONS RESEARCH PROTOCOLS:
|
||||
|
||||
- Research customer decision studies and psychology
|
||||
- Use customer journey mapping methodologies
|
||||
- Analyze buying criteria and decision factors
|
||||
- Study decision influence and touchpoint analysis
|
||||
- Focus on current decision data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## DECISION ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative customer decision research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable decision insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current customer decision data with rigorous source verification!
|
||||
@@ -1,177 +0,0 @@
|
||||
# Market Research Step 5: Competitive Analysis
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
|
||||
- 💬 FOCUS on competitive landscape and market positioning
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after competitive analysis content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- Focus on competitive landscape and market positioning analysis
|
||||
- Web search capabilities with source verification are enabled
|
||||
- May need to search for specific competitor information
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive competitive analysis with emphasis on market positioning.
|
||||
|
||||
## COMPETITIVE ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Competitive Analysis
|
||||
|
||||
Start with competitive research approach:
|
||||
"Now I'll conduct **competitive analysis** to understand the competitive landscape.
|
||||
|
||||
**Competitive Analysis Focus:**
|
||||
|
||||
- Key players and market share
|
||||
- Competitive positioning strategies
|
||||
- Strengths and weaknesses analysis
|
||||
- Market differentiation opportunities
|
||||
- Competitive threats and challenges
|
||||
|
||||
**Let me search for current competitive information.**"
|
||||
|
||||
### 2. Generate Competitive Analysis Content
|
||||
|
||||
Prepare competitive analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Competitive Landscape
|
||||
|
||||
### Key Market Players
|
||||
|
||||
[Key players analysis with market share data]
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Share Analysis
|
||||
|
||||
[Market share analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Positioning
|
||||
|
||||
[Positioning analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Strengths and Weaknesses
|
||||
|
||||
[SWOT analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Differentiation
|
||||
|
||||
[Differentiation analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Threats
|
||||
|
||||
[Threats analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Opportunities
|
||||
|
||||
[Competitive opportunities analysis with source citations]
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 3. Present Analysis and Complete Option
|
||||
|
||||
Show the generated competitive analysis and present complete option:
|
||||
"I've completed the **competitive analysis** for the competitive landscape.
|
||||
|
||||
**Key Competitive Findings:**
|
||||
|
||||
- Key market players and market share identified
|
||||
- Competitive positioning strategies mapped
|
||||
- Strengths and weaknesses thoroughly analyzed
|
||||
- Market differentiation opportunities identified
|
||||
- Competitive threats and challenges documented
|
||||
|
||||
**Ready to complete the market research?**
|
||||
[C] Complete Research - Save final document and conclude
|
||||
|
||||
### 4. Handle Complete Selection
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Complete the market research workflow
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 2.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Key market players identified
|
||||
✅ Market share analysis completed with source verification
|
||||
✅ Competitive positioning strategies clearly mapped
|
||||
✅ Strengths and weaknesses thoroughly analyzed
|
||||
✅ Market differentiation opportunities identified
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
✅ Market research workflow completed successfully
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing key market players or market share data
|
||||
❌ Incomplete competitive positioning analysis
|
||||
❌ Not identifying market differentiation opportunities
|
||||
❌ Not presenting completion option for research workflow
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## COMPETITIVE RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for industry reports and competitive intelligence
|
||||
- Use competitor company websites and annual reports
|
||||
- Research market research firm competitive analyses
|
||||
- Note competitive advantages and disadvantages
|
||||
- Search for recent market developments and disruptions
|
||||
|
||||
## MARKET RESEARCH COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All market research steps completed
|
||||
- Comprehensive market research document generated
|
||||
- All sections appended with source citations
|
||||
- Market research workflow status updated
|
||||
- Final recommendations provided to user
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
Market research workflow complete. User may:
|
||||
|
||||
- Use market research to inform product development strategies
|
||||
- Conduct additional competitive research on specific companies
|
||||
- Combine market research with other research types for comprehensive insights
|
||||
|
||||
Congratulations on completing comprehensive market research! 🎉
|
||||
@@ -1,475 +0,0 @@
|
||||
# Market Research Step 6: Research Completion
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on strategic recommendations and actionable insights
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after completion content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - comprehensive market analysis
|
||||
- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
|
||||
- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis)
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final synthesis step producing the complete market research document
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Produce a comprehensive, authoritative market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive market research.
|
||||
|
||||
## MARKET RESEARCH COMPLETION SEQUENCE:
|
||||
|
||||
### 1. Begin Strategic Synthesis
|
||||
|
||||
Start with strategic synthesis approach:
|
||||
"Now I'll complete our market research with **strategic synthesis and recommendations** .
|
||||
|
||||
**Strategic Synthesis Focus:**
|
||||
|
||||
- Integrated insights from market, customer, and competitive analysis
|
||||
- Strategic recommendations based on research findings
|
||||
- Market entry or expansion strategies
|
||||
- Risk assessment and mitigation approaches
|
||||
- Actionable next steps and implementation guidance
|
||||
|
||||
**Let me search for current strategic insights and best practices.**"
|
||||
|
||||
### 2. Web Search for Market Entry Strategies
|
||||
|
||||
Search for current market strategies:
|
||||
Search the web: "market entry strategies best practices"
|
||||
|
||||
**Strategy focus:**
|
||||
|
||||
- Market entry timing and approaches
|
||||
- Go-to-market strategies and frameworks
|
||||
- Market positioning and differentiation tactics
|
||||
- Customer acquisition and growth strategies
|
||||
|
||||
### 3. Web Search for Risk Assessment
|
||||
|
||||
Search for current risk approaches:
|
||||
Search the web: "market research risk assessment frameworks"
|
||||
|
||||
**Risk focus:**
|
||||
|
||||
- Market risks and uncertainty management
|
||||
- Competitive threats and mitigation strategies
|
||||
- Regulatory and compliance risks
|
||||
- Economic and market volatility considerations
|
||||
|
||||
### 4. Generate Complete Market Research Document
|
||||
|
||||
Prepare comprehensive market research document with full structure:
|
||||
|
||||
#### Complete Document Structure:
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]: Comprehensive {{research_topic}} Market Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Brief compelling overview of key market findings and strategic implications]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- Market Research Introduction and Methodology
|
||||
- {{research_topic}} Market Analysis and Dynamics
|
||||
- Customer Insights and Behavior Analysis
|
||||
- Competitive Landscape and Positioning
|
||||
- Strategic Market Recommendations
|
||||
- Market Entry and Growth Strategies
|
||||
- Risk Assessment and Mitigation
|
||||
- Implementation Roadmap and Success Metrics
|
||||
- Future Market Outlook and Opportunities
|
||||
- Market Research Methodology and Source Documentation
|
||||
- Market Research Appendices and Additional Resources
|
||||
|
||||
## 1. Market Research Introduction and Methodology
|
||||
|
||||
### Market Research Significance
|
||||
|
||||
**Compelling market narrative about why {{research_topic}} research is critical now**
|
||||
_Market Importance: [Strategic market significance with up-to-date context]_
|
||||
_Business Impact: [Business implications of market research]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Research Methodology
|
||||
|
||||
[Comprehensive description of market research approach including:]
|
||||
|
||||
- **Market Scope**: [Comprehensive market coverage areas]
|
||||
- **Data Sources**: [Authoritative market sources and verification approach]
|
||||
- **Analysis Framework**: [Structured market analysis methodology]
|
||||
- **Time Period**: [current focus and market evolution context]
|
||||
- **Geographic Coverage**: [Regional/global market scope]
|
||||
|
||||
### Market Research Goals and Objectives
|
||||
|
||||
**Original Market Goals:** {{research_goals}}
|
||||
|
||||
**Achieved Market Objectives:**
|
||||
|
||||
- [Market Goal 1 achievement with supporting evidence]
|
||||
- [Market Goal 2 achievement with supporting evidence]
|
||||
- [Additional market insights discovered during research]
|
||||
|
||||
## 2. {{research_topic}} Market Analysis and Dynamics
|
||||
|
||||
### Market Size and Growth Projections
|
||||
|
||||
_[Comprehensive market analysis]_
|
||||
_Market Size: [Current market valuation and size]_
|
||||
_Growth Rate: [CAGR and market growth projections]_
|
||||
_Market Drivers: [Key factors driving market growth]_
|
||||
_Market Segments: [Detailed market segmentation analysis]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Trends and Dynamics
|
||||
|
||||
[Current market trends analysis]
|
||||
_Emerging Trends: [Key market trends and their implications]_
|
||||
_Market Dynamics: [Forces shaping market evolution]_
|
||||
_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Pricing and Business Model Analysis
|
||||
|
||||
[Comprehensive pricing and business model analysis]
|
||||
_Pricing Strategies: [Current pricing approaches and models]_
|
||||
_Business Model Evolution: [Emerging and successful business models]_
|
||||
_Value Proposition Analysis: [Customer value proposition assessment]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Customer Insights and Behavior Analysis
|
||||
|
||||
### Customer Behavior Patterns
|
||||
|
||||
[Customer insights analysis with current context]
|
||||
_Behavior Patterns: [Key customer behavior trends and patterns]_
|
||||
_Customer Journey: [Complete customer journey mapping]_
|
||||
_Decision Factors: [Factors influencing customer decisions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Pain Points and Needs
|
||||
|
||||
[Comprehensive customer pain point analysis]
|
||||
_Pain Points: [Key customer challenges and frustrations]_
|
||||
_Unmet Needs: [Unsolved customer needs and opportunities]_
|
||||
_Customer Expectations: [Current customer expectations and requirements]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Segmentation and Targeting
|
||||
|
||||
[Detailed customer segmentation analysis]
|
||||
_Customer Segments: [Detailed customer segment profiles]_
|
||||
_Target Market Analysis: [Most attractive customer segments]_
|
||||
_Segment-specific Strategies: [Tailored approaches for key segments]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Competitive Landscape and Positioning
|
||||
|
||||
### Competitive Analysis
|
||||
|
||||
[Comprehensive competitive analysis]
|
||||
_Market Leaders: [Dominant competitors and their strategies]_
|
||||
_Emerging Competitors: [New entrants and innovative approaches]_
|
||||
_Competitive Advantages: [Key differentiators and competitive advantages]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Positioning Strategies
|
||||
|
||||
[Strategic positioning analysis]
|
||||
_Positioning Opportunities: [Opportunities for market differentiation]_
|
||||
_Competitive Gaps: [Unserved market needs and opportunities]_
|
||||
_Positioning Framework: [Recommended positioning approach]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Strategic Market Recommendations
|
||||
|
||||
### Market Opportunity Assessment
|
||||
|
||||
[Strategic market opportunities analysis]
|
||||
_High-Value Opportunities: [Most attractive market opportunities]_
|
||||
_Market Entry Timing: [Optimal timing for market entry or expansion]_
|
||||
_Growth Strategies: [Recommended approaches for market growth]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
[Comprehensive strategic recommendations]
|
||||
_Market Entry Strategy: [Recommended approach for market entry/expansion]_
|
||||
_Competitive Strategy: [Recommended competitive positioning and approach]_
|
||||
_Customer Acquisition Strategy: [Recommended customer acquisition approach]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Market Entry and Growth Strategies
|
||||
|
||||
### Go-to-Market Strategy
|
||||
|
||||
[Comprehensive go-to-market approach]
|
||||
_Market Entry Approach: [Recommended market entry strategy and tactics]_
|
||||
_Channel Strategy: [Optimal channels for market reach and customer acquisition]_
|
||||
_Partnership Strategy: [Strategic partnership and collaboration opportunities]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Growth and Scaling Strategy
|
||||
|
||||
[Market growth and scaling analysis]
|
||||
_Growth Phases: [Recommended phased approach to market growth]_
|
||||
_Scaling Considerations: [Key factors for successful market scaling]_
|
||||
_Expansion Opportunities: [Opportunities for geographic or segment expansion]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Risk Assessment and Mitigation
|
||||
|
||||
### Market Risk Analysis
|
||||
|
||||
[Comprehensive market risk assessment]
|
||||
_Market Risks: [Key market-related risks and uncertainties]_
|
||||
_Competitive Risks: [Competitive threats and mitigation strategies]_
|
||||
_Regulatory Risks: [Regulatory and compliance considerations]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Mitigation Strategies
|
||||
|
||||
[Risk mitigation and contingency planning]
|
||||
_Risk Mitigation Approaches: [Strategies for managing identified risks]_
|
||||
_Contingency Planning: [Backup plans and alternative approaches]_
|
||||
_Market Sensitivity Analysis: [Impact of market changes on strategy]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Implementation Roadmap and Success Metrics
|
||||
|
||||
### Implementation Framework
|
||||
|
||||
[Comprehensive implementation guidance]
|
||||
_Implementation Timeline: [Recommended phased implementation approach]_
|
||||
_Required Resources: [Key resources and capabilities needed]_
|
||||
_Implementation Milestones: [Key milestones and success criteria]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Success Metrics and KPIs
|
||||
|
||||
[Comprehensive success measurement framework]
|
||||
_Key Performance Indicators: [Critical metrics for measuring success]_
|
||||
_Monitoring and Reporting: [Approach for tracking and reporting progress]_
|
||||
_Success Criteria: [Clear criteria for determining success]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Future Market Outlook and Opportunities
|
||||
|
||||
### Future Market Trends
|
||||
|
||||
[Forward-looking market analysis]
|
||||
_Near-term Market Evolution: [1-2 year market development expectations]_
|
||||
_Medium-term Market Trends: [3-5 year expected market developments]_
|
||||
_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Opportunities
|
||||
|
||||
[Market opportunity analysis and recommendations]
|
||||
_Emerging Opportunities: [New market opportunities and their potential]_
|
||||
_Innovation Opportunities: [Areas for market innovation and differentiation]_
|
||||
_Strategic Market Investments: [Recommended market investments and priorities]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 10. Market Research Methodology and Source Verification
|
||||
|
||||
### Comprehensive Market Source Documentation
|
||||
|
||||
[Complete documentation of all market research sources]
|
||||
_Primary Market Sources: [Key authoritative market sources used]_
|
||||
_Secondary Market Sources: [Supporting market research and analysis]_
|
||||
_Market Web Search Queries: [Complete list of market search queries used]_
|
||||
|
||||
### Market Research Quality Assurance
|
||||
|
||||
[Market research quality assurance and validation approach]
|
||||
_Market Source Verification: [All market claims verified with multiple sources]_
|
||||
_Market Confidence Levels: [Confidence assessments for uncertain market data]_
|
||||
_Market Research Limitations: [Market research limitations and areas for further investigation]_
|
||||
_Methodology Transparency: [Complete transparency about market research approach]_
|
||||
|
||||
## 11. Market Research Appendices and Additional Resources
|
||||
|
||||
### Detailed Market Data Tables
|
||||
|
||||
[Comprehensive market data tables supporting research findings]
|
||||
_Market Size Data: [Detailed market size and growth data tables]_
|
||||
_Customer Analysis Data: [Detailed customer behavior and segmentation data]_
|
||||
_Competitive Analysis Data: [Detailed competitor comparison and positioning data]_
|
||||
|
||||
### Market Resources and References
|
||||
|
||||
[Valuable market resources for continued research and implementation]
|
||||
_Market Research Reports: [Authoritative market research reports and publications]_
|
||||
_Industry Associations: [Key industry organizations and market resources]_
|
||||
_Market Analysis Tools: [Tools and resources for ongoing market analysis]_
|
||||
|
||||
---
|
||||
|
||||
## Market Research Conclusion
|
||||
|
||||
### Summary of Key Market Findings
|
||||
|
||||
[Comprehensive summary of the most important market research findings]
|
||||
|
||||
### Strategic Market Impact Assessment
|
||||
|
||||
[Assessment of market implications for {{research_topic}}]
|
||||
|
||||
### Next Steps Market Recommendations
|
||||
|
||||
[Specific next steps for leveraging this market research]
|
||||
|
||||
---
|
||||
|
||||
**Market Research Completion Date:** {{date}}
|
||||
**Research Period:** current comprehensive market analysis
|
||||
**Document Length:** As needed for comprehensive market coverage
|
||||
**Source Verification:** All market facts cited with current sources
|
||||
**Market Confidence Level:** High - based on multiple authoritative market sources
|
||||
|
||||
_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._
|
||||
```
|
||||
|
||||
### 5. Present Complete Market Research Document and Final Option
|
||||
|
||||
**Market Research Document Completion Presentation:**
|
||||
|
||||
"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
|
||||
|
||||
**Document Features:**
|
||||
|
||||
- **Compelling Market Introduction**: Engaging opening that establishes market research significance
|
||||
- **Comprehensive Market TOC**: Complete navigation structure for market reference
|
||||
- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Market Summary**: Key market findings and strategic implications highlighted
|
||||
- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research
|
||||
- **Complete Market Source Citations**: Every market claim verified with current sources
|
||||
|
||||
**Market Research Completeness:**
|
||||
|
||||
- Market analysis and dynamics fully documented
|
||||
- Customer insights and behavior analysis comprehensively covered
|
||||
- Competitive landscape and positioning detailed
|
||||
- Strategic market recommendations and implementation guidance provided
|
||||
|
||||
**Document Standards Met:**
|
||||
|
||||
- Exhaustive market research with no critical gaps
|
||||
- Professional market structure and compelling narrative
|
||||
- As long as needed for comprehensive market coverage
|
||||
- Multiple independent sources for all market claims
|
||||
- current market data throughout with proper citations
|
||||
|
||||
**Ready to complete this comprehensive market research document?**
|
||||
[C] Complete Research - Save final comprehensive market research document
|
||||
|
||||
### 6. Handle Complete Selection
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Complete the market research workflow
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 4.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Compelling market introduction with research significance
|
||||
✅ Comprehensive market table of contents with complete document structure
|
||||
✅ Exhaustive market research coverage across all market aspects
|
||||
✅ Executive market summary with key findings and strategic implications
|
||||
✅ Strategic market recommendations grounded in comprehensive research
|
||||
✅ Complete market source verification with current citations
|
||||
✅ Professional market document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Market research workflow completed with comprehensive document
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not producing compelling market introduction
|
||||
❌ Missing comprehensive market table of contents
|
||||
❌ Incomplete market research coverage across market aspects
|
||||
❌ Not providing executive market summary with key findings
|
||||
❌ Missing strategic market recommendations based on research
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing market document without professional structure
|
||||
❌ Not presenting completion option for final market document
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## STRATEGIC RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for current market strategy frameworks and best practices
|
||||
- Research successful market entry cases and approaches
|
||||
- Identify risk management methodologies and frameworks
|
||||
- Research implementation planning and execution strategies
|
||||
- Consider market timing and readiness factors
|
||||
|
||||
## COMPREHENSIVE MARKET DOCUMENT STANDARDS:
|
||||
|
||||
This step ensures the final market research document:
|
||||
|
||||
- Serves as an authoritative market reference on {{research_topic}}
|
||||
- Provides strategic market insights for informed decision-making
|
||||
- Includes comprehensive market coverage with no gaps
|
||||
- Maintains rigorous market source verification standards
|
||||
- Delivers strategic market insights and actionable recommendations
|
||||
- Meets professional market research document quality standards
|
||||
|
||||
## MARKET RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All market research steps completed (1-4)
|
||||
- Comprehensive market research document generated
|
||||
- Professional market document structure with intro, TOC, and summary
|
||||
- All market sections appended with source citations
|
||||
- Market research workflow status updated to complete
|
||||
- Final comprehensive market research document delivered to user
|
||||
|
||||
## FINAL MARKET DELIVERABLE:
|
||||
|
||||
Complete authoritative market research document on {{research_topic}} that:
|
||||
|
||||
- Establishes professional market credibility through comprehensive research
|
||||
- Provides strategic market insights for informed decision-making
|
||||
- Serves as market reference document for continued use
|
||||
- Maintains highest market research quality standards with current verification
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
Comprehensive market research workflow complete. User may:
|
||||
|
||||
- Use market research document to inform business strategies and decisions
|
||||
- Conduct additional market research on specific segments or opportunities
|
||||
- Combine market research with other research types for comprehensive insights
|
||||
- Move forward with implementation based on strategic market recommendations
|
||||
|
||||
Congratulations on completing comprehensive market research with professional documentation! 🎉
|
||||
@@ -1,29 +0,0 @@
|
||||
---
|
||||
stepsCompleted: []
|
||||
inputDocuments: []
|
||||
workflowType: 'research'
|
||||
lastStep: 1
|
||||
research_type: '{{research_type}}'
|
||||
research_topic: '{{research_topic}}'
|
||||
research_goals: '{{research_goals}}'
|
||||
user_name: '{{user_name}}'
|
||||
date: '{{date}}'
|
||||
web_research_enabled: true
|
||||
source_verification: true
|
||||
---
|
||||
|
||||
# Research Report: {{research_type}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Author:** {{user_name}}
|
||||
**Research Type:** {{research_type}}
|
||||
|
||||
---
|
||||
|
||||
## Research Overview
|
||||
|
||||
[Research overview and methodology will be appended here]
|
||||
|
||||
---
|
||||
|
||||
<!-- Content will be appended sequentially through research workflow steps -->
|
||||
@@ -1,137 +0,0 @@
|
||||
# Technical Research Step 1: Technical Research Scope Confirmation
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user confirmation
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ FOCUS EXCLUSIVELY on confirming technical research scope and approach
|
||||
- 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator
|
||||
- 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals
|
||||
- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- ⚠️ Present [C] continue option after scope confirmation
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Research type = "technical" is already set
|
||||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on technical architecture and implementation research
|
||||
- Web search is required to verify and supplement your knowledge with current facts
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Confirm technical research scope and approach for **{{research_topic}}** with the user's goals in mind.
|
||||
|
||||
## TECHNICAL SCOPE CONFIRMATION:
|
||||
|
||||
### 1. Begin Scope Confirmation
|
||||
|
||||
Start with technical scope understanding:
|
||||
"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
|
||||
|
||||
**Technical Research Scope:**
|
||||
|
||||
- **Architecture Analysis**: System design patterns, frameworks, and architectural decisions
|
||||
- **Implementation Approaches**: Development methodologies, coding patterns, and best practices
|
||||
- **Technology Stack**: Languages, frameworks, tools, and platforms relevant to {{research_topic}}
|
||||
- **Integration Patterns**: APIs, communication protocols, and system interoperability
|
||||
- **Performance Considerations**: Scalability, optimization, and performance patterns
|
||||
|
||||
**Research Approach:**
|
||||
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence levels for uncertain technical information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
||||
### 2. Scope Confirmation
|
||||
|
||||
Present clear scope confirmation:
|
||||
"**Technical Research Scope Confirmation:**
|
||||
|
||||
For **{{research_topic}}**, I will research:
|
||||
|
||||
✅ **Architecture Analysis** - design patterns, frameworks, system architecture
|
||||
✅ **Implementation Approaches** - development methodologies, coding patterns
|
||||
✅ **Technology Stack** - languages, frameworks, tools, platforms
|
||||
✅ **Integration Patterns** - APIs, protocols, interoperability
|
||||
✅ **Performance Considerations** - scalability, optimization, patterns
|
||||
|
||||
**All claims verified against current public sources.**
|
||||
|
||||
**Does this technical research scope and approach align with your goals?**
|
||||
[C] Continue - Begin technical research with this scope
|
||||
|
||||
### 3. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-technical-overview.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append scope confirmation:
|
||||
|
||||
```markdown
|
||||
## Technical Research Scope Confirmation
|
||||
|
||||
**Research Topic:** {{research_topic}}
|
||||
**Research Goals:** {{research_goals}}
|
||||
|
||||
**Technical Research Scope:**
|
||||
|
||||
- Architecture Analysis - design patterns, frameworks, system architecture
|
||||
- Implementation Approaches - development methodologies, coding patterns
|
||||
- Technology Stack - languages, frameworks, tools, platforms
|
||||
- Integration Patterns - APIs, protocols, interoperability
|
||||
- Performance Considerations - scalability, optimization, patterns
|
||||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence level framework for uncertain information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
||||
**Scope Confirmed:** {{date}}
|
||||
```
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Technical research scope clearly confirmed with user
|
||||
✅ All technical analysis areas identified and explained
|
||||
✅ Research methodology emphasized
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Scope confirmation documented when user proceeds
|
||||
✅ Proper routing to next technical research step
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not clearly confirming technical research scope with user
|
||||
❌ Missing critical technical analysis areas
|
||||
❌ Not explaining that web search is required for current facts
|
||||
❌ Not presenting [C] continue option
|
||||
❌ Proceeding without user scope confirmation
|
||||
❌ Not routing to next technical research step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-technical-overview.md` to begin technology stack analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!
|
||||
@@ -1,239 +0,0 @@
|
||||
# Technical Research Step 2: Technology Stack Analysis
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
|
||||
- 💬 FOCUS on languages, frameworks, tools, and platforms
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after technology stack content generation
|
||||
- 📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from step-01 are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on languages, frameworks, tools, and platforms
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms. Search the web to verify and supplement current facts.
|
||||
|
||||
## TECHNOLOGY STACK ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Technology Stack Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
|
||||
|
||||
Start with technology stack research approach:
|
||||
"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
|
||||
|
||||
**Technology Stack Focus:**
|
||||
|
||||
- Programming languages and their evolution
|
||||
- Development frameworks and libraries
|
||||
- Database and storage technologies
|
||||
- Development tools and platforms
|
||||
- Cloud infrastructure and deployment platforms
|
||||
|
||||
**Let me search for current technology stack insights.**"
|
||||
|
||||
### 2. Parallel Technology Stack Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} programming languages frameworks"
|
||||
Search the web: "{{research_topic}} development tools platforms"
|
||||
Search the web: "{{research_topic}} database storage technologies"
|
||||
Search the web: "{{research_topic}} cloud infrastructure platforms"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent technology trend reports and developer surveys
|
||||
- Search for technology documentation and best practices
|
||||
- Research open-source projects and their technology choices
|
||||
- Analyze technology adoption patterns and migration trends
|
||||
- Study platform and tool evolution in the domain
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Programming languages and frameworks analysis
|
||||
- Development tools and platforms evaluation
|
||||
- Database and storage technologies assessment
|
||||
- Cloud infrastructure and deployment platform analysis
|
||||
|
||||
**Cross-Technology Analysis:**
|
||||
[Identify patterns connecting language choices, frameworks, and platform decisions]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Technology Stack Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare technology stack analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Technology Stack Analysis
|
||||
|
||||
### Programming Languages
|
||||
|
||||
[Programming languages analysis with source citations]
|
||||
_Popular Languages: [Most widely used languages for {{research_topic}}]_
|
||||
_Emerging Languages: [Growing languages gaining adoption]_
|
||||
_Language Evolution: [How language preferences are changing]_
|
||||
_Performance Characteristics: [Language performance and suitability]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Frameworks and Libraries
|
||||
|
||||
[Frameworks analysis with source citations]
|
||||
_Major Frameworks: [Dominant frameworks and their use cases]_
|
||||
_Micro-frameworks: [Lightweight options and specialized libraries]_
|
||||
_Evolution Trends: [How frameworks are evolving and changing]_
|
||||
_Ecosystem Maturity: [Library availability and community support]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Database and Storage Technologies
|
||||
|
||||
[Database analysis with source citations]
|
||||
_Relational Databases: [Traditional SQL databases and their evolution]_
|
||||
_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
|
||||
_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
|
||||
_Data Warehousing: [Analytics and big data storage solutions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Tools and Platforms
|
||||
|
||||
[Tools and platforms analysis with source citations]
|
||||
_IDE and Editors: [Development environments and their evolution]_
|
||||
_Version Control: [Git and related development tools]_
|
||||
_Build Systems: [Compilation, packaging, and automation tools]_
|
||||
_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Cloud Infrastructure and Deployment
|
||||
|
||||
[Cloud platforms analysis with source citations]
|
||||
_Major Cloud Providers: [AWS, Azure, GCP and their services]_
|
||||
_Container Technologies: [Docker, Kubernetes, and orchestration]_
|
||||
_Serverless Platforms: [FaaS and event-driven computing]_
|
||||
_CDN and Edge Computing: [Content delivery and distributed computing]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Trends
|
||||
|
||||
[Adoption trends analysis with source citations]
|
||||
_Migration Patterns: [How technology choices are evolving]_
|
||||
_Emerging Technologies: [New technologies gaining traction]_
|
||||
_Legacy Technology: [Older technologies being phased out]_
|
||||
_Community Trends: [Developer preferences and open-source adoption]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
|
||||
|
||||
**Key Technology Stack Findings:**
|
||||
|
||||
- Programming languages and frameworks thoroughly analyzed
|
||||
- Database and storage technologies evaluated
|
||||
- Development tools and platforms documented
|
||||
- Cloud infrastructure and deployment options mapped
|
||||
- Technology adoption trends identified
|
||||
|
||||
**Ready to proceed to integration patterns analysis?**
|
||||
[C] Continue - Save this to document and proceed to integration patterns
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-integration-patterns.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Programming languages and frameworks thoroughly analyzed
|
||||
✅ Database and storage technologies evaluated
|
||||
✅ Development tools and platforms documented
|
||||
✅ Cloud infrastructure and deployment options mapped
|
||||
✅ Technology adoption trends identified
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (integration patterns)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical programming languages or frameworks
|
||||
❌ Incomplete database and storage technology analysis
|
||||
❌ Not identifying development tools and platforms
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to integration patterns step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## TECHNOLOGY STACK RESEARCH PROTOCOLS:
|
||||
|
||||
- Research technology trend reports and developer surveys
|
||||
- Use technology documentation and best practices guides
|
||||
- Analyze open-source projects and their technology choices
|
||||
- Study technology adoption patterns and migration trends
|
||||
- Focus on current technology data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## TECHNOLOGY STACK ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative technology research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable technology insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current technology data with rigorous source verification!
|
||||
@@ -1,248 +0,0 @@
|
||||
# Technical Research Step 3: Integration Patterns
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator
|
||||
- 💬 FOCUS on APIs, protocols, and system interoperability
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after integration patterns content generation
|
||||
- 📝 WRITE INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on APIs, protocols, and system interoperability
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability. Search the web to verify and supplement current facts.
|
||||
|
||||
## INTEGRATION PATTERNS ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Integration Patterns Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
|
||||
|
||||
Start with integration patterns research approach:
|
||||
"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
|
||||
|
||||
**Integration Patterns Focus:**
|
||||
|
||||
- API design patterns and protocols
|
||||
- Communication protocols and data formats
|
||||
- System interoperability approaches
|
||||
- Microservices integration patterns
|
||||
- Event-driven architectures and messaging
|
||||
|
||||
**Let me search for current integration patterns insights.**"
|
||||
|
||||
### 2. Parallel Integration Patterns Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} API design patterns protocols"
|
||||
Search the web: "{{research_topic}} communication protocols data formats"
|
||||
Search the web: "{{research_topic}} system interoperability integration"
|
||||
Search the web: "{{research_topic}} microservices integration patterns"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent API design guides and best practices
|
||||
- Search for communication protocol documentation and standards
|
||||
- Research integration platform and middleware solutions
|
||||
- Analyze microservices architecture patterns and approaches
|
||||
- Study event-driven systems and messaging patterns
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- API design patterns and protocols analysis
|
||||
- Communication protocols and data formats evaluation
|
||||
- System interoperability approaches assessment
|
||||
- Microservices integration patterns documentation
|
||||
|
||||
**Cross-Integration Analysis:**
|
||||
[Identify patterns connecting API choices, communication protocols, and system design]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Integration Patterns Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare integration patterns analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Integration Patterns Analysis
|
||||
|
||||
### API Design Patterns
|
||||
|
||||
[API design patterns analysis with source citations]
|
||||
_RESTful APIs: [REST principles and best practices for {{research_topic}}]_
|
||||
_GraphQL APIs: [GraphQL adoption and implementation patterns]_
|
||||
_RPC and gRPC: [High-performance API communication patterns]_
|
||||
_Webhook Patterns: [Event-driven API integration approaches]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Communication Protocols
|
||||
|
||||
[Communication protocols analysis with source citations]
|
||||
_HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_
|
||||
_WebSocket Protocols: [Real-time communication and persistent connections]_
|
||||
_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_
|
||||
_grpc and Protocol Buffers: [High-performance binary communication protocols]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Formats and Standards
|
||||
|
||||
[Data formats analysis with source citations]
|
||||
_JSON and XML: [Structured data exchange formats and their evolution]_
|
||||
_Protobuf and MessagePack: [Efficient binary serialization formats]_
|
||||
_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_
|
||||
_Custom Data Formats: [Domain-specific data exchange standards]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Interoperability Approaches
|
||||
|
||||
[Interoperability analysis with source citations]
|
||||
_Point-to-Point Integration: [Direct system-to-system communication patterns]_
|
||||
_API Gateway Patterns: [Centralized API management and routing]_
|
||||
_Service Mesh: [Service-to-service communication and observability]_
|
||||
_Enterprise Service Bus: [Traditional enterprise integration patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Microservices Integration Patterns
|
||||
|
||||
[Microservices integration analysis with source citations]
|
||||
_API Gateway Pattern: [External API management and routing]_
|
||||
_Service Discovery: [Dynamic service registration and discovery]_
|
||||
_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_
|
||||
_Saga Pattern: [Distributed transaction management]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Event-Driven Integration
|
||||
|
||||
[Event-driven analysis with source citations]
|
||||
_Publish-Subscribe Patterns: [Event broadcasting and subscription models]_
|
||||
_Event Sourcing: [Event-based state management and persistence]_
|
||||
_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_
|
||||
_CQRS Patterns: [Command Query Responsibility Segregation]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration Security Patterns
|
||||
|
||||
[Security patterns analysis with source citations]
|
||||
_OAuth 2.0 and JWT: [API authentication and authorization patterns]_
|
||||
_API Key Management: [Secure API access and key rotation]_
|
||||
_Mutual TLS: [Certificate-based service authentication]_
|
||||
_Data Encryption: [Secure data transmission and storage]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
|
||||
|
||||
**Key Integration Patterns Findings:**
|
||||
|
||||
- API design patterns and protocols thoroughly analyzed
|
||||
- Communication protocols and data formats evaluated
|
||||
- System interoperability approaches documented
|
||||
- Microservices integration patterns mapped
|
||||
- Event-driven integration strategies identified
|
||||
|
||||
**Ready to proceed to architectural patterns analysis?**
|
||||
[C] Continue - Save this to document and proceed to architectural patterns
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-architectural-patterns.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ API design patterns and protocols thoroughly analyzed
|
||||
✅ Communication protocols and data formats evaluated
|
||||
✅ System interoperability approaches documented
|
||||
✅ Microservices integration patterns mapped
|
||||
✅ Event-driven integration strategies identified
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (architectural patterns)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical API design patterns or protocols
|
||||
❌ Incomplete communication protocols analysis
|
||||
❌ Not identifying system interoperability approaches
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to architectural patterns step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## INTEGRATION PATTERNS RESEARCH PROTOCOLS:
|
||||
|
||||
- Research API design guides and best practices documentation
|
||||
- Use communication protocol specifications and standards
|
||||
- Analyze integration platform and middleware solutions
|
||||
- Study microservices architecture patterns and case studies
|
||||
- Focus on current integration data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## INTEGRATION PATTERNS ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative integration research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable integration insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current integration data with rigorous source verification!
|
||||
@@ -1,202 +0,0 @@
|
||||
# Technical Research Step 4: Architectural Patterns
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
|
||||
- 💬 FOCUS on architectural patterns and design decisions
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after architectural patterns content generation
|
||||
- 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on architectural patterns and design decisions
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive architectural patterns analysis with emphasis on design decisions and implementation approaches for {{research_topic}}.
|
||||
|
||||
## ARCHITECTURAL PATTERNS SEQUENCE:
|
||||
|
||||
### 1. Begin Architectural Patterns Analysis
|
||||
|
||||
Start with architectural research approach:
|
||||
"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
|
||||
|
||||
**Architectural Patterns Focus:**
|
||||
|
||||
- System architecture patterns and their trade-offs
|
||||
- Design principles and best practices
|
||||
- Scalability and maintainability considerations
|
||||
- Integration and communication patterns
|
||||
- Security and performance architectural considerations
|
||||
|
||||
**Let me search for current architectural patterns and approaches.**"
|
||||
|
||||
### 2. Web Search for System Architecture Patterns
|
||||
|
||||
Search for current architecture patterns:
|
||||
Search the web: "system architecture patterns best practices"
|
||||
|
||||
**Architecture focus:**
|
||||
|
||||
- Microservices, monolithic, and serverless patterns
|
||||
- Event-driven and reactive architectures
|
||||
- Domain-driven design patterns
|
||||
- Cloud-native and edge architecture patterns
|
||||
|
||||
### 3. Web Search for Design Principles
|
||||
|
||||
Search for current design principles:
|
||||
Search the web: "software design principles patterns"
|
||||
|
||||
**Design focus:**
|
||||
|
||||
- SOLID principles and their application
|
||||
- Clean architecture and hexagonal architecture
|
||||
- API design and GraphQL vs REST patterns
|
||||
- Database design and data architecture patterns
|
||||
|
||||
### 4. Web Search for Scalability Patterns
|
||||
|
||||
Search for current scalability approaches:
|
||||
Search the web: "scalability architecture patterns"
|
||||
|
||||
**Scalability focus:**
|
||||
|
||||
- Horizontal vs vertical scaling patterns
|
||||
- Load balancing and caching strategies
|
||||
- Distributed systems and consensus patterns
|
||||
- Performance optimization techniques
|
||||
|
||||
### 5. Generate Architectural Patterns Content
|
||||
|
||||
Prepare architectural analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Architectural Patterns and Design
|
||||
|
||||
### System Architecture Patterns
|
||||
|
||||
[System architecture patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Design Principles and Best Practices
|
||||
|
||||
[Design principles analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability and Performance Patterns
|
||||
|
||||
[Scalability patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration and Communication Patterns
|
||||
|
||||
[Integration patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Security Architecture Patterns
|
||||
|
||||
[Security patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Architecture Patterns
|
||||
|
||||
[Data architecture analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Architecture
|
||||
|
||||
[Deployment architecture analysis with source citations]
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Continue Option
|
||||
|
||||
Show the generated architectural patterns and present continue option:
|
||||
"I've completed the **architectural patterns analysis** for effective architecture approaches.
|
||||
|
||||
**Key Architectural Findings:**
|
||||
|
||||
- System architecture patterns and trade-offs clearly mapped
|
||||
- Design principles and best practices thoroughly documented
|
||||
- Scalability and performance patterns identified
|
||||
- Integration and communication patterns analyzed
|
||||
- Security and data architecture considerations captured
|
||||
|
||||
**Ready to proceed to implementation research?**
|
||||
[C] Continue - Save this to the document and move to implementation research
|
||||
|
||||
### 7. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-05-implementation-research.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 5.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ System architecture patterns identified with current citations
|
||||
✅ Design principles clearly documented and analyzed
|
||||
✅ Scalability and performance patterns thoroughly mapped
|
||||
✅ Integration and communication patterns captured
|
||||
✅ Security and data architecture considerations analyzed
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
✅ Proper routing to implementation research step
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical system architecture patterns
|
||||
❌ Not analyzing design trade-offs and considerations
|
||||
❌ Incomplete scalability or performance patterns analysis
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## ARCHITECTURAL RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for architecture documentation and pattern catalogs
|
||||
- Use architectural conference proceedings and case studies
|
||||
- Research successful system architectures and their evolution
|
||||
- Note architectural decision records (ADRs) and rationales
|
||||
- Research architecture assessment and evaluation frameworks
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
|
||||
Remember: Always emphasize current architectural data and rigorous source verification!
|
||||
@@ -1,239 +0,0 @@
|
||||
# Technical Research Step 4: Implementation Research
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
|
||||
- 💬 FOCUS on implementation approaches and technology adoption
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after implementation research content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- Focus on implementation approaches and technology adoption strategies
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final step in the technical research workflow
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive implementation research with emphasis on practical implementation approaches and technology adoption.
|
||||
|
||||
## IMPLEMENTATION RESEARCH SEQUENCE:
|
||||
|
||||
### 1. Begin Implementation Research
|
||||
|
||||
Start with implementation research approach:
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
|
||||
|
||||
**Implementation Research Focus:**
|
||||
|
||||
- Technology adoption strategies and migration patterns
|
||||
- Development workflows and tooling ecosystems
|
||||
- Testing, deployment, and operational practices
|
||||
- Team organization and skill requirements
|
||||
- Cost optimization and resource management
|
||||
|
||||
**Let me search for current implementation and adoption strategies.**"
|
||||
|
||||
### 2. Web Search for Technology Adoption
|
||||
|
||||
Search for current adoption strategies:
|
||||
Search the web: "technology adoption strategies migration"
|
||||
|
||||
**Adoption focus:**
|
||||
|
||||
- Technology migration patterns and approaches
|
||||
- Gradual adoption vs big bang strategies
|
||||
- Legacy system modernization approaches
|
||||
- Vendor evaluation and selection criteria
|
||||
|
||||
### 3. Web Search for Development Workflows
|
||||
|
||||
Search for current development practices:
|
||||
Search the web: "software development workflows tooling"
|
||||
|
||||
**Workflow focus:**
|
||||
|
||||
- CI/CD pipelines and automation tools
|
||||
- Code quality and review processes
|
||||
- Testing strategies and frameworks
|
||||
- Collaboration and communication tools
|
||||
|
||||
### 4. Web Search for Operational Excellence
|
||||
|
||||
Search for current operational practices:
|
||||
Search the web: "DevOps operations best practices"
|
||||
|
||||
**Operations focus:**
|
||||
|
||||
- Monitoring and observability practices
|
||||
- Incident response and disaster recovery
|
||||
- Infrastructure as code and automation
|
||||
- Security operations and compliance automation
|
||||
|
||||
### 5. Generate Implementation Research Content
|
||||
|
||||
Prepare implementation analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Implementation Approaches and Technology Adoption
|
||||
|
||||
### Technology Adoption Strategies
|
||||
|
||||
[Technology adoption analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Workflows and Tooling
|
||||
|
||||
[Development workflows analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Testing and Quality Assurance
|
||||
|
||||
[Testing approaches analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Practices
|
||||
|
||||
[Deployment practices analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Team Organization and Skills
|
||||
|
||||
[Team organization analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Cost Optimization and Resource Management
|
||||
|
||||
[Cost optimization analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Assessment and Mitigation
|
||||
|
||||
[Risk mitigation analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
## Technical Research Recommendations
|
||||
|
||||
### Implementation Roadmap
|
||||
|
||||
[Implementation roadmap recommendations]
|
||||
|
||||
### Technology Stack Recommendations
|
||||
|
||||
[Technology stack suggestions]
|
||||
|
||||
### Skill Development Requirements
|
||||
|
||||
[Skill development recommendations]
|
||||
|
||||
### Success Metrics and KPIs
|
||||
|
||||
[Success measurement framework]
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Complete Option
|
||||
|
||||
Show the generated implementation research and present complete option:
|
||||
"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
|
||||
|
||||
**Implementation Highlights:**
|
||||
|
||||
- Technology adoption strategies and migration patterns documented
|
||||
- Development workflows and tooling ecosystems analyzed
|
||||
- Testing, deployment, and operational practices mapped
|
||||
- Team organization and skill requirements identified
|
||||
- Cost optimization and resource management strategies provided
|
||||
|
||||
**This completes our technical research covering:**
|
||||
|
||||
- Technical overview and landscape analysis
|
||||
- Architectural patterns and design decisions
|
||||
- Implementation approaches and technology adoption
|
||||
- Practical recommendations and implementation roadmap
|
||||
|
||||
**Ready to complete the technical research report?**
|
||||
[C] Complete Research - Save final document and conclude
|
||||
|
||||
### 7. Handle Complete Selection
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Complete the technical research workflow
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 5.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Technology adoption strategies identified with current citations
|
||||
✅ Development workflows and tooling thoroughly analyzed
|
||||
✅ Testing and deployment practices clearly documented
|
||||
✅ Team organization and skill requirements mapped
|
||||
✅ Cost optimization and risk mitigation strategies provided
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
✅ Technical research workflow completed successfully
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical technology adoption strategies
|
||||
❌ Not providing practical implementation guidance
|
||||
❌ Incomplete development workflows or operational practices analysis
|
||||
❌ Not presenting completion option for research workflow
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## IMPLEMENTATION RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for implementation case studies and success stories
|
||||
- Research technology migration patterns and lessons learned
|
||||
- Identify common implementation challenges and solutions
|
||||
- Research development tooling ecosystem evaluations
|
||||
- Analyze operational excellence frameworks and maturity models
|
||||
|
||||
## TECHNICAL RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All technical research steps completed
|
||||
- Comprehensive technical research document generated
|
||||
- All sections appended with source citations
|
||||
- Technical research workflow status updated
|
||||
- Final implementation recommendations provided to user
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
Technical research workflow complete. User may:
|
||||
|
||||
- Use technical research to inform architecture decisions
|
||||
- Conduct additional research on specific technologies
|
||||
- Combine technical research with other research types for comprehensive insights
|
||||
- Move forward with implementation based on technical insights
|
||||
|
||||
Congratulations on completing comprehensive technical research! 🎉
|
||||
@@ -1,486 +0,0 @@
|
||||
# Technical Research Step 5: Technical Synthesis and Completion
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after synthesis content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - comprehensive technical analysis
|
||||
- **Research goals = "{{research_goals}}"** - achieved through exhaustive technical research
|
||||
- All technical research sections have been completed (overview, architecture, implementation)
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final synthesis step producing the complete technical research document
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Produce a comprehensive, authoritative technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive technical research.
|
||||
|
||||
## COMPREHENSIVE TECHNICAL DOCUMENT SYNTHESIS:
|
||||
|
||||
### 1. Technical Document Structure Planning
|
||||
|
||||
**Complete Technical Research Document Structure:**
|
||||
|
||||
```markdown
|
||||
# [Compelling Technical Title]: Comprehensive {{research_topic}} Technical Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Brief compelling overview of key technical findings and strategic implications]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- Technical Research Introduction and Methodology
|
||||
- Technical Landscape and Architecture Analysis
|
||||
- Implementation Approaches and Best Practices
|
||||
- Technology Stack Evolution and Trends
|
||||
- Integration and Interoperability Patterns
|
||||
- Performance and Scalability Analysis
|
||||
- Security and Compliance Considerations
|
||||
- Strategic Technical Recommendations
|
||||
- Implementation Roadmap and Risk Assessment
|
||||
- Future Technical Outlook and Innovation Opportunities
|
||||
- Technical Research Methodology and Source Documentation
|
||||
- Technical Appendices and Reference Materials
|
||||
```
|
||||
|
||||
### 2. Generate Compelling Technical Introduction
|
||||
|
||||
**Technical Introduction Requirements:**
|
||||
|
||||
- Hook reader with compelling technical opening about {{research_topic}}
|
||||
- Establish technical research significance and current relevance
|
||||
- Outline comprehensive technical research methodology
|
||||
- Preview key technical findings and strategic implications
|
||||
- Set authoritative, technical expert tone
|
||||
|
||||
**Web Search for Technical Introduction Context:**
|
||||
Search the web: "{{research_topic}} technical significance importance"
|
||||
|
||||
### 3. Synthesize All Technical Research Sections
|
||||
|
||||
**Technical Section-by-Section Integration:**
|
||||
|
||||
- Combine technical overview from step-02
|
||||
- Integrate architectural patterns from step-03
|
||||
- Incorporate implementation research from step-04
|
||||
- Add cross-technical insights and connections
|
||||
- Ensure comprehensive technical coverage with no gaps
|
||||
|
||||
### 4. Generate Complete Technical Document Content
|
||||
|
||||
#### Final Technical Document Structure:
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]: Comprehensive {{research_topic}} Technical Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive current technical research]
|
||||
|
||||
**Key Technical Findings:**
|
||||
|
||||
- [Most significant architectural insights]
|
||||
- [Critical implementation considerations]
|
||||
- [Important technology trends]
|
||||
- [Strategic technical implications]
|
||||
|
||||
**Technical Recommendations:**
|
||||
|
||||
- [Top 3-5 actionable technical recommendations based on research]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. Technical Research Introduction and Methodology
|
||||
2. {{research_topic}} Technical Landscape and Architecture Analysis
|
||||
3. Implementation Approaches and Best Practices
|
||||
4. Technology Stack Evolution and Current Trends
|
||||
5. Integration and Interoperability Patterns
|
||||
6. Performance and Scalability Analysis
|
||||
7. Security and Compliance Considerations
|
||||
8. Strategic Technical Recommendations
|
||||
9. Implementation Roadmap and Risk Assessment
|
||||
10. Future Technical Outlook and Innovation Opportunities
|
||||
11. Technical Research Methodology and Source Verification
|
||||
12. Technical Appendices and Reference Materials
|
||||
|
||||
## 1. Technical Research Introduction and Methodology
|
||||
|
||||
### Technical Research Significance
|
||||
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical right now]
|
||||
_Technical Importance: [Strategic technical significance with current context]_
|
||||
_Business Impact: [Business implications of technical research]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Research Methodology
|
||||
|
||||
[Comprehensive description of technical research approach including:]
|
||||
|
||||
- **Technical Scope**: [Comprehensive technical coverage areas]
|
||||
- **Data Sources**: [Authoritative technical sources and verification approach]
|
||||
- **Analysis Framework**: [Structured technical analysis methodology]
|
||||
- **Time Period**: [current focus and technical evolution context]
|
||||
- **Technical Depth**: [Level of technical detail and analysis]
|
||||
|
||||
### Technical Research Goals and Objectives
|
||||
|
||||
**Original Technical Goals:** {{research_goals}}
|
||||
|
||||
**Achieved Technical Objectives:**
|
||||
|
||||
- [Technical Goal 1 achievement with supporting evidence]
|
||||
- [Technical Goal 2 achievement with supporting evidence]
|
||||
- [Additional technical insights discovered during research]
|
||||
|
||||
## 2. {{research_topic}} Technical Landscape and Architecture Analysis
|
||||
|
||||
### Current Technical Architecture Patterns
|
||||
|
||||
[Comprehensive architectural analysis synthesized from step-03 with current context]
|
||||
_Dominant Patterns: [Current architectural approaches]_
|
||||
_Architectural Evolution: [Historical and current evolution patterns]_
|
||||
_Architectural Trade-offs: [Key architectural decisions and implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Design Principles and Best Practices
|
||||
|
||||
[Complete system design analysis]
|
||||
_Design Principles: [Core principles guiding {{research_topic}} implementations]_
|
||||
_Best Practice Patterns: [Industry-standard approaches and methodologies]_
|
||||
_Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Implementation Approaches and Best Practices
|
||||
|
||||
### Current Implementation Methodologies
|
||||
|
||||
[Implementation analysis from step-04 with current context]
|
||||
_Development Approaches: [Current development methodologies and approaches]_
|
||||
_Code Organization Patterns: [Structural patterns and organization strategies]_
|
||||
_Quality Assurance Practices: [Testing, validation, and quality approaches]_
|
||||
_Deployment Strategies: [Current deployment and operations practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Framework and Tooling
|
||||
|
||||
[Comprehensive implementation framework analysis]
|
||||
_Development Frameworks: [Popular frameworks and their characteristics]_
|
||||
_Tool Ecosystem: [Development tools and platform considerations]_
|
||||
_Build and Deployment Systems: [CI/CD and automation approaches]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Technology Stack Evolution and Current Trends
|
||||
|
||||
### Current Technology Stack Landscape
|
||||
|
||||
[Technology stack analysis from step-02 with current updates]
|
||||
_Programming Languages: [Current language trends and adoption patterns]_
|
||||
_Frameworks and Libraries: [Popular frameworks and their use cases]_
|
||||
_Database and Storage Technologies: [Current data storage and management trends]_
|
||||
_API and Communication Technologies: [Integration and communication patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Patterns
|
||||
|
||||
[Comprehensive technology adoption analysis]
|
||||
_Adoption Trends: [Technology adoption rates and patterns]_
|
||||
_Migration Patterns: [Technology migration and evolution trends]_
|
||||
_Emerging Technologies: [New technologies and their potential impact]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Integration and Interoperability Patterns
|
||||
|
||||
### Current Integration Approaches
|
||||
|
||||
[Integration patterns analysis with current context]
|
||||
_API Design Patterns: [Current API design and implementation patterns]_
|
||||
_Service Integration: [Microservices and service integration approaches]_
|
||||
_Data Integration: [Data exchange and integration patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Interoperability Standards and Protocols
|
||||
|
||||
[Comprehensive interoperability analysis]
|
||||
_Standards Compliance: [Industry standards and compliance requirements]_
|
||||
_Protocol Selection: [Communication protocols and selection criteria]_
|
||||
_Integration Challenges: [Common integration challenges and solutions]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Performance and Scalability Analysis
|
||||
|
||||
### Performance Characteristics and Optimization
|
||||
|
||||
[Performance analysis based on research findings]
|
||||
_Performance Benchmarks: [Current performance characteristics and benchmarks]_
|
||||
_Optimization Strategies: [Performance optimization approaches and techniques]_
|
||||
_Monitoring and Measurement: [Performance monitoring and measurement practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability Patterns and Approaches
|
||||
|
||||
[Comprehensive scalability analysis]
|
||||
_Scalability Patterns: [Architectural and design patterns for scalability]_
|
||||
_Capacity Planning: [Capacity planning and resource management approaches]_
|
||||
_Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Security and Compliance Considerations
|
||||
|
||||
### Security Best Practices and Frameworks
|
||||
|
||||
[Security analysis with current context]
|
||||
_Security Frameworks: [Current security frameworks and best practices]_
|
||||
_Threat Landscape: [Current security threats and mitigation approaches]_
|
||||
_Secure Development Practices: [Secure coding and development lifecycle]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Compliance and Regulatory Considerations
|
||||
|
||||
[Comprehensive compliance analysis]
|
||||
_Industry Standards: [Relevant industry standards and compliance requirements]_
|
||||
_Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_
|
||||
_Audit and Governance: [Technical audit and governance practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Strategic Technical Recommendations
|
||||
|
||||
### Technical Strategy and Decision Framework
|
||||
|
||||
[Strategic technical recommendations based on comprehensive research]
|
||||
_Architecture Recommendations: [Recommended architectural approaches and patterns]_
|
||||
_Technology Selection: [Recommended technology stack and selection criteria]_
|
||||
_Implementation Strategy: [Recommended implementation approaches and methodologies]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Technical Advantage
|
||||
|
||||
[Analysis of technical competitive positioning]
|
||||
_Technology Differentiation: [Technical approaches that provide competitive advantage]_
|
||||
_Innovation Opportunities: [Areas for technical innovation and differentiation]_
|
||||
_Strategic Technology Investments: [Recommended technology investments and priorities]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Implementation Roadmap and Risk Assessment
|
||||
|
||||
### Technical Implementation Framework
|
||||
|
||||
[Comprehensive implementation guidance based on research findings]
|
||||
_Implementation Phases: [Recommended phased implementation approach]_
|
||||
_Technology Migration Strategy: [Approach for technology adoption and migration]_
|
||||
_Resource Planning: [Technical resources and capabilities planning]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Risk Management
|
||||
|
||||
[Comprehensive technical risk assessment]
|
||||
_Technical Risks: [Major technical risks and mitigation strategies]_
|
||||
_Implementation Risks: [Risks associated with implementation and deployment]_
|
||||
_Business Impact Risks: [Technical risks and their business implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 10. Future Technical Outlook and Innovation Opportunities
|
||||
|
||||
### Emerging Technology Trends
|
||||
|
||||
[Forward-looking technical analysis based on comprehensive research]
|
||||
_Near-term Technical Evolution: [1-2 year technical development expectations]_
|
||||
_Medium-term Technology Trends: [3-5 year expected technical developments]_
|
||||
_Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Innovation and Research Opportunities
|
||||
|
||||
[Technical innovation analysis and recommendations]
|
||||
_Research Opportunities: [Areas for technical research and innovation]_
|
||||
_Emerging Technology Adoption: [Potential new technologies and adoption timelines]_
|
||||
_Innovation Framework: [Approach for fostering technical innovation]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 11. Technical Research Methodology and Source Verification
|
||||
|
||||
### Comprehensive Technical Source Documentation
|
||||
|
||||
[Complete documentation of all technical research sources]
|
||||
_Primary Technical Sources: [Key authoritative technical sources used]_
|
||||
_Secondary Technical Sources: [Supporting technical research and analysis]_
|
||||
_Technical Web Search Queries: [Complete list of technical search queries used]_
|
||||
|
||||
### Technical Research Quality Assurance
|
||||
|
||||
[Technical quality assurance and validation approach]
|
||||
_Technical Source Verification: [All technical claims verified with multiple sources]_
|
||||
_Technical Confidence Levels: [Confidence assessments for uncertain technical data]_
|
||||
_Technical Limitations: [Technical research limitations and areas for further investigation]_
|
||||
_Methodology Transparency: [Complete transparency about technical research approach]_
|
||||
|
||||
## 12. Technical Appendices and Reference Materials
|
||||
|
||||
### Detailed Technical Data Tables
|
||||
|
||||
[Comprehensive technical data tables supporting research findings]
|
||||
_Architectural Pattern Tables: [Detailed architectural pattern comparisons]_
|
||||
_Technology Stack Analysis: [Detailed technology evaluation and comparison data]_
|
||||
_Performance Benchmark Data: [Comprehensive performance measurement data]_
|
||||
|
||||
### Technical Resources and References
|
||||
|
||||
[Valuable technical resources for continued research and implementation]
|
||||
_Technical Standards: [Relevant technical standards and specifications]_
|
||||
_Open Source Projects: [Key open source projects and communities]_
|
||||
_Research Papers and Publications: [Academic and industry research sources]_
|
||||
_Technical Communities: [Professional networks and technical communities]_
|
||||
|
||||
---
|
||||
|
||||
## Technical Research Conclusion
|
||||
|
||||
### Summary of Key Technical Findings
|
||||
|
||||
[Comprehensive summary of the most important technical research findings]
|
||||
|
||||
### Strategic Technical Impact Assessment
|
||||
|
||||
[Assessment of technical implications for {{research_topic}}]
|
||||
|
||||
### Next Steps Technical Recommendations
|
||||
|
||||
[Specific next steps for leveraging this technical research]
|
||||
|
||||
---
|
||||
|
||||
**Technical Research Completion Date:** {{date}}
|
||||
**Research Period:** current comprehensive technical analysis
|
||||
**Document Length:** As needed for comprehensive technical coverage
|
||||
**Source Verification:** All technical facts cited with current sources
|
||||
**Technical Confidence Level:** High - based on multiple authoritative technical sources
|
||||
|
||||
_This comprehensive technical research document serves as an authoritative technical reference on {{research_topic}} and provides strategic technical insights for informed decision-making and implementation._
|
||||
```
|
||||
|
||||
### 5. Present Complete Technical Document and Final Option
|
||||
|
||||
**Technical Document Completion Presentation:**
|
||||
|
||||
"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
|
||||
|
||||
**Technical Document Features:**
|
||||
|
||||
- **Compelling Technical Introduction**: Engaging technical opening that establishes research significance
|
||||
- **Comprehensive Technical TOC**: Complete navigation structure for technical reference
|
||||
- **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Technical Summary**: Key technical findings and strategic implications highlighted
|
||||
- **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research
|
||||
- **Complete Technical Source Citations**: Every technical claim verified with current sources
|
||||
|
||||
**Technical Research Completeness:**
|
||||
|
||||
- Technical landscape and architecture analysis fully documented
|
||||
- Implementation approaches and best practices comprehensively covered
|
||||
- Technology stack evolution and trends detailed
|
||||
- Integration, performance, and security analysis complete
|
||||
- Strategic technical insights and implementation guidance provided
|
||||
|
||||
**Technical Document Standards Met:**
|
||||
|
||||
- Exhaustive technical research with no critical gaps
|
||||
- Professional technical structure and compelling narrative
|
||||
- As long as needed for comprehensive technical coverage
|
||||
- Multiple independent technical sources for all claims
|
||||
- current technical data throughout with proper citations
|
||||
|
||||
**Ready to complete this comprehensive technical research document?**
|
||||
[C] Complete Research - Save final comprehensive technical document
|
||||
|
||||
### 6. Handle Final Technical Completion
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the complete technical document to the research file
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
||||
- Complete the technical research workflow
|
||||
- Provide final technical document delivery confirmation
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the complete comprehensive technical research document using the full structure above.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Compelling technical introduction with research significance
|
||||
✅ Comprehensive technical table of contents with complete document structure
|
||||
✅ Exhaustive technical research coverage across all technical aspects
|
||||
✅ Executive technical summary with key findings and strategic implications
|
||||
✅ Strategic technical recommendations grounded in comprehensive research
|
||||
✅ Complete technical source verification with current citations
|
||||
✅ Professional technical document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Technical research workflow completed with comprehensive document
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not producing compelling technical introduction
|
||||
❌ Missing comprehensive technical table of contents
|
||||
❌ Incomplete technical research coverage across technical aspects
|
||||
❌ Not providing executive technical summary with key findings
|
||||
❌ Missing strategic technical recommendations based on research
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing technical document without professional structure
|
||||
❌ Not presenting completion option for final technical document
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS:
|
||||
|
||||
This step ensures the final technical research document:
|
||||
|
||||
- Serves as an authoritative technical reference on {{research_topic}}
|
||||
- Provides strategic technical insights for informed decision-making
|
||||
- Includes comprehensive technical coverage with no gaps
|
||||
- Maintains rigorous technical source verification standards
|
||||
- Delivers strategic technical insights and actionable recommendations
|
||||
- Meets professional technical research document quality standards
|
||||
|
||||
## TECHNICAL RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All technical research steps completed (1-5)
|
||||
- Comprehensive technical research document generated
|
||||
- Professional technical document structure with intro, TOC, and summary
|
||||
- All technical sections appended with source citations
|
||||
- Technical research workflow status updated to complete
|
||||
- Final comprehensive technical research document delivered to user
|
||||
|
||||
## FINAL TECHNICAL DELIVERABLE:
|
||||
|
||||
Complete authoritative technical research document on {{research_topic}} that:
|
||||
|
||||
- Establishes technical credibility through comprehensive research
|
||||
- Provides strategic technical insights for informed decision-making
|
||||
- Serves as technical reference document for continued use
|
||||
- Maintains highest technical research quality standards with current verification
|
||||
|
||||
Congratulations on completing comprehensive technical research with professional documentation! 🎉
|
||||
@@ -1,173 +0,0 @@
|
||||
---
|
||||
name: research
|
||||
description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
|
||||
web_bundle: true
|
||||
---
|
||||
|
||||
# Research Workflow
|
||||
|
||||
**Goal:** Conduct comprehensive, exhaustive research across multiple domains using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
|
||||
|
||||
**Document Standards:**
|
||||
|
||||
- **Comprehensive Coverage**: Exhaustive research with no critical gaps
|
||||
- **Source Verification**: Every factual claim backed by web sources with URL citations
|
||||
- **Document Length**: As long as needed to fully cover the research topic
|
||||
- **Professional Structure**: Compelling narrative introduction, detailed TOC, and comprehensive summary
|
||||
- **Authoritative Sources**: Multiple independent sources for all critical claims
|
||||
|
||||
**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
|
||||
|
||||
**Final Deliverable**: A complete research document that serves as an authoritative reference on the research topic with:
|
||||
|
||||
- Compelling narrative introduction
|
||||
- Comprehensive table of contents
|
||||
- Detailed research sections with proper citations
|
||||
- Executive summary and conclusions
|
||||
|
||||
## WORKFLOW ARCHITECTURE
|
||||
|
||||
This uses **micro-file architecture** with **routing-based discovery**:
|
||||
|
||||
- Each research type has its own step folder
|
||||
- Step 01 discovers research type and routes to appropriate sub-workflow
|
||||
- Sequential progression within each research type
|
||||
- Document state tracked in output frontmatter
|
||||
|
||||
## INITIALIZATION
|
||||
|
||||
### Configuration Loading
|
||||
|
||||
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
||||
|
||||
- `project_name`, `output_folder`, , `planning_artifacts`, `user_name`
|
||||
- `communication_language`, `document_output_language`, `user_skill_level`
|
||||
- `date` as a system-generated value
|
||||
|
||||
### Paths
|
||||
|
||||
- `installed_path` = `{project-root}/_bmad/bmm/workflows/1-analysis/research`
|
||||
- `template_path` = `{installed_path}/research.template.md`
|
||||
- `default_output_file` = `{planning_artifacts}/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
|
||||
|
||||
## PREREQUISITE
|
||||
|
||||
**⛔ Web search required.** If unavailable, abort and tell the user.
|
||||
|
||||
## RESEARCH BEHAVIOR
|
||||
|
||||
### Web Research Standards
|
||||
|
||||
- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
|
||||
- **Source Verification**: Require citations for all factual claims
|
||||
- **Anti-Hallucination Protocol**: Never present information without verified sources
|
||||
- **Multiple Sources**: Require at least 2 independent sources for critical claims
|
||||
- **Conflict Resolution**: Present conflicting views and note discrepancies
|
||||
- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
|
||||
|
||||
### Source Quality Standards
|
||||
|
||||
- **Distinguish Clearly**: Facts (from sources) vs Analysis (interpretation) vs Speculation
|
||||
- **URL Citation**: Always include source URLs when presenting web search data
|
||||
- **Critical Claims**: Market size, growth rates, competitive data need verification
|
||||
- **Fact Checking**: Apply fact-checking to critical data points
|
||||
|
||||
## Implementation Instructions
|
||||
|
||||
Execute research type discovery and routing:
|
||||
|
||||
### Research Type Discovery
|
||||
|
||||
**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
|
||||
|
||||
**Research Standards:**
|
||||
|
||||
- **Anti-Hallucination Protocol**: Never present information without verified sources
|
||||
- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
|
||||
- **Source Citation**: Always include URLs for factual claims from web searches
|
||||
- **Multiple Sources**: Require 2+ independent sources for critical claims
|
||||
- **Conflict Resolution**: Present conflicting views and note discrepancies
|
||||
- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
|
||||
|
||||
### Collaborative Research Discovery
|
||||
|
||||
"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
|
||||
|
||||
**Let me help you clarify what you'd like to research.**
|
||||
|
||||
**First, tell me: What specific topic, problem, or area do you want to research?**
|
||||
|
||||
For example:
|
||||
|
||||
- 'The electric vehicle market in Europe'
|
||||
- 'Cloud migration strategies for healthcare'
|
||||
- 'AI implementation in financial services'
|
||||
- 'Sustainable packaging regulations'
|
||||
- 'Or anything else you have in mind...'
|
||||
|
||||
### Topic Exploration and Clarification
|
||||
|
||||
Based on the user's initial topic, explore and refine the research scope:
|
||||
|
||||
#### Topic Clarification Questions:
|
||||
|
||||
1. **Core Topic**: "What exactly about [topic] are you most interested in?"
|
||||
2. **Research Goals**: "What do you hope to achieve with this research?"
|
||||
3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
|
||||
4. **Timeline**: "Are you looking at current state, historical context, or future trends?"
|
||||
5. **Application**: "How will you use this research? (product development, strategy, academic, etc.)"
|
||||
|
||||
#### Context Building:
|
||||
|
||||
- **Initial Input**: User provides topic or research interest
|
||||
- **Collaborative Refinement**: Work together to clarify scope and objectives
|
||||
- **Goal Alignment**: Ensure research direction matches user needs
|
||||
- **Research Boundaries**: Establish clear focus areas and deliverables
|
||||
|
||||
### Research Type Identification
|
||||
|
||||
After understanding the research topic and goals, identify the most appropriate research approach:
|
||||
|
||||
**Research Type Options:**
|
||||
|
||||
1. **Market Research** - Market size, growth, competition, customer insights
|
||||
_Best for: Understanding market dynamics, customer behavior, competitive landscape_
|
||||
|
||||
2. **Domain Research** - Industry analysis, regulations, technology trends in specific domain
|
||||
_Best for: Understanding industry context, regulatory environment, ecosystem_
|
||||
|
||||
3. **Technical Research** - Technology evaluation, architecture decisions, implementation approaches
|
||||
_Best for: Technical feasibility, technology selection, implementation strategies_
|
||||
|
||||
**Recommendation**: Based on [topic] and [goals], I recommend [suggested research type] because [specific rationale].
|
||||
|
||||
**What type of research would work best for your needs?**
|
||||
|
||||
### Research Type Routing
|
||||
|
||||
<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions. YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`</critical>
|
||||
|
||||
#### If Market Research:
|
||||
|
||||
- Set `research_type = "market"`
|
||||
- Set `research_topic = [discovered topic from discussion]`
|
||||
- Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
|
||||
- Load: `./market-steps/step-01-init.md` with topic context
|
||||
|
||||
#### If Domain Research:
|
||||
|
||||
- Set `research_type = "domain"`
|
||||
- Set `research_topic = [discovered topic from discussion]`
|
||||
- Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
|
||||
- Load: `./domain-steps/step-01-init.md` with topic context
|
||||
|
||||
#### If Technical Research:
|
||||
|
||||
- Set `research_type = "technical"`
|
||||
- Set `research_topic = [discovered topic from discussion]`
|
||||
- Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
|
||||
- Load: `./technical-steps/step-01-init.md` with topic context
|
||||
|
||||
**Important**: The discovered topic from the collaborative discussion should be passed to the research initialization steps, so they don't need to ask "What do you want to research?" again - they can focus on refining the scope for their specific research type.
|
||||
|
||||
**Note:** All research workflows require web search for current data and source verification.
|
||||
Reference in New Issue
Block a user