brainstorming, research and partymode updated to use sharded step flow workflows

This commit is contained in:
Brian Madison
2025-11-28 15:18:51 -06:00
parent 00e72e66f8
commit 4e254d7c63
48 changed files with 4476 additions and 2432 deletions

View File

@@ -23,8 +23,9 @@ agent:
description: Get workflow status or initialize a workflow if not already done (optional)
- trigger: brainstorm-project
exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.md"
description: Guided Brainstorming session with final report (optional)
exec: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md"
data: "{project-root}/{bmad_folder}/bmm/data/project-context-template.md"
description: Guided Project Brainstorming session with final report (optional)
- trigger: research
exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md"

View File

@@ -17,7 +17,7 @@ agent:
- Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
critical_actions:
- "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
- "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
- "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
menu:
@@ -54,7 +54,7 @@ agent:
description: Create clear technical explanations with examples
- trigger: standards-guide
action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/workflows/techdoc/documentation-standards.md in a clear, formatted way for the user."
action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user."
description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
- trigger: party-mode

View File

@@ -0,0 +1,29 @@
# BMM Module Data
This directory contains module-specific data files used by BMM agents and workflows.
## Files
### `project-context-template.md`
Template for project-specific brainstorming context. Used by:
- Analyst agent `brainstorm-project` command
- Core brainstorming workflow when called with context
### `documentation-standards.md`
BMAD documentation standards and guidelines. Used by:
- Tech Writer agent (critical action loading)
- Various documentation workflows
- Standards validation and review processes
## Purpose
Separates module-specific data from core workflow implementations, maintaining clean architecture:
- Core workflows remain generic and reusable
- Module-specific templates and standards are properly scoped
- Data files can be easily maintained and updated
- Clear separation of concerns between core and module functionality

View File

@@ -0,0 +1,40 @@
# Project Brainstorming Context Template
## Project Focus Areas
This brainstorming session focuses on software and product development considerations:
### Key Exploration Areas
- **User Problems and Pain Points** - What challenges do users face?
- **Feature Ideas and Capabilities** - What could the product do?
- **Technical Approaches** - How might we build it?
- **User Experience** - How will users interact with it?
- **Business Model and Value** - How does it create value?
- **Market Differentiation** - What makes it unique?
- **Technical Risks and Challenges** - What could go wrong?
- **Success Metrics** - How will we measure success?
### Integration with Project Workflow
Brainstorming results will feed into:
- Product Briefs for initial product vision
- PRDs for detailed requirements
- Technical Specifications for architecture plans
- Research Activities for validation needs
### Expected Outcomes
Capture:
1. Problem Statements - Clearly defined user challenges
2. Solution Concepts - High-level approach descriptions
3. Feature Priorities - Categorized by importance and feasibility
4. Technical Considerations - Architecture and implementation thoughts
5. Next Steps - Actions needed to advance concepts
6. Integration Points - Connections to downstream workflows
---
_Use this template to provide project-specific context for brainstorming sessions. Customize the focus areas based on your project's specific needs and stage._

View File

@@ -1,71 +0,0 @@
# Project Brainstorming Focus
This context guide provides project-specific considerations for brainstorming sessions focused on software and product development.
## Session Focus Areas
When brainstorming for projects, consider exploring:
- **User Problems and Pain Points** - What challenges do users face?
- **Feature Ideas and Capabilities** - What could the product do?
- **Technical Approaches** - How might we build it?
- **User Experience** - How will users interact with it?
- **Business Model and Value** - How does it create value?
- **Market Differentiation** - What makes it unique?
- **Technical Risks and Challenges** - What could go wrong?
- **Success Metrics** - How will we measure success?
## Integration with Project Workflow
Brainstorming sessions typically feed into:
- **Product Briefs** - Initial product vision and strategy
- **PRDs** - Detailed requirements documents
- **Technical Specifications** - Architecture and implementation plans
- **Research Activities** - Areas requiring further investigation
## Brainstorming Techniques for Projects
### Problem-Solution Mapping
- Identify core user problems
- Brainstorm multiple solution approaches
- Evaluate feasibility and impact
### Feature Ideation
- Must-have vs nice-to-have features
- User journey mapping
- Competitive differentiation opportunities
### Technical Architecture Thinking
- High-level system design considerations
- Technology stack possibilities
- Integration challenges and opportunities
### Business Model Canvas
- Value proposition identification
- Customer segments and channels
- Revenue streams and cost structures
## Output Structure Guidance
Brainstorming results should capture:
1. **Problem Statements** - Clearly defined user challenges
2. **Solution Concepts** - High-level approach descriptions
3. **Feature Priorities** - Categorized by importance and feasibility
4. **Technical Considerations** - Architecture and implementation thoughts
5. **Next Steps** - Actions needed to advance concepts
6. **Integration Points** - Connections to downstream workflows
## Session Facilitation Notes
This context will be passed to the core CIS brainstorming workflow to:
- Provide project-specific framing for ideation techniques
- Ensure results align with BMAD workflow expectations
- Maintain focus on software/product development considerations
- Facilitate smooth integration with subsequent workflows

View File

@@ -1,194 +0,0 @@
# Project Brainstorming Step 1: Orchestrated Brainstorming Session
## MANDATORY EXECUTION RULES (READ FIRST):
- 🎯 This is a meta-workflow that orchestrates the core brainstorming workflow
- 📋 YOU ARE A BRAINSTORMING FACILITATOR, Guiding the user to get the best ideas out of them through facilitated suggestion
- 💬 FOCUS on project-specific context and workflow integration
- 🔗 CRITICAL: Must pass context to core brainstorming workflow correctly
## EXECUTION PROTOCOLS:
- 🎯 Validate workflow status and execution context before proceeding
- 📖 Load project context from brainstorming-focus.md
- 🔗 Invoke core brainstorming workflow with project context
- 💾 Save results to specified output location
- 📊 Update workflow status in integrated mode
## CONTEXT BOUNDARIES:
- Project context from brainstorming-focus.md is available
- Core brainstorming workflow path: `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
- Output location: `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
- Status file: `{output_folder}/bmm-workflow-status.yaml` (if in integrated mode)
## YOUR TASK:
Orchestrate a project brainstorming session using the core brainstorming workflow with project-specific context.
## PROJECT BRAINSTORMING SEQUENCE:
### 1. Workflow Status Validation
Begin with status validation approach:
"Now I'll set up your **project brainstorming session** by validating the workflow context and preparing the core brainstorming workflow.
**Status Validation Focus:**
- Check for existing workflow status file
- Validate execution mode (standalone vs integrated)
- Ensure brainstorming is appropriate next step in sequence
- Prepare workflow integration context
**Let me check the current workflow status.**"
#### Status File Check
- Check if `{output_folder}/bmm-workflow-status.yaml` exists
- If no status file: Set standalone_mode = true
- If status file exists: Load and validate workflow sequence
- Check if brainstorm-project is next expected workflow
- Validate project_level from metadata
### 2. Project Context Loading
Load project-specific brainstorming guidance:
"**Loading Project Brainstorming Context...**
**Project Focus Areas for Today's Session:**
- User Problems and Pain Points identification
- Feature Ideas and Capabilities exploration
- Technical Approaches and feasibility consideration
- User Experience design thinking
- Business Model and Value creation strategies
- Market Differentiation opportunities
- Technical Risks and Challenges assessment
- Success Metrics definition
**Integration Pathways:**
This brainstorming session will feed into:
- Product Briefs for initial product vision
- PRDs for detailed requirements
- Technical Specifications for architecture plans
- Research Activities for validation needs"
### 3. Core Brainstorming Workflow Orchestration
Invoke the core brainstorming workflow with project context:
**Orchestration Approach:**
"I'll now orchestrate the **core brainstorming workflow** with your project-specific context.
**What to Expect:**
- Interactive brainstorming techniques menu tailored for projects
- Project-focused ideation methods and guidance
- Structured capture of all generated ideas and insights
- Results saved to your project's brainstorming folder
**The core workflow will provide:**
- Multiple brainstorming technique options
- Guided ideation sessions based on your selections
- Real-time capture and organization of ideas
- Project-specific prompting and context awareness
**Let me launch the core brainstorming workflow with your project context...**"
#### Workflow Invocation
- Execute: `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
- Pass: `brainstorming-focus.md` context as input data
- Ensure: Output saves to `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
- Monitor: Session progress and results generation
### 4. Session Completion and Status Update
Complete the orchestrated session:
**Completion Process:**
"**✅ Project Brainstorming Session Complete!**
**Session Results:**
- Brainstorming session successfully orchestrated
- Core workflow executed with project context
- Results captured in: `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
- All ideas and insights organized for downstream workflows
{{#if standalone_mode != true}}
**Workflow Status Updated:**
- Progress tracking updated in BMAD workflow system
- Ready for next workflow in sequence
**Next Steps:**
- **Next required:** [Will determine from workflow status]
- **Recommended:** Review results before proceeding to next workflow
- **Optional:** Run additional analysis workflows (research, product-brief)
{{else}}
**Next Steps:**
Since no workflow sequence is active:
- Review brainstorming results and identify key concepts
- Consider running `workflow-init` to create a guided workflow path
- Refer to BMAD workflow guide for next steps
{{/if}}
**Integration Opportunities:**
Your brainstorming results are ready to feed into:
- **Product Brief** workflow for initial product vision
- **PRD** workflow for detailed requirements
- **Research** workflows for market/technical validation
- **Architecture** workflows for technical design"
#### Status Update (Integrated Mode Only)
- Load: `{output_folder}/bmm-workflow-status.yaml`
- Update: `workflow_status["brainstorm-project"] = "{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md"`
- Preserve: ALL comments and structure in status file
- Determine: Next workflow and agent for progression
## SUCCESS METRICS:
✅ Workflow status validated and execution context confirmed
✅ Project context loaded and prepared for core workflow
✅ Core brainstorming workflow successfully orchestrated
✅ Project-specific context passed correctly to core workflow
✅ Session results captured in specified output location
✅ Workflow status updated (in integrated mode)
✅ Integration guidance provided for next steps
## FAILURE MODES:
❌ Not validating workflow status before execution
❌ Failing to pass project context to core workflow
❌ Core brainstorming workflow execution failure
❌ Results not saved to correct output location
❌ Status not updated in integrated mode
❌ Not providing integration guidance for next steps
## CRITICAL WORKFLOW INTEGRATION:
- **Context Passing**: Must pass brainstorming-focus.md intact to core workflow
- **Output Management**: Ensure core workflow saves to correct location
- **Status Consistency**: Update workflow status file only in integrated mode
- **Path Recording**: Record only file paths as status values (no extra text)
## NEXT STEPS:
After completion, users can:
- Review brainstorming session results
- Brainstorm something else
- Proceed with recommended next workflow (integrated mode)
- Run product-brief or PRD workflows to develop concepts further
- Conduct research workflows to validate brainstormed ideas
- Begin architecture workflows for technical design concepts
This meta-workflow successfully bridges project-specific brainstorming needs with the powerful core brainstorming workflow while maintaining seamless integration with the broader BMAD methodology.

View File

@@ -1,191 +0,0 @@
---
name: Brainstorm Project Workflow
description: Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.
---
# Brainstorm Project Workflow
**Goal:** Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.
**Your Role:** You are a brainstorming facilitator who guides project ideation sessions using structured techniques while ensuring the results integrate seamlessly with the broader BMAD project workflow.
---
## WORKFLOW ARCHITECTURE
This uses **meta-workflow orchestration** with **step-based execution**:
- Orchestrates the core CIS brainstorming workflow with project context
- Step-based progression through project-specific preparation
- Integrates results with the broader BMAD workflow system
- Handles workflow status tracking and progression
---
## INITIALIZATION
### Configuration Loading
Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
- `project_name`, `output_folder`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
- `date`, `current_year`, `current_month` as system-generated values
### Paths
- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project`
- `context_path` = `{installed_path}/brainstorming-focus.md`
- `core_brainstorming` = `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
- `output_file` = `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
### Workflow Status Integration
- `status_file` = `{output_folder}/bmm-workflow-status.yaml`
- Tracks progress within the broader BMAD workflow system
- Handles both standalone and integrated execution modes
---
## EXECUTION
Execute project brainstorming with workflow orchestration:
### Step 1: Workflow Status Validation
**Goal:** Validate workflow readiness and execution context
**Status Check Process:**
1. **Status File Detection**: Check if `{status_file}` exists
2. **Standalone Mode**: If no status file, proceed in standalone mode
3. **Integrated Mode**: If status file found, validate workflow sequence
4. **Completion Check**: Verify if brainstorming already completed
5. **Sequence Validation**: Ensure brainstorming is appropriate next step
**Integrated Mode Logic:**
- Load full status file and parse workflow_status section
- Check status of "brainstorm-project" workflow
- Validate project_level from YAML metadata
- Determine next expected workflow in sequence
### Step 2: Project Context Loading
**Goal:** Load project-specific brainstorming guidance
**Context Areas:**
- User Problems and Pain Points identification
- Feature Ideas and Capabilities exploration
- Technical Approaches consideration
- User Experience design thinking
- Business Model and Value creation
- Market Differentiation strategies
- Technical Risks and Challenges assessment
- Success Metrics definition
**Integration Pathways:**
- Product Briefs - Initial product vision and strategy
- PRDs - Detailed requirements documents
- Technical Specifications - Architecture and implementation plans
- Research Activities - Areas requiring further investigation
### Step 3: Core Brainstorming Orchestration
**Goal:** Execute CIS brainstorming workflow with project context
**Orchestration Process:**
1. **Context Passing**: Transfer project context to core workflow
2. **Workflow Invocation**: Execute `{core_brainstorming}` with enriched context
3. **Session Guidance**: Provide project-specific framing for brainstorming techniques
4. **Result Capture**: Ensure output saves to specified location
**Core Workflow Integration:**
- Present interactive brainstorming techniques menu
- Guide user through selected ideation methods
- Generate and capture brainstorming session results
- Save output to: `{output_folder}/brainstorming/brainstorming-session-{{date}}.md`
### Step 4: Status Update and Completion
**Goal:** Update workflow status and provide completion guidance
**Status Update Process:**
1. **Integrated Mode**: Update workflow status file with completion path
2. **Path Recording**: Save brainstorming session file path as status value
3. **Next Workflow**: Determine next required workflow in sequence
4. **Agent Identification**: Identify next agent for workflow progression
**Completion Output:**
- Session results location and summary
- Status update confirmation (integrated mode)
- Next workflow steps and agent guidance
- Optional workflow recommendations
---
## OUTPUT STRUCTURE
### Brainstorming Session Output
```
{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md
```
Contains:
- Brainstorming session techniques used
- Generated ideas and concepts
- Project-specific insights and recommendations
- Integration guidance for downstream workflows
### Status Integration
Updates `{output_folder}/bmm-workflow-status.yaml`:
```yaml
workflow_status:
brainstorm-project: '{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md'
# Next workflow will be automatically determined
```
---
## WORKFLOW INTEGRATION CRITICAL POINTS
### Context Preservation
- Project context must be passed intact to core brainstorming workflow
- Maintain project focus areas throughout session
- Ensure integration pathways are considered during ideation
### Status Consistency
- Only update status file in integrated mode
- Preserve ALL comments and structure in status file
- Record only file paths as status values (no additional text)
### Output Location Management
- Brainstorming results go to dedicated `/brainstorming` subfolder
- Maintain consistent naming convention with date stamps
- Ensure accessibility for downstream workflows
---
## NEXT WORKFLOW INTEGRATION
After brainstorming completion, typical progression:
1. **Product Brief** - Transform ideas into structured product vision
2. **PRD** - Develop detailed requirements from brainstormed concepts
3. **Research** - Investigate ideas requiring market/technical validation
4. **Architecture** - Design technical approaches for selected concepts
The brainstorming session results provide the foundational ideation input for these subsequent workflows.

View File

@@ -1,191 +0,0 @@
# Deep Research Prompt Step 1: Context and Scope
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
- ✅ ALWAYS treat this as collaborative prompt engineering partnership
- 📋 YOU ARE A RESEARCH METHODOLOGIST, not content generator
- 💬 FOCUS on understanding research needs and creating structured prompts
- 🔍 WEB RESEARCH OPTIONAL - May search for best practices in research prompting
## EXECUTION PROTOCOLS:
- 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after initial context generation
- 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
## COLLABORATION MENUS (A/P/C):
This step will generate content and present choices:
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper prompt insights
- **P (Party Mode)**: Bring multiple perspectives to validate prompt methodology
- **C (Continue)**: Save the content to the document and proceed to next step
## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
## CONTEXT BOUNDARIES:
- Current document and frontmatter from main workflow discovery are available
- Research type = "deep-prompt" is already set
- Focus on creating structured research prompts for AI platforms
- May use web search for research prompting best practices
## YOUR TASK:
Understand the research prompting needs and establish the scope and methodology for creating structured research prompts.
## DEEP PROMPT RESEARCH INITIALIZATION:
### 1. Confirm Deep Prompt Research Direction
Begin with prompt engineering positioning:
"I'll guide you through **deep research prompt creation** where we develop structured, effective prompts for AI platforms.
**Deep Prompt Research Focus:**
- Structured prompt methodologies and frameworks
- Multi-step research prompt design
- Domain-specific prompt engineering techniques
- Prompt optimization and testing strategies
- Research workflow automation through prompts
**What type of research prompts are we creating?**
### 2. Gather Prompt Context
Understand the specific prompting needs:
#### Context Questions:
- "What AI platforms or models will these prompts be used with?"
- "What types of research topics or domains will the prompts cover?"
- "What level of complexity do the research prompts need?"
- "Are there specific methodologies or frameworks you want the prompts to follow?"
- "What research outcomes or deliverables should the prompts generate?"
### 3. Establish Prompt Research Scope
Define the boundaries and objectives:
#### Scope Definition:
- "How many different types of research prompts do we need?"
- "Should we focus on general research prompts or domain-specific ones?"
- "Are we creating prompts for single-use research or repeatable workflows?"
- "What level of detail should the prompts provide?"
- "Should the prompts include data analysis, synthesis, or both?"
### 4. Generate Prompt Research Overview
Prepare initial content to append to the document:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
```markdown
## Research Overview
### Prompt Engineering Objectives
[Prompt engineering objectives based on conversation]
### Target AI Platforms
[Target platforms and models based on conversation]
### Research Prompt Types
[Types of research prompts based on conversation]
### Prompt Methodology Framework
[Methodology framework for structuring research prompts]
### Quality Assurance Approach
[Quality assurance and testing approach for prompts]
```
### 5. Present Content and Menu
Show the generated overview and present choices:
"I've established the foundation for our **deep research prompt** creation. This will help you develop structured, effective prompts for AI-powered research.
**Here's what I'll add to the document:**
[Show the complete markdown content from step 4]
**What would you like to do?**
[A] Advanced Elicitation - Let's deepen our understanding of prompt engineering needs
[P] Party Mode - Bring different perspectives on prompt methodology
[C] Continue - Save this to the document and begin prompt framework development
### 6. Handle Menu Selection
#### If 'A' (Advanced Elicitation):
- Execute advanced-elicitation.xml with current prompt overview
- Process enhanced prompt insights that come back
- Ask user: "Accept these improvements to the prompt research overview? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
#### If 'P' (Party Mode):
- Execute party-mode workflow with current prompt overview
- Process collaborative prompt expertise and additional insights
- Ask user: "Accept these changes to the prompt research overview? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
#### If 'C' (Continue):
- Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1]`
- Load: `./step-02-prompt-frameworks.md`
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 4.
## SUCCESS METRICS:
✅ Prompt research scope clearly defined and confirmed
✅ Target AI platforms and models identified
✅ Prompt methodology framework established
✅ Quality assurance approach documented
✅ A/P/C menu presented and handled correctly
✅ Content properly appended to document when C selected
✅ Proper routing to next prompt development step
## FAILURE MODES:
❌ Not confirming specific AI platforms or use cases
❌ Missing prompt methodology framework definition
❌ Not establishing quality assurance approach
❌ Not presenting A/P/C menu after content generation
❌ Appending content without user selecting 'C'
## WEB RESEARCH READINESS:
This step may include web search for:
- Current best practices in AI research prompting
- Prompt engineering methodologies and frameworks
- Domain-specific prompt optimization techniques
- AI platform-specific prompt capabilities
## NEXT STEP:
After user selects 'C' and content is saved to document, load `./step-02-prompt-frameworks.md` to begin structured prompt framework development.
Remember: Focus on creating structured, effective prompts that enable AI-powered research workflows!

View File

@@ -1,190 +0,0 @@
# Deep Prompt Research Step 2: Prompt Engineering
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without web search verification
- ✅ ALWAYS use {{current_year}} web searches for current prompt engineering data
- 📋 YOU ARE A PROMPT ENGINEERING ANALYST, not content generator
- 💬 FOCUS on prompt engineering techniques and best practices
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
## EXECUTION PROTOCOLS:
- 🎯 Show web search analysis before presenting findings
- ⚠️ Present [C] continue option after prompt engineering 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 prompt engineering techniques and methodologies
- Web search capabilities with source verification are enabled
- May need to search for current prompt engineering research and frameworks
## YOUR TASK:
Conduct comprehensive prompt engineering research using current {{current_year}} web data with emphasis on techniques, frameworks, and best practices.
## PROMPT ENGINEERING SEQUENCE:
### 1. Begin Prompt Engineering Analysis
Start with prompt engineering research approach:
"Now I'll conduct **prompt engineering research** using current {{current_year}} web data to understand effective prompt design and optimization techniques.
**Prompt Engineering Focus:**
- Current prompt engineering methodologies and frameworks
- Advanced prompting techniques and strategies
- Prompt optimization and evaluation approaches
- Industry best practices and case studies
- Emerging trends in prompt engineering
**Let me search for current prompt engineering research and techniques.**"
### 2. Web Search for Prompt Engineering Techniques
Search for current prompt engineering techniques:
`WebSearch: "prompt engineering techniques methodologies {{current_year}}"`
**Techniques focus:**
- Chain-of-thought and reasoning prompts
- Few-shot and zero-shot prompting strategies
- Instruction following and role-based prompts
- Multi-modal and multimodal prompting approaches
### 3. Web Search for Prompt Frameworks
Search for current prompt frameworks:
`WebSearch: "prompt engineering frameworks tools {{current_year}}"`
**Frameworks focus:**
- Structured prompt design frameworks
- Prompt template systems and libraries
- Evaluation and testing frameworks
- Industry-standard prompting methodologies
### 4. Web Search for Prompt Optimization
Search for current optimization approaches:
`WebSearch: "prompt optimization evaluation {{current_year}}"`
**Optimization focus:**
- A/B testing and prompt improvement strategies
- Performance metrics and evaluation criteria
- Automated prompt optimization techniques
- Quality assessment methodologies
### 5. Generate Prompt Engineering Content
Prepare prompt engineering analysis with web search citations:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
```markdown
## Prompt Engineering Analysis
### Current Prompting Techniques
[Prompting techniques analysis with source citations]
_Source: [URL with {{current_year}} prompting data]_
### Structured Prompting Frameworks
[Prompt frameworks analysis with source citations]
_Source: [URL with {{current_year}} frameworks data]_
### Advanced Prompting Strategies
[Advanced strategies analysis with source citations]
_Source: [URL with {{current_year}} strategies data]_
### Prompt Optimization Methods
[Optimization methods analysis with source citations]
_Source: [URL with {{current_year}} optimization data]_
### Industry Best Practices
[Best practices analysis with source citations]
_Source: [URL with {{current_year}} best practices data]_
### Evaluation and Testing Approaches
[Evaluation approaches analysis with source citations]
_Source: [URL with {{current_year}} evaluation data]_
### Emerging Trends and Innovations
[Emerging trends analysis with source citations]
_Source: [URL with {{current_year}} trends data]_
```
### 6. Present Analysis and Continue Option
Show the generated prompt engineering analysis and present continue option:
"I've completed the **prompt engineering research** using current {{current_year}} data to understand effective prompt design and optimization techniques.
**Key Prompt Engineering Findings:**
- Current prompting techniques and methodologies clearly mapped
- Structured prompting frameworks and tools identified
- Advanced prompting strategies thoroughly analyzed
- Optimization and evaluation approaches documented
- Industry best practices and emerging trends captured
**Ready to proceed to AI interaction patterns?**
[C] Continue - Save this to the document and move to AI interaction patterns
### 7. Handle Continue Selection
#### If 'C' (Continue):
- Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1, 2]`
- Load: `./step-03-ai-interaction-patterns.md`
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 5.
## SUCCESS METRICS:
✅ Prompting techniques identified with current {{current_year}} citations
✅ Structured prompting frameworks clearly documented
✅ Advanced prompting strategies thoroughly analyzed
✅ Optimization and evaluation approaches mapped
✅ Industry best practices and emerging trends captured
✅ [C] continue option presented and handled correctly
✅ Content properly appended to document when C selected
✅ Proper routing to AI interaction patterns step
## FAILURE MODES:
❌ Not using {{current_year}} in prompt engineering web searches
❌ Missing critical prompting techniques or frameworks
❌ Not analyzing advanced prompting strategies
❌ Incomplete optimization or evaluation approaches analysis
❌ Not presenting [C] continue option after content generation
❌ Appending content without user selecting 'C'
## PROMPT ENGINEERING RESEARCH PROTOCOLS:
- Search for academic research papers on prompt engineering
- Research AI company blog posts and technical documentation
- Analyze open-source prompting frameworks and libraries
- Study prompt engineering case studies and success stories
- Research evaluation methodologies and benchmark datasets
## NEXT STEP:
After user selects 'C' and content is saved to document, load `./step-03-ai-interaction-patterns.md` to focus on AI interaction patterns and conversational design.
Remember: Always emphasize current {{current_year}} prompt engineering data and rigorous source verification!

View File

@@ -1,195 +0,0 @@
# Deep Prompt Research Step 3: AI Interaction Patterns
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without web search verification
- ✅ ALWAYS use {{current_year}} web searches for current AI interaction data
- 📋 YOU ARE AN AI INTERACTION DESIGN ANALYST, not content generator
- 💬 FOCUS on conversational AI patterns and user experience design
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
## EXECUTION PROTOCOLS:
- 🎯 Show web search analysis before presenting findings
- ⚠️ Present [C] continue option after AI interaction patterns content generation
- 💾 ONLY save 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
- Focus on AI interaction patterns and conversational design principles
- Web search capabilities with source verification are enabled
- May need to search for current conversational AI research and patterns
## YOUR TASK:
Conduct comprehensive AI interaction patterns research using current {{current_year}} web data with emphasis on conversational design and user experience patterns.
## AI INTERACTION PATTERNS SEQUENCE:
### 1. Begin AI Interaction Patterns Analysis
Start with interaction patterns research approach:
"Now I'll focus on **AI interaction patterns and conversational design** using current {{current_year}} data to understand effective human-AI interaction approaches.
**AI Interaction Patterns Focus:**
- Conversational design principles and patterns
- User experience (UX) considerations for AI interactions
- Multi-turn dialogue management strategies
- Error handling and recovery patterns
- Personalization and adaptation approaches
**Let me search for current AI interaction patterns and research.**"
### 2. Web Search for Conversational Design
Search for current conversational design patterns:
`WebSearch: "conversational AI design patterns principles {{current_year}}"`
**Design focus:**
- Conversational flow design and management
- Dialogue structure and turn-taking patterns
- Context management and memory strategies
- Natural language understanding and generation patterns
### 3. Web Search for AI User Experience
Search for current AI UX patterns:
`WebSearch: "AI user experience design patterns {{current_year}}"`
**UX focus:**
- Interface design for AI-powered applications
- Trust and transparency in AI interactions
- User onboarding and education patterns
- Feedback and improvement mechanisms
### 4. Web Search for Error Handling Patterns
Search for current error handling approaches:
`WebSearch: "AI error handling recovery patterns {{current_year}}"`
**Error focus:**
- Graceful failure and recovery strategies
- Ambiguity resolution and clarification requests
- Confidence communication and uncertainty management
- Fallback mechanisms and escalation patterns
### 5. Generate AI Interaction Patterns Content
Prepare interaction patterns analysis with web search citations:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
```markdown
## AI Interaction Patterns and Design
### Conversational Design Principles
[Conversational design analysis with source citations]
_Source: [URL with {{current_year}} conversational data]_
### Multi-Turn Dialogue Management
[Dialogue management analysis with source citations]
_Source: [URL with {{current_year}} dialogue data]_
### User Experience Patterns
[UX patterns analysis with source citations]
_Source: [URL with {{current_year}} UX data]_
### Error Handling and Recovery
[Error handling analysis with source citations]
_Source: [URL with {{current_year}} error handling data]_
### Context Management Strategies
[Context management analysis with source citations]
_Source: [URL with {{current_year}} context data]_
### Personalization and Adaptation
[Personalization analysis with source citations]
_Source: [URL with {{current_year}} personalization data]_
### Trust and Transparency Patterns
[Trust patterns analysis with source citations]
_Source: [URL with {{current_year}} trust data]_
### Performance Optimization Strategies
[Performance optimization analysis with source citations]
_Source: [URL with {{current_year}} performance data]_
```
### 6. Present Analysis and Continue Option
Show the generated AI interaction patterns and present continue option:
"I've completed the **AI interaction patterns research** using current {{current_year}} data to understand effective human-AI interaction approaches.
**Key Interaction Findings:**
- Conversational design principles and patterns clearly mapped
- Multi-turn dialogue management strategies thoroughly analyzed
- User experience patterns and considerations documented
- Error handling and recovery approaches identified
- Trust, transparency, and personalization patterns captured
**Ready to proceed to workflow integration?**
[C] Continue - Save this to the document and move to workflow integration
### 7. Handle Continue Selection
#### If 'C' (Continue):
- Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
- Load: `./step-04-workflow-integration.md`
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 5.
## SUCCESS METRICS:
✅ Conversational design principles identified with current {{current_year}} citations
✅ Multi-turn dialogue management strategies clearly documented
✅ User experience patterns thoroughly analyzed
✅ Error handling and recovery approaches mapped
✅ Trust, transparency, and personalization patterns captured
✅ [C] continue option presented and handled correctly
✅ Content properly appended to document when C selected
✅ Proper routing to workflow integration step
## FAILURE MODES:
❌ Not using {{current_year}} in AI interaction web searches
❌ Missing critical conversational design principles
❌ Not analyzing user experience patterns thoroughly
❌ Incomplete error handling or recovery patterns analysis
❌ Not presenting [C] continue option after content generation
❌ Appending content without user selecting 'C'
## AI INTERACTION RESEARCH PROTOCOLS:
- Search for human-computer interaction (HCI) research on AI interfaces
- Research conversational AI case studies and best practices
- Analyze industry guidelines for AI-powered product design
- Study user research and usability testing methodologies for AI
- Research accessibility and inclusive design patterns for AI interactions
## NEXT STEP:
After user selects 'C' and content is saved to document, load `./step-04-workflow-integration.md` to focus on workflow integration and implementation strategies.
Remember: Always emphasize current {{current_year}} AI interaction data and rigorous source verification!

View File

@@ -1,235 +0,0 @@
# Deep Prompt Research Step 4: Workflow Integration
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without web search verification
- ✅ ALWAYS use {{current_year}} web searches for current workflow integration data
- 📋 YOU ARE A WORKFLOW INTEGRATION SPECIALIST, not content generator
- 💬 FOCUS on practical implementation and workflow design strategies
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
## EXECUTION PROTOCOLS:
- 🎯 Show web search analysis before presenting findings
- ⚠️ Present [C] complete option after workflow integration 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 workflow integration and practical implementation strategies
- Web search capabilities with source verification are enabled
- This is the final step in the deep prompt research workflow
## YOUR TASK:
Conduct comprehensive workflow integration research using current {{current_year}} web data with emphasis on practical implementation and workflow design strategies.
## WORKFLOW INTEGRATION SEQUENCE:
### 1. Begin Workflow Integration Analysis
Start with workflow integration research approach:
"Now I'll complete our deep prompt research with **workflow integration and implementation strategies** using current {{current_year}} data.
**Workflow Integration Focus:**
- Integration patterns for AI-powered workflows
- Implementation strategies and best practices
- Workflow orchestration and automation approaches
- Testing and validation methodologies
- Monitoring and optimization techniques
**Let me search for current workflow integration and implementation strategies.**"
### 2. Web Search for Workflow Integration Patterns
Search for current integration patterns:
`WebSearch: "AI workflow integration patterns best practices {{current_year}}"`
**Integration focus:**
- System architecture integration approaches
- API design and integration patterns
- Data flow and processing workflows
- Microservices and distributed system integration
### 3. Web Search for Implementation Strategies
Search for current implementation approaches:
`WebSearch: "AI implementation strategies deployment {{current_year}}"`
**Implementation focus:**
- Development and deployment workflows
- Testing and quality assurance practices
- Change management and adoption strategies
- Performance monitoring and optimization
### 4. Web Search for Workflow Automation
Search for current automation approaches:
`WebSearch: "workflow automation orchestration AI {{current_year}}"`
**Automation focus:**
- Low-code and no-code workflow platforms
- Process automation and optimization techniques
- Integration with existing business processes
- Scalability and reliability considerations
### 5. Generate Workflow Integration Content
Prepare integration analysis with web search citations:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
```markdown
## Workflow Integration and Implementation
### Integration Architecture Patterns
[Integration patterns analysis with source citations]
_Source: [URL with {{current_year}} integration data]_
### Implementation Strategies
[Implementation strategies analysis with source citations]
_Source: [URL with {{current_year}} implementation data]_
### Workflow Orchestration Approaches
[Orchestration analysis with source citations]
_Source: [URL with {{current_year}} orchestration data]_
### Testing and Validation Frameworks
[Testing frameworks analysis with source citations]
_Source: [URL with {{current_year}} testing data]_
### Monitoring and Optimization
[Monitoring optimization analysis with source citations]
_Source: [URL with {{current_year}} monitoring data]_
### Change Management and Adoption
[Change management analysis with source citations]
_Source: [URL with {{current_year}} change management data]_
### Scalability and Performance Considerations
[Scalability analysis with source citations]
_Source: [URL with {{current_year}} scalability data]_
### Security and Compliance Integration
[Security integration analysis with source citations]
_Source: [URL with {{current_year}} security data]_
## Deep Prompt Research Recommendations
### Implementation Roadmap
[Implementation roadmap recommendations]
### Technology Stack Recommendations
[Technology stack suggestions]
### Best Practices and Guidelines
[Best practices recommendations]
### Success Metrics and Evaluation
[Success measurement framework]
```
### 6. Present Analysis and Complete Option
Show the generated workflow integration and present complete option:
"I've completed the **workflow integration and implementation research** using current {{current_year}} data, finalizing our comprehensive deep prompt research.
**Integration Highlights:**
- Integration architecture patterns and approaches documented
- Implementation strategies and best practices thoroughly analyzed
- Workflow orchestration and automation approaches identified
- Testing, monitoring, and optimization strategies provided
- Change management and adoption considerations captured
**This completes our deep prompt research covering:**
- Prompt engineering techniques and methodologies
- AI interaction patterns and design principles
- Workflow integration and implementation strategies
- Practical recommendations and implementation roadmap
**Ready to complete the deep prompt 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 deep prompt 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:
✅ Integration architecture patterns identified with current {{current_year}} citations
✅ Implementation strategies clearly documented
✅ Workflow orchestration approaches thoroughly analyzed
✅ Testing and monitoring frameworks mapped
✅ Change management and scalability considerations captured
✅ [C] complete option presented and handled correctly
✅ Content properly appended to document when C selected
✅ Deep prompt research workflow completed successfully
## FAILURE MODES:
❌ Not using {{current_year}} in workflow integration web searches
❌ Missing critical integration patterns or implementation strategies
❌ Not providing practical implementation guidance
❌ Incomplete testing or monitoring frameworks analysis
❌ Not presenting completion option for research workflow
❌ Appending content without user selecting 'C'
## WORKFLOW INTEGRATION RESEARCH PROTOCOLS:
- Search for enterprise architecture integration patterns
- Research DevOps and CI/CD practices for AI-powered applications
- Analyze workflow automation platforms and case studies
- Study change management methodologies for AI implementation
- Research monitoring and observability best practices for AI workflows
## DEEP PROMPT RESEARCH WORKFLOW COMPLETION:
When 'C' is selected:
- All deep prompt research steps completed
- Comprehensive deep prompt research document generated
- All sections appended with source citations
- Deep prompt research workflow status updated
- Final implementation recommendations provided to user
## NEXT STEPS:
Deep prompt research workflow complete. User may:
- Use deep prompt research to inform AI-powered workflow design
- Conduct additional research on specific AI technologies
- Combine deep prompt research with other research types for comprehensive insights
- Move forward with AI implementation based on research insights
Congratulations on completing comprehensive deep prompt research with current {{current_year}} data! 🎉

View File

@@ -33,43 +33,47 @@ This step will generate content and present choices:
## CONTEXT BOUNDARIES:
- Current document and frontmatter from step-01-discovery are available
- Current document and frontmatter from main workflow are available
- 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 capabilities with {{current_year}} data are enabled
## YOUR TASK:
Initialize domain research, gather context, and establish research scope with current web data.
Initialize domain research scope and approach for the already-identified topic: **{{research_topic}}**
## DOMAIN RESEARCH INITIALIZATION:
### 1. Confirm Domain Research Direction
Begin with domain-specific positioning:
"I'll guide you through **domain research** using current {{current_year}} web data with rigorous source verification.
"I'll guide you through **domain research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
**Domain Research Focus:**
**Research Goals Identified:** {{research_goals}}
- Industry analysis and market dynamics
- Regulatory requirements and compliance standards
- Technology trends and innovation patterns
- Competitive landscape within the domain
**Domain Research Focus for {{research_topic}}:**
- Industry analysis and market dynamics for this domain
- Regulatory requirements and compliance standards affecting {{research_topic}}
- Technology trends and innovation patterns in {{research_topic}}
- Competitive landscape within the {{research_topic}} domain
- Supply chain and ecosystem analysis
**What specific domain or industry are we researching?**
Let me refine the research scope specifically for **{{research_topic}}**:
### 2. Establish Research Context
Gather domain-specific details:
Refine domain-specific details based on the already-identified topic:
#### Context Questions:
#### Context Refinement Questions:
- "What specific domain/industry are we focusing on?"
- "Are there particular segments or sub-domains we should examine?"
- "What aspects of this domain are most critical for your project?"
- "Are there specific regulatory or compliance concerns?"
- "What time horizon should we consider (current state, future trends)?"
- "What specific aspects of {{research_topic}} are most critical for your goals?"
- "Are there particular segments or sub-domains within {{research_topic}} we should examine?"
- "What regulatory or compliance factors most impact {{research_topic}}?"
- "What time horizon for {{research_topic}} research - current state or include future trends?"
- "How deep should we analyze the {{research_topic}} domain - overview or comprehensive?"
### 3. Define Research Scope

View File

@@ -31,6 +31,8 @@ Conduct comprehensive domain/industry analysis using current {{current_year}} we
### 1. Begin Domain Analysis
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different domain areas simultaneously and thoroughly
Start with web research approach:
"Now I'll conduct comprehensive domain research using current {{current_year}} web data with rigorous source verification.
@@ -42,12 +44,16 @@ Start with web research approach:
- Key players and competitive ecosystem
- Supply chain and business model evolution
**Let me search for current {{current_year}} data on [domain/industry].**"
**Let me search for current {{current_year}} data on [domain/industry] using parallel web searches for comprehensive coverage.**"
### 2. Web Search for Industry Overview
### 2. Parallel Web Search Execution
**Execute multiple web searches simultaneously:**
Search for current industry information:
`WebSearch: "[domain/industry] market size growth {{current_year}}"`
`WebSearch: "[domain/industry] technology trends {{current_year}}"`
`WebSearch: "[domain/industry] regulations compliance {{current_year}}"`
`WebSearch: "[domain/industry] key players ecosystem {{current_year}}"`
**Analysis approach:**
@@ -55,32 +61,30 @@ Search for current industry information:
- Identify market size, growth rates, and trends
- Find authoritative sources (market research firms, industry associations)
- Note conflicting information from different sources
- Gather technology trends and innovation patterns
- Research regulatory requirements and compliance standards
- Analyze competitive landscape and key players
### 3. Web Search for Technology Trends
### 3. Analyze and Aggregate Results
Search for current technology developments:
`WebSearch: "[domain/industry] technology trends {{current_year}}"`
**Collect and analyze findings from all parallel searches:**
**Technology focus:**
"After executing comprehensive parallel web searches, let me analyze and aggregate the findings:
- Emerging technologies and innovation patterns
- Digital transformation impacts
- Automation and efficiency improvements
- New business models enabled by technology
**Research Coverage:**
### 4. Web Search for Regulatory Landscape
- Market analysis and industry dynamics
- Technology trends and innovation patterns
- Regulatory landscape and compliance requirements
- Key players and competitive ecosystem
Search for current regulatory requirements:
`WebSearch: "[domain/industry] regulations compliance {{current_year}}"`
**Cross-Domain Analysis:**
[Identify patterns, connections, and insights that emerge across multiple search areas]
**Regulatory focus:**
**Quality Assessment:**
[Overall confidence levels and research gaps identified]"
- Current regulations and compliance requirements
- Recent changes or upcoming regulations
- Industry standards and best practices
- Regional or jurisdictional differences
### 5. Generate Domain Analysis Content
### 4. Generate Domain Analysis Content
Prepare analysis content with source citations:
@@ -117,7 +121,7 @@ _Source: [URL with {{current_year}} data]_
_Source: [URL with {{current_year}} data]_
```
### 6. Present Analysis and Continue Option
### 5. Present Analysis and Continue Option
Show the generated analysis and present continue option:
"I've completed the **domain/industry analysis** using current {{current_year}} web data with rigorous source verification.
@@ -132,7 +136,7 @@ Show the generated analysis and present continue option:
**Ready to proceed to regulatory focus?**
[C] Continue - Save this to the document and move to regulatory focus
### 7. Handle Continue Selection
### 6. Handle Continue Selection
#### If 'C' (Continue):
@@ -142,7 +146,7 @@ Show the generated analysis and present continue option:
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 5.
When user selects 'C', append the content directly to the research document using the structure from step 4.
## SUCCESS METRICS:

View File

@@ -0,0 +1,436 @@
# Domain Research Step 5: Research Synthesis and Completion
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without web search verification
- ✅ ALWAYS use {{current_year}} web searches for current domain data
- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator
- 💬 FOCUS on comprehensive synthesis and authoritative conclusions
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
## 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 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:**
`WebSearch: "{{research_topic}} significance importance {{current_year}}"`
### 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_year}} 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 in {{current_year}}]
_Why this research matters now: [Strategic importance with {{current_year}} context]_
_Source: [URL with {{current_year}} industry significance data]_
### 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_year}} 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_year}} data]
_Market Size: [Current market valuation]_
_Growth Rate: [CAGR and projections]_
_Market Drivers: [Key growth factors]_
_Source: [URL with {{current_year}} market data]_
### 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 with {{current_year}} industry structure data]_
## 3. Technology Landscape and Innovation Trends
### Current Technology Adoption
[Technology trends analysis from step-04 with {{current_year}} context]
_Emerging Technologies: [Key technologies affecting {{research_topic}}]_
_Adoption Patterns: [Technology adoption rates and patterns]_
_Innovation Drivers: [Factors driving technology change]_
_Source: [URL with {{current_year}} technology data]_
### 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 with {{current_year}} digital transformation data]_
## 4. Regulatory Framework and Compliance Requirements
### Current Regulatory Landscape
[Regulatory analysis from step-03 with {{current_year}} updates]
_Key Regulations: [Critical regulatory requirements]_
_Compliance Standards: [Industry standards and best practices]_
_Recent Changes: [{{current_year}} regulatory updates and implications]_
_Source: [URL with {{current_year}} regulatory data]_
### 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 with {{current_year}} compliance data]_
## 5. Competitive Landscape and Ecosystem Analysis
### Market Positioning and Key Players
[Competitive analysis with {{current_year}} market positioning]
_Market Leaders: [Dominant players and strategies]_
_Emerging Competitors: [New entrants and innovative approaches]_
_Competitive Dynamics: [Market competition patterns and trends]_
_Source: [URL with {{current_year}} competitive data]_
### 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 with {{current_year}} ecosystem data]_
## 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 with {{current_year}} strategic analysis data]_
### 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 with {{current_year}} opportunity data]_
## 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 with {{current_year}} implementation data]_
### 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 with {{current_year}} risk management data]_
## 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 with {{current_year}} future outlook data]_
### 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 with {{current_year}} strategic planning data]_
## 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]_
_Data Currency: [All data verified for {{current_year}} currency]_
### 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:** {{current_year}} comprehensive analysis
**Document Length:** As needed for comprehensive coverage
**Source Verification:** All facts cited with {{current_year}} 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 {{current_year}} 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
- {{current_year}} data throughout with proper citations
**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 {{current_year}} 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
❌ Not using {{current_year}} sources for all factual claims
❌ Producing document without professional structure
❌ Not presenting completion option for final document
## 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 with {{current_year}} verification
Congratulations on completing comprehensive domain research with professional documentation! 🎉

View File

@@ -20,29 +20,47 @@
- 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 with current {{current_year}} data
- Web search capabilities with source verification are enabled
## YOUR TASK:
Conduct comprehensive market analysis using current {{current_year}} web data with rigorous source verification.
Initialize market research scope and approach for the already-identified topic: **{{research_topic}}** with goals: {{research_goals}}
## MARKET ANALYSIS SEQUENCE:
### 1. Begin Market Analysis
### 1. Initialize Market Research
Start with market research approach:
"I'll conduct comprehensive **market analysis** using current {{current_year}} web data with rigorous source verification.
Start with market-specific positioning:
"I'll guide you through **market research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
**Market Analysis Focus:**
**Research Goals Identified:** {{research_goals}}
- Market size and growth projections
- Customer segments and demographics
- Competitive landscape analysis
- Pricing strategies and business models
- Market trends and consumer behavior
**Market Research Focus for {{research_topic}}:**
**Let me search for current market data.**"
- Market size and growth projections for {{research_topic}}
- Customer segments and demographics interested in {{research_topic}}
- Competitive landscape analysis in {{research_topic}} market
- Pricing strategies and business models for {{research_topic}}
- Market trends and consumer behavior around {{research_topic}}
Let me refine the market research scope specifically for **{{research_topic}}**:
### 2. Establish Market Research Context
#### Market Context Questions:
- "What specific market aspects of {{research_topic}} are most critical for your goals?"
- "Are there particular customer segments or demographics within {{research_topic}} we should focus on?"
- "Should we analyze the global {{research_topic}} market or specific regions?"
- "What time horizon for {{research_topic}} market research - current state or future projections?"
- "How comprehensive should the {{research_topic}} competitive analysis be?"
### 3. Begin Market Research Execution
After scope refinement, proceed with:
### 2. Generate Market Analysis Content

View File

@@ -31,6 +31,8 @@ Conduct comprehensive customer insights analysis using current {{current_year}}
### 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** using current {{current_year}} web data to understand customer behavior and needs.
@@ -43,9 +45,44 @@ Start with customer research approach:
- Customer satisfaction drivers
- Demographic and psychographic profiles
**Let me search for current customer insights.**"
**Let me search for current customer insights using parallel web searches for comprehensive coverage.**"
### 2. Generate Customer Insights Content
### 2. Parallel Customer Research Execution
**Execute multiple web searches simultaneously:**
`WebSearch: "[product/service/market] customer behavior patterns {{current_year}}"`
`WebSearch: "[product/service/market] customer pain points challenges {{current_year}}"`
`WebSearch: "[product/service/market] customer decision process {{current_year}}"`
**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:
@@ -92,7 +129,7 @@ _Source: [URL with {{current_year}} demographic data]_
_Source: [URL with {{current_year}} psychographic data]_
```
### 3. Present Analysis and Continue Option
### 5. Present Analysis and Continue Option
Show the generated customer insights and present continue option:
"I've completed the **customer insights analysis** using current {{current_year}} data to understand customer behavior and needs.
@@ -108,7 +145,7 @@ Show the generated customer insights and present continue option:
**Ready to proceed to competitive analysis?**
[C] Continue - Save this to the document and proceed to competitive analysis
### 4. Handle Continue Selection
### 6. Handle Continue Selection
#### If 'C' (Continue):
@@ -118,7 +155,7 @@ Show the generated customer insights and present continue option:
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 2.
When user selects 'C', append the content directly to the research document using the structure from step 4.
## SUCCESS METRICS:

View File

@@ -15,17 +15,20 @@
- 💾 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
- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
## CONTEXT BOUNDARIES:
- Current document and frontmatter from previous steps are available
- Focus on strategic synthesis and actionable recommendations
- **Research topic = "{{research_topic}}"** - comprehensive market analysis
- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
- All market research sections have been completed (customer insights, competitive analysis)
- Web search capabilities with source verification are enabled
- This is the final step in the market research workflow
- This is the final synthesis step producing the complete market research document
## YOUR TASK:
Conduct comprehensive strategic synthesis using current {{current_year}} web data with emphasis on actionable market research recommendations.
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:
@@ -68,89 +71,316 @@ Search for current risk approaches:
- Regulatory and compliance risks
- Economic and market volatility considerations
### 4. Generate Strategic Synthesis Content
### 4. Generate Complete Market Research Document
Prepare strategic recommendations with web search citations:
Prepare comprehensive market research document with full structure:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
#### Complete Document Structure:
```markdown
## Strategic Synthesis and Recommendations
# [Compelling Title]: Comprehensive {{research_topic}} Market Research
### Key Market Insights Summary
## Executive Summary
[Integrated summary of market research findings with source citations]
_Source: [URL with {{current_year}} strategic data]_
[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 in {{current_year}}]
_Market Importance: [Strategic market significance with {{current_year}} context]_
_Business Impact: [Business implications of market research]_
_Source: [URL with {{current_year}} market significance data]_
### 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_year}} 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 with {{current_year}} data]
_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 with {{current_year}} market size data]_
### 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 with {{current_year}} market trends data]_
### 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 with {{current_year}} pricing data]_
## 3. Customer Insights and Behavior Analysis
### Customer Behavior Patterns
[Customer insights analysis with {{current_year}} context]
_Behavior Patterns: [Key customer behavior trends and patterns]_
_Customer Journey: [Complete customer journey mapping]_
_Decision Factors: [Factors influencing customer decisions]_
_Source: [URL with {{current_year}} customer behavior data]_
### 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 with {{current_year}} customer insights data]_
### 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 with {{current_year}} segmentation data]_
## 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 with {{current_year}} competitive data]_
### 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 with {{current_year}} positioning data]_
## 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 with {{current_year}} market opportunity data]_
### Strategic Recommendations
[Strategic recommendations based on research with source citations]
_Source: [URL with {{current_year}} strategy data]_
[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 with {{current_year}} strategic data]_
### Market Entry or Expansion Strategy
## 6. Market Entry and Growth Strategies
[Market approach strategy with source citations]
### 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 with {{current_year}} market entry data]_
### Competitive Positioning Strategy
### Growth and Scaling Strategy
[Positioning recommendations with source citations]
_Source: [URL with {{current_year}} positioning data]_
[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 with {{current_year}} growth strategy data]_
### Risk Assessment and Mitigation
## 7. Risk Assessment and Mitigation
[Risk analysis and mitigation strategies with source citations]
_Source: [URL with {{current_year}} risk data]_
### Market Risk Analysis
### Implementation Roadmap
[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 with {{current_year}} risk assessment data]_
[Actionable implementation plan with source citations]
### 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 with {{current_year}} mitigation data]_
## 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 with {{current_year}} implementation data]_
### Success Metrics and KPIs
[Success measurement framework with source citations]
[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 with {{current_year}} metrics data]_
## Market Research Summary
## 9. Future Market Outlook and Opportunities
### Research Methodology
### Future Market Trends
[Summary of research approach and sources]
[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 with {{current_year}} future trends data]_
### Key Findings Recap
### Strategic Opportunities
[Brief recap of all research findings]
[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 with {{current_year}} opportunity data]_
### Limitations and Considerations
## 10. Market Research Methodology and Source Verification
[Research limitations and additional considerations]
### 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 Data Currency: [All market data verified for {{current_year}} currency]_
### 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_year}} comprehensive market analysis
**Document Length:** As needed for comprehensive market coverage
**Source Verification:** All market facts cited with {{current_year}} 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 Analysis and Complete Option
### 5. Present Complete Market Research Document and Final Option
Show the generated strategic synthesis and present complete option:
"I've completed the **market research strategic synthesis** using current {{current_year}} data, finalizing our comprehensive market research.
**Market Research Document Completion Presentation:**
**Strategic Highlights:**
"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
- Integrated market insights synthesized from all research phases
- Strategic recommendations grounded in current market data
- Market entry and positioning strategies developed
- Risk assessment and mitigation approaches documented
- Actionable implementation roadmap provided
**Document Features:**
**This completes our market research covering:**
- **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_year}} sources
- Market size, growth, and dynamics analysis
- Customer behavior and insights profiling
- Competitive landscape and positioning analysis
- Strategic recommendations and implementation guidance
**Market Research Completeness:**
**Ready to complete the market research report?**
[C] Complete Research - Save final document and conclude
- 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_year}} 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
@@ -166,23 +396,26 @@ When user selects 'C', append the content directly to the research document usin
## SUCCESS METRICS:
Strategic insights synthesized with current {{current_year}} citations
Strategic recommendations grounded in research findings
Market entry/positioning strategies clearly documented
Risk assessment and mitigation approaches provided
Implementation roadmap with actionable steps
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_year}} citations
✅ Professional market document structure and compelling narrative
✅ [C] complete option presented and handled correctly
Content properly appended to document when C selected
✅ Market research workflow completed successfully
Market research workflow completed with comprehensive document
## FAILURE MODES:
❌ Not using {{current_year}} in strategic web searches
Not synthesizing insights from all research phases
Missing actionable strategic recommendations
❌ Not providing implementation guidance
Not presenting completion option for research workflow
Appending content without user selecting 'C'
❌ 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
Not using {{current_year}} market sources for all factual claims
❌ Producing market document without professional structure
❌ Not presenting completion option for final market document
## STRATEGIC RESEARCH PROTOCOLS:
@@ -192,23 +425,44 @@ When user selects 'C', append the content directly to the research document usin
- 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
- All market research steps completed (1-4)
- Comprehensive market research document generated
- All sections appended with source citations
- Market research workflow status updated
- Final strategic recommendations provided to user
- 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_year}} verification
## NEXT STEPS:
Market research workflow complete. User may:
Comprehensive market research workflow complete. User may:
- Use market research to inform product development strategies
- Conduct additional research on specific market segments
- 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 product development based on market insights
- Move forward with implementation based on strategic market recommendations
Congratulations on completing comprehensive market research with current {{current_year}} data! 🎉
Congratulations on completing comprehensive market research with professional documentation! 🎉

View File

@@ -0,0 +1,203 @@
# Technical Research Step 1: Technical Initialization
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
- ✅ ALWAYS use {{current_year}} web searches for current technical data
- 📋 YOU ARE A TECHNICAL ANALYST, not content generator
- 💬 FOCUS on technical architecture and implementation patterns
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
## EXECUTION PROTOCOLS:
- 🎯 Show web search analysis before presenting findings
- ⚠️ Present [C] continue option after technical overview content generation
- 💾 ONLY save when user chooses C (Continue)
- 📖 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 = "technical" is already set
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
- **Research goals = "{{research_goals}}"** - captured from initial discussion
- Focus on technical research with current {{current_year}} data
- Web search capabilities with source verification are enabled
## YOUR TASK:
Initialize technical research scope and approach for the already-identified topic: **{{research_topic}}** with goals: {{research_goals}}
## TECHNICAL OVERVIEW SEQUENCE:
### 1. Initialize Technical Research
Start with technical-specific positioning:
"I'll guide you through **technical research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
**Research Goals Identified:** {{research_goals}}
**Technical Research Focus for {{research_topic}}:**
- Technical architecture patterns and frameworks relevant to {{research_topic}}
- Implementation approaches and best practices for {{research_topic}}
- Technology stack evolution and trends affecting {{research_topic}}
- Integration patterns and interoperability for {{research_topic}}
- Performance and scalability considerations for {{research_topic}}
Let me refine the technical research scope specifically for **{{research_topic}}**:
### 2. Establish Technical Research Context
#### Technical Context Questions:
- "What technical aspects of {{research_topic}} are most critical for your goals?"
- "Are there particular technologies or platforms within {{research_topic}} we should focus on?"
- "Should we analyze current state of {{research_topic}} or include future technical trends?"
- "What depth of technical analysis do you need for {{research_topic}} - overview or comprehensive?"
- "Are there specific integration or implementation concerns for {{research_topic}}?"
### 3. Begin Technical Research Execution
After scope refinement, proceed with:
### 2. Web Search for Technical Architecture
Search for current architecture patterns:
`WebSearch: "[technology/domain] architecture patterns frameworks {{current_year}}"`
**Architecture focus:**
- Current architectural patterns and design principles
- Frameworks and platforms commonly used
- Microservices, monolith, and hybrid approaches
- Cloud-native and edge computing patterns
### 3. Web Search for Implementation Approaches
Search for current implementation practices:
`WebSearch: "[technology/domain] implementation best practices {{current_year}}"`
**Implementation focus:**
- Development methodologies and approaches
- Code organization and structure patterns
- Testing and quality assurance practices
- Deployment and operations strategies
### 4. Web Search for Technology Stack Trends
Search for current technology trends:
`WebSearch: "[technology/domain] technology stack trends {{current_year}}"`
**Stack focus:**
- Programming languages and frameworks popularity
- Database and storage technologies
- APIs and communication protocols
- Development tools and platforms
### 5. Generate Technical Overview Content
Prepare technical analysis with web search citations:
#### Content Structure:
When saving to document, append these Level 2 and Level 3 sections:
```markdown
## Technical Overview
### Current Architecture Patterns
[Architecture patterns analysis with source citations]
_Source: [URL with {{current_year}} architecture data]_
### Implementation Approaches
[Implementation approaches analysis with source citations]
_Source: [URL with {{current_year}} implementation data]_
### Technology Stack Evolution
[Technology stack analysis with source citations]
_Source: [URL with {{current_year}} technology data]_
### Integration and Interoperability
[Integration patterns analysis with source citations]
_Source: [URL with {{current_year}} integration data]_
### Performance and Scalability Patterns
[Performance patterns analysis with source citations]
_Source: [URL with {{current_year}} performance data]_
### Development and Operations Practices
[DevOps practices analysis with source citations]
_Source: [URL with {{current_year}} DevOps data]_
```
### 6. Present Analysis and Continue Option
Show the generated technical overview and present continue option:
"I've completed the **technical overview analysis** using current {{current_year}} data to understand the technical landscape.
**Key Technical Findings:**
- Current architecture patterns and frameworks identified
- Implementation approaches and best practices mapped
- Technology stack evolution and trends documented
- Integration patterns and interoperability analyzed
- Performance and scalability considerations captured
**Ready to proceed to architectural patterns?**
[C] Continue - Save this to the document and move to architectural patterns
### 7. Handle Continue Selection
#### If 'C' (Continue):
- Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1]`
- Load: `./step-02-technical-overview.md`
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 5.
## SUCCESS METRICS:
✅ Architecture patterns identified with current {{current_year}} citations
✅ Implementation approaches clearly documented
✅ Technology stack evolution thoroughly analyzed
✅ Integration patterns and interoperability mapped
✅ Performance and scalability considerations captured
✅ [C] continue option presented and handled correctly
✅ Content properly appended to document when C selected
✅ Proper routing to architectural patterns step
## FAILURE MODES:
❌ Not using {{current_year}} in technical web searches
❌ Missing critical architecture patterns or frameworks
❌ Not identifying current implementation best practices
❌ Incomplete technology stack evolution analysis
❌ Not presenting [C] continue option after content generation
❌ Appending content without user selecting 'C'
## TECHNICAL RESEARCH PROTOCOLS:
- Search for technical documentation and architecture guides
- Use industry technical publications and conference proceedings
- Research open-source projects and their architectures
- Note technology adoption patterns and migration trends
- Research performance benchmarking and optimization techniques
## NEXT STEP:
After user selects 'C', load `./step-02-technical-overview.md` to focus on specific architectural patterns and design decisions.
Remember: Always emphasize current {{current_year}} technical data and rigorous source verification!

View File

@@ -31,6 +31,8 @@ Conduct comprehensive technical overview using current {{current_year}} web data
### 1. Begin Technical Overview
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technical areas simultaneously and thoroughly
Start with technical research approach:
"Now I'll conduct **technical overview analysis** using current {{current_year}} web data to understand the technical landscape for [technology/domain].
@@ -42,45 +44,43 @@ Start with technical research approach:
- Integration patterns and interoperability
- Performance and scalability considerations
**Let me search for current technical landscape information.**"
**Let me search for current technical landscape information using parallel web searches for comprehensive coverage.**"
### 2. Web Search for Technical Architecture
### 2. Parallel Technical Research Execution
**Execute multiple web searches simultaneously:**
Search for current architecture patterns:
`WebSearch: "[technology/domain] architecture patterns frameworks {{current_year}}"`
**Architecture focus:**
- Current architectural patterns and design principles
- Frameworks and platforms commonly used
- Microservices, monolith, and hybrid approaches
- Cloud-native and edge computing patterns
### 3. Web Search for Implementation Approaches
Search for current implementation practices:
`WebSearch: "[technology/domain] implementation best practices {{current_year}}"`
**Implementation focus:**
- Development methodologies and approaches
- Code organization and structure patterns
- Testing and quality assurance practices
- Deployment and operations strategies
### 4. Web Search for Technology Stack Trends
Search for current technology trends:
`WebSearch: "[technology/domain] technology stack trends {{current_year}}"`
**Stack focus:**
**Analysis approach:**
- Programming languages and frameworks popularity
- Database and storage technologies
- APIs and communication protocols
- Development tools and platforms
- Look for recent technical documentation and architecture guides
- Search for technical publications and conference proceedings
- Research open-source projects and their architectures
- Note technology adoption patterns and migration trends
- Research performance benchmarking and optimization techniques
### 5. Generate Technical Overview Content
### 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 technical findings:
**Research Coverage:**
- Architecture patterns and design principles
- Implementation approaches and methodologies
- Technology stack evolution and current trends
**Technical Integration Analysis:**
[Identify how architecture patterns influence implementation approaches and technology choices]
**Quality Assessment:**
[Overall confidence levels and research gaps identified]"
### 4. Generate Technical Overview Content
Prepare technical analysis with web search citations:
@@ -122,7 +122,7 @@ _Source: [URL with {{current_year}} performance data]_
_Source: [URL with {{current_year}} DevOps data]_
```
### 6. Present Analysis and Continue Option
### 5. Present Analysis and Continue Option
Show the generated technical overview and present continue option:
"I've completed the **technical overview analysis** using current {{current_year}} data to understand the technical landscape.
@@ -138,7 +138,7 @@ Show the generated technical overview and present continue option:
**Ready to proceed to architectural patterns?**
[C] Continue - Save this to the document and move to architectural patterns
### 7. Handle Continue Selection
### 6. Handle Continue Selection
#### If 'C' (Continue):
@@ -148,7 +148,7 @@ Show the generated technical overview and present continue option:
## APPEND TO DOCUMENT:
When user selects 'C', append the content directly to the research document using the structure from step 5.
When user selects 'C', append the content directly to the research document using the structure from step 4.
## SUCCESS METRICS:

View File

@@ -0,0 +1,479 @@
# Technical Research Step 5: Technical Synthesis and Completion
## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without web search verification
- ✅ ALWAYS use {{current_year}} web searches for current technical data
- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
## 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:**
`WebSearch: "{{research_topic}} technical significance importance {{current_year}}"`
### 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_year}} 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 in {{current_year}}]
_Technical Importance: [Strategic technical significance with {{current_year}} context]_
_Business Impact: [Business implications of technical research]_
_Source: [URL with {{current_year}} technical significance data]_
### 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_year}} 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_year}} context]
_Dominant Patterns: [Current architectural approaches]_
_Architectural Evolution: [Historical and current evolution patterns]_
_Architectural Trade-offs: [Key architectural decisions and implications]_
_Source: [URL with {{current_year}} architectural data]_
### 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 with {{current_year}} design principles data]_
## 3. Implementation Approaches and Best Practices
### Current Implementation Methodologies
[Implementation analysis from step-04 with {{current_year}} 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 with {{current_year}} implementation data]_
### 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 with {{current_year}} framework data]_
## 4. Technology Stack Evolution and Current Trends
### Current Technology Stack Landscape
[Technology stack analysis from step-02 with {{current_year}} 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 with {{current_year}} technology stack data]_
### 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 with {{current_year}} adoption data]_
## 5. Integration and Interoperability Patterns
### Current Integration Approaches
[Integration patterns analysis with {{current_year}} 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 with {{current_year}} integration data]_
### 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 with {{current_year}} interoperability data]_
## 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 with {{current_year}} performance data]_
### 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 with {{current_year}} scalability data]_
## 7. Security and Compliance Considerations
### Security Best Practices and Frameworks
[Security analysis with {{current_year}} 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 with {{current_year}} security data]_
### 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 with {{current_year}} compliance data]_
## 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 with {{current_year}} technical strategy data]_
### 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 with {{current_year}} competitive analysis data]_
## 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 with {{current_year}} implementation planning data]_
### 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 with {{current_year}} technical risk data]_
## 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 with {{current_year}} future trends data]_
### 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 with {{current_year}} innovation data]_
## 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 Data Currency: [All technical data verified for {{current_year}} currency]_
### 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_year}} comprehensive technical analysis
**Document Length:** As needed for comprehensive technical coverage
**Source Verification:** All technical facts cited with {{current_year}} 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_year}} 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_year}} 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_year}} 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
❌ Not using {{current_year}} technical sources for all factual claims
❌ Producing technical document without professional structure
❌ Not presenting completion option for final technical document
## 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_year}} verification
Congratulations on completing comprehensive technical research with professional documentation! 🎉

View File

@@ -5,10 +5,25 @@ description: Conduct comprehensive research across multiple domains using curren
# Research Workflow
**Goal:** Conduct comprehensive research across multiple domains using current web data and verified sources
**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 cited with URLs from {{current_year}}
- **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
@@ -82,46 +97,82 @@ Execute research type discovery and routing:
"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with current {{current_year}} data and rigorous source verification, while you bring the domain expertise and research direction.
\*\*What would you like to research today?"
**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
Listen for research type indicators and present options:
After understanding the research topic and goals, identify the most appropriate research approach:
**Research Options:**
**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
4. **Deep Research Prompt** - Creating structured research prompts for AI platforms
_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
Based on user selection, route to appropriate sub-workflow:
Based on user selection, route to appropriate sub-workflow with the discovered topic:
#### If Market Research:
- Set `research_type = "market"`
- Set output file: `{output_folder}/analysis/research/market-{{topic}}-research-{{date}}.md`
- Load: `./market-steps/step-01-init.md`
- Set `research_topic = [discovered topic from discussion]`
- Set output file: `{output_folder}/analysis/research/market-{{research_topic}}-research-{{date}}.md`
- Load: `./market-steps/step-01-init.md` with topic context
#### If Domain Research:
- Set `research_type = "domain"`
- Set output file: `{output_folder}/analysis/research/domain-{{topic}}-research-{{date}}.md`
- Load: `./domain-steps/step-01-init.md`
- Set `research_topic = [discovered topic from discussion]`
- Set output file: `{output_folder}/analysis/research/domain-{{research_topic}}-research-{{date}}.md`
- Load: `./domain-steps/step-01-init.md` with topic context
#### If Technical Research:
- Set `research_type = "technical"`
- Set output file: `{output_folder}/analysis/research/technical-{{topic}}-research-{{date}}.md`
- Load: `./technical-steps/step-01-init.md`
- Set `research_topic = [discovered topic from discussion]`
- Set output file: `{output_folder}/analysis/research/technical-{{research_topic}}-research-{{date}}.md`
- Load: `./technical-steps/step-01-init.md` with topic context
#### If Deep Research Prompt:
- Set `research_type = "deep-prompt"`
- Set output file: `{output_folder}/analysis/research/deep-prompt-{{topic}}-research-{{date}}.md`
- Load: `./deep-prompt-steps/step-01-init.md`
**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.
### Document Initialization
@@ -134,6 +185,8 @@ inputDocuments: []
workflowType: 'research'
lastStep: 1
research_type: '{{research_type}}'
research_topic: '{{research_topic}}'
research_goals: '{{research_goals}}'
user_name: '{{user_name}}'
date: '{{date}}'
current_year: '{{current_year}}'

View File

@@ -1,3 +1,8 @@
---
name: PRD Workflow
description: Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.
---
# PRD Workflow
**Goal:** Create comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.

View File

@@ -28,6 +28,7 @@ phases:
optional: true
agent: "analyst"
command: "brainstorm-project"
note: "Uses core brainstorming workflow with project context template"
included_by: "user_choice"
- id: "research"

View File

@@ -16,6 +16,7 @@ phases:
optional: true
agent: "analyst"
command: "brainstorm-project"
note: "Uses core brainstorming workflow with project context template"
included_by: "user_choice"
- id: "research"

View File

@@ -29,6 +29,7 @@ phases:
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
note: "Uses core brainstorming workflow with project context template"
- id: "research"
optional: true

View File

@@ -17,6 +17,7 @@ phases:
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
note: "Uses core brainstorming workflow with project context template"
- id: "research"
optional: true