fix: ChatBubble crash and DeepSeek API compatibility
- Fix ChatBubble to handle non-string content with String() wrapper - Fix API route to use generateText for non-streaming requests - Add @ai-sdk/openai-compatible for non-OpenAI providers (DeepSeek, etc.) - Use Chat Completions API instead of Responses API for compatible providers - Update ChatBubble tests and fix component exports to kebab-case - Remove stale PascalCase ChatBubble.tsx file
This commit is contained in:
Max
@@ -0,0 +1,137 @@
|
||||
# Technical Research Step 1: Technical Research Scope Confirmation
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user confirmation
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ FOCUS EXCLUSIVELY on confirming technical research scope and approach
|
||||
- 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator
|
||||
- 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals
|
||||
- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- ⚠️ Present [C] continue option after scope confirmation
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Research type = "technical" is already set
|
||||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on technical architecture and implementation research
|
||||
- Web search is required to verify and supplement your knowledge with current facts
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Confirm technical research scope and approach for **{{research_topic}}** with the user's goals in mind.
|
||||
|
||||
## TECHNICAL SCOPE CONFIRMATION:
|
||||
|
||||
### 1. Begin Scope Confirmation
|
||||
|
||||
Start with technical scope understanding:
|
||||
"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
|
||||
|
||||
**Technical Research Scope:**
|
||||
|
||||
- **Architecture Analysis**: System design patterns, frameworks, and architectural decisions
|
||||
- **Implementation Approaches**: Development methodologies, coding patterns, and best practices
|
||||
- **Technology Stack**: Languages, frameworks, tools, and platforms relevant to {{research_topic}}
|
||||
- **Integration Patterns**: APIs, communication protocols, and system interoperability
|
||||
- **Performance Considerations**: Scalability, optimization, and performance patterns
|
||||
|
||||
**Research Approach:**
|
||||
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence levels for uncertain technical information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
||||
### 2. Scope Confirmation
|
||||
|
||||
Present clear scope confirmation:
|
||||
"**Technical Research Scope Confirmation:**
|
||||
|
||||
For **{{research_topic}}**, I will research:
|
||||
|
||||
✅ **Architecture Analysis** - design patterns, frameworks, system architecture
|
||||
✅ **Implementation Approaches** - development methodologies, coding patterns
|
||||
✅ **Technology Stack** - languages, frameworks, tools, platforms
|
||||
✅ **Integration Patterns** - APIs, protocols, interoperability
|
||||
✅ **Performance Considerations** - scalability, optimization, patterns
|
||||
|
||||
**All claims verified against current public sources.**
|
||||
|
||||
**Does this technical research scope and approach align with your goals?**
|
||||
[C] Continue - Begin technical research with this scope
|
||||
|
||||
### 3. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-technical-overview.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append scope confirmation:
|
||||
|
||||
```markdown
|
||||
## Technical Research Scope Confirmation
|
||||
|
||||
**Research Topic:** {{research_topic}}
|
||||
**Research Goals:** {{research_goals}}
|
||||
|
||||
**Technical Research Scope:**
|
||||
|
||||
- Architecture Analysis - design patterns, frameworks, system architecture
|
||||
- Implementation Approaches - development methodologies, coding patterns
|
||||
- Technology Stack - languages, frameworks, tools, platforms
|
||||
- Integration Patterns - APIs, protocols, interoperability
|
||||
- Performance Considerations - scalability, optimization, patterns
|
||||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence level framework for uncertain information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
||||
**Scope Confirmed:** {{date}}
|
||||
```
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Technical research scope clearly confirmed with user
|
||||
✅ All technical analysis areas identified and explained
|
||||
✅ Research methodology emphasized
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Scope confirmation documented when user proceeds
|
||||
✅ Proper routing to next technical research step
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not clearly confirming technical research scope with user
|
||||
❌ Missing critical technical analysis areas
|
||||
❌ Not explaining that web search is required for current facts
|
||||
❌ Not presenting [C] continue option
|
||||
❌ Proceeding without user scope confirmation
|
||||
❌ Not routing to next technical research step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-technical-overview.md` to begin technology stack analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!
|
||||
@@ -0,0 +1,239 @@
|
||||
# Technical Research Step 2: Technology Stack Analysis
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
|
||||
- 💬 FOCUS on languages, frameworks, tools, and platforms
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after technology stack content generation
|
||||
- 📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from step-01 are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on languages, frameworks, tools, and platforms
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms. Search the web to verify and supplement current facts.
|
||||
|
||||
## TECHNOLOGY STACK ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Technology Stack Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
|
||||
|
||||
Start with technology stack research approach:
|
||||
"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
|
||||
|
||||
**Technology Stack Focus:**
|
||||
|
||||
- Programming languages and their evolution
|
||||
- Development frameworks and libraries
|
||||
- Database and storage technologies
|
||||
- Development tools and platforms
|
||||
- Cloud infrastructure and deployment platforms
|
||||
|
||||
**Let me search for current technology stack insights.**"
|
||||
|
||||
### 2. Parallel Technology Stack Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} programming languages frameworks"
|
||||
Search the web: "{{research_topic}} development tools platforms"
|
||||
Search the web: "{{research_topic}} database storage technologies"
|
||||
Search the web: "{{research_topic}} cloud infrastructure platforms"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent technology trend reports and developer surveys
|
||||
- Search for technology documentation and best practices
|
||||
- Research open-source projects and their technology choices
|
||||
- Analyze technology adoption patterns and migration trends
|
||||
- Study platform and tool evolution in the domain
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- Programming languages and frameworks analysis
|
||||
- Development tools and platforms evaluation
|
||||
- Database and storage technologies assessment
|
||||
- Cloud infrastructure and deployment platform analysis
|
||||
|
||||
**Cross-Technology Analysis:**
|
||||
[Identify patterns connecting language choices, frameworks, and platform decisions]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Technology Stack Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare technology stack analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Technology Stack Analysis
|
||||
|
||||
### Programming Languages
|
||||
|
||||
[Programming languages analysis with source citations]
|
||||
_Popular Languages: [Most widely used languages for {{research_topic}}]_
|
||||
_Emerging Languages: [Growing languages gaining adoption]_
|
||||
_Language Evolution: [How language preferences are changing]_
|
||||
_Performance Characteristics: [Language performance and suitability]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Frameworks and Libraries
|
||||
|
||||
[Frameworks analysis with source citations]
|
||||
_Major Frameworks: [Dominant frameworks and their use cases]_
|
||||
_Micro-frameworks: [Lightweight options and specialized libraries]_
|
||||
_Evolution Trends: [How frameworks are evolving and changing]_
|
||||
_Ecosystem Maturity: [Library availability and community support]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Database and Storage Technologies
|
||||
|
||||
[Database analysis with source citations]
|
||||
_Relational Databases: [Traditional SQL databases and their evolution]_
|
||||
_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
|
||||
_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
|
||||
_Data Warehousing: [Analytics and big data storage solutions]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Tools and Platforms
|
||||
|
||||
[Tools and platforms analysis with source citations]
|
||||
_IDE and Editors: [Development environments and their evolution]_
|
||||
_Version Control: [Git and related development tools]_
|
||||
_Build Systems: [Compilation, packaging, and automation tools]_
|
||||
_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Cloud Infrastructure and Deployment
|
||||
|
||||
[Cloud platforms analysis with source citations]
|
||||
_Major Cloud Providers: [AWS, Azure, GCP and their services]_
|
||||
_Container Technologies: [Docker, Kubernetes, and orchestration]_
|
||||
_Serverless Platforms: [FaaS and event-driven computing]_
|
||||
_CDN and Edge Computing: [Content delivery and distributed computing]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Trends
|
||||
|
||||
[Adoption trends analysis with source citations]
|
||||
_Migration Patterns: [How technology choices are evolving]_
|
||||
_Emerging Technologies: [New technologies gaining traction]_
|
||||
_Legacy Technology: [Older technologies being phased out]_
|
||||
_Community Trends: [Developer preferences and open-source adoption]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
|
||||
|
||||
**Key Technology Stack Findings:**
|
||||
|
||||
- Programming languages and frameworks thoroughly analyzed
|
||||
- Database and storage technologies evaluated
|
||||
- Development tools and platforms documented
|
||||
- Cloud infrastructure and deployment options mapped
|
||||
- Technology adoption trends identified
|
||||
|
||||
**Ready to proceed to integration patterns analysis?**
|
||||
[C] Continue - Save this to document and proceed to integration patterns
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-integration-patterns.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Programming languages and frameworks thoroughly analyzed
|
||||
✅ Database and storage technologies evaluated
|
||||
✅ Development tools and platforms documented
|
||||
✅ Cloud infrastructure and deployment options mapped
|
||||
✅ Technology adoption trends identified
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (integration patterns)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical programming languages or frameworks
|
||||
❌ Incomplete database and storage technology analysis
|
||||
❌ Not identifying development tools and platforms
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to integration patterns step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## TECHNOLOGY STACK RESEARCH PROTOCOLS:
|
||||
|
||||
- Research technology trend reports and developer surveys
|
||||
- Use technology documentation and best practices guides
|
||||
- Analyze open-source projects and their technology choices
|
||||
- Study technology adoption patterns and migration trends
|
||||
- Focus on current technology data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## TECHNOLOGY STACK ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative technology research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable technology insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current technology data with rigorous source verification!
|
||||
@@ -0,0 +1,248 @@
|
||||
# Technical Research Step 3: Integration Patterns
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator
|
||||
- 💬 FOCUS on APIs, protocols, and system interoperability
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after integration patterns content generation
|
||||
- 📝 WRITE INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on APIs, protocols, and system interoperability
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability. Search the web to verify and supplement current facts.
|
||||
|
||||
## INTEGRATION PATTERNS ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Integration Patterns Analysis
|
||||
|
||||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
|
||||
|
||||
Start with integration patterns research approach:
|
||||
"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
|
||||
|
||||
**Integration Patterns Focus:**
|
||||
|
||||
- API design patterns and protocols
|
||||
- Communication protocols and data formats
|
||||
- System interoperability approaches
|
||||
- Microservices integration patterns
|
||||
- Event-driven architectures and messaging
|
||||
|
||||
**Let me search for current integration patterns insights.**"
|
||||
|
||||
### 2. Parallel Integration Patterns Research Execution
|
||||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
Search the web: "{{research_topic}} API design patterns protocols"
|
||||
Search the web: "{{research_topic}} communication protocols data formats"
|
||||
Search the web: "{{research_topic}} system interoperability integration"
|
||||
Search the web: "{{research_topic}} microservices integration patterns"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
- Look for recent API design guides and best practices
|
||||
- Search for communication protocol documentation and standards
|
||||
- Research integration platform and middleware solutions
|
||||
- Analyze microservices architecture patterns and approaches
|
||||
- Study event-driven systems and messaging patterns
|
||||
|
||||
### 3. Analyze and Aggregate Results
|
||||
|
||||
**Collect and analyze findings from all parallel searches:**
|
||||
|
||||
"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
|
||||
|
||||
**Research Coverage:**
|
||||
|
||||
- API design patterns and protocols analysis
|
||||
- Communication protocols and data formats evaluation
|
||||
- System interoperability approaches assessment
|
||||
- Microservices integration patterns documentation
|
||||
|
||||
**Cross-Integration Analysis:**
|
||||
[Identify patterns connecting API choices, communication protocols, and system design]
|
||||
|
||||
**Quality Assessment:**
|
||||
[Overall confidence levels and research gaps identified]"
|
||||
|
||||
### 4. Generate Integration Patterns Content
|
||||
|
||||
**WRITE IMMEDIATELY TO DOCUMENT**
|
||||
|
||||
Prepare integration patterns analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Integration Patterns Analysis
|
||||
|
||||
### API Design Patterns
|
||||
|
||||
[API design patterns analysis with source citations]
|
||||
_RESTful APIs: [REST principles and best practices for {{research_topic}}]_
|
||||
_GraphQL APIs: [GraphQL adoption and implementation patterns]_
|
||||
_RPC and gRPC: [High-performance API communication patterns]_
|
||||
_Webhook Patterns: [Event-driven API integration approaches]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Communication Protocols
|
||||
|
||||
[Communication protocols analysis with source citations]
|
||||
_HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_
|
||||
_WebSocket Protocols: [Real-time communication and persistent connections]_
|
||||
_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_
|
||||
_grpc and Protocol Buffers: [High-performance binary communication protocols]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Formats and Standards
|
||||
|
||||
[Data formats analysis with source citations]
|
||||
_JSON and XML: [Structured data exchange formats and their evolution]_
|
||||
_Protobuf and MessagePack: [Efficient binary serialization formats]_
|
||||
_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_
|
||||
_Custom Data Formats: [Domain-specific data exchange standards]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Interoperability Approaches
|
||||
|
||||
[Interoperability analysis with source citations]
|
||||
_Point-to-Point Integration: [Direct system-to-system communication patterns]_
|
||||
_API Gateway Patterns: [Centralized API management and routing]_
|
||||
_Service Mesh: [Service-to-service communication and observability]_
|
||||
_Enterprise Service Bus: [Traditional enterprise integration patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Microservices Integration Patterns
|
||||
|
||||
[Microservices integration analysis with source citations]
|
||||
_API Gateway Pattern: [External API management and routing]_
|
||||
_Service Discovery: [Dynamic service registration and discovery]_
|
||||
_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_
|
||||
_Saga Pattern: [Distributed transaction management]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Event-Driven Integration
|
||||
|
||||
[Event-driven analysis with source citations]
|
||||
_Publish-Subscribe Patterns: [Event broadcasting and subscription models]_
|
||||
_Event Sourcing: [Event-based state management and persistence]_
|
||||
_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_
|
||||
_CQRS Patterns: [Command Query Responsibility Segregation]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration Security Patterns
|
||||
|
||||
[Security patterns analysis with source citations]
|
||||
_OAuth 2.0 and JWT: [API authentication and authorization patterns]_
|
||||
_API Key Management: [Secure API access and key rotation]_
|
||||
_Mutual TLS: [Certificate-based service authentication]_
|
||||
_Data Encryption: [Secure data transmission and storage]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
|
||||
|
||||
**Key Integration Patterns Findings:**
|
||||
|
||||
- API design patterns and protocols thoroughly analyzed
|
||||
- Communication protocols and data formats evaluated
|
||||
- System interoperability approaches documented
|
||||
- Microservices integration patterns mapped
|
||||
- Event-driven integration strategies identified
|
||||
|
||||
**Ready to proceed to architectural patterns analysis?**
|
||||
[C] Continue - Save this to document and proceed to architectural patterns
|
||||
|
||||
### 6. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-architectural-patterns.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
Content is already written to document when generated in step 4. No additional append needed.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ API design patterns and protocols thoroughly analyzed
|
||||
✅ Communication protocols and data formats evaluated
|
||||
✅ System interoperability approaches documented
|
||||
✅ Microservices integration patterns mapped
|
||||
✅ Event-driven integration strategies identified
|
||||
✅ Content written immediately to document
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Proper routing to next step (architectural patterns)
|
||||
✅ Research goals alignment maintained
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical API design patterns or protocols
|
||||
❌ Incomplete communication protocols analysis
|
||||
❌ Not identifying system interoperability approaches
|
||||
❌ Not writing content immediately to document
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Not routing to architectural patterns step
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## INTEGRATION PATTERNS RESEARCH PROTOCOLS:
|
||||
|
||||
- Research API design guides and best practices documentation
|
||||
- Use communication protocol specifications and standards
|
||||
- Analyze integration platform and middleware solutions
|
||||
- Study microservices architecture patterns and case studies
|
||||
- Focus on current integration data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
## INTEGRATION PATTERNS ANALYSIS STANDARDS:
|
||||
|
||||
- Always cite URLs for web search results
|
||||
- Use authoritative integration research sources
|
||||
- Note data currency and potential limitations
|
||||
- Present multiple perspectives when sources conflict
|
||||
- Apply confidence levels to uncertain data
|
||||
- Focus on actionable integration insights
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current integration data with rigorous source verification!
|
||||
@@ -0,0 +1,202 @@
|
||||
# Technical Research Step 4: Architectural Patterns
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
|
||||
- 💬 FOCUS on architectural patterns and design decisions
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] continue option after architectural patterns content generation
|
||||
- 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
|
||||
- 💾 ONLY proceed when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
||||
- Focus on architectural patterns and design decisions
|
||||
- Web search capabilities with source verification are enabled
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive architectural patterns analysis with emphasis on design decisions and implementation approaches for {{research_topic}}.
|
||||
|
||||
## ARCHITECTURAL PATTERNS SEQUENCE:
|
||||
|
||||
### 1. Begin Architectural Patterns Analysis
|
||||
|
||||
Start with architectural research approach:
|
||||
"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
|
||||
|
||||
**Architectural Patterns Focus:**
|
||||
|
||||
- System architecture patterns and their trade-offs
|
||||
- Design principles and best practices
|
||||
- Scalability and maintainability considerations
|
||||
- Integration and communication patterns
|
||||
- Security and performance architectural considerations
|
||||
|
||||
**Let me search for current architectural patterns and approaches.**"
|
||||
|
||||
### 2. Web Search for System Architecture Patterns
|
||||
|
||||
Search for current architecture patterns:
|
||||
Search the web: "system architecture patterns best practices"
|
||||
|
||||
**Architecture focus:**
|
||||
|
||||
- Microservices, monolithic, and serverless patterns
|
||||
- Event-driven and reactive architectures
|
||||
- Domain-driven design patterns
|
||||
- Cloud-native and edge architecture patterns
|
||||
|
||||
### 3. Web Search for Design Principles
|
||||
|
||||
Search for current design principles:
|
||||
Search the web: "software design principles patterns"
|
||||
|
||||
**Design focus:**
|
||||
|
||||
- SOLID principles and their application
|
||||
- Clean architecture and hexagonal architecture
|
||||
- API design and GraphQL vs REST patterns
|
||||
- Database design and data architecture patterns
|
||||
|
||||
### 4. Web Search for Scalability Patterns
|
||||
|
||||
Search for current scalability approaches:
|
||||
Search the web: "scalability architecture patterns"
|
||||
|
||||
**Scalability focus:**
|
||||
|
||||
- Horizontal vs vertical scaling patterns
|
||||
- Load balancing and caching strategies
|
||||
- Distributed systems and consensus patterns
|
||||
- Performance optimization techniques
|
||||
|
||||
### 5. Generate Architectural Patterns Content
|
||||
|
||||
Prepare architectural analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Architectural Patterns and Design
|
||||
|
||||
### System Architecture Patterns
|
||||
|
||||
[System architecture patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Design Principles and Best Practices
|
||||
|
||||
[Design principles analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability and Performance Patterns
|
||||
|
||||
[Scalability patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration and Communication Patterns
|
||||
|
||||
[Integration patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Security Architecture Patterns
|
||||
|
||||
[Security patterns analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Architecture Patterns
|
||||
|
||||
[Data architecture analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Architecture
|
||||
|
||||
[Deployment architecture analysis with source citations]
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Continue Option
|
||||
|
||||
Show the generated architectural patterns and present continue option:
|
||||
"I've completed the **architectural patterns analysis** for effective architecture approaches.
|
||||
|
||||
**Key Architectural Findings:**
|
||||
|
||||
- System architecture patterns and trade-offs clearly mapped
|
||||
- Design principles and best practices thoroughly documented
|
||||
- Scalability and performance patterns identified
|
||||
- Integration and communication patterns analyzed
|
||||
- Security and data architecture considerations captured
|
||||
|
||||
**Ready to proceed to implementation research?**
|
||||
[C] Continue - Save this to the document and move to implementation research
|
||||
|
||||
### 7. Handle Continue Selection
|
||||
|
||||
#### If 'C' (Continue):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-05-implementation-research.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 5.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ System architecture patterns identified with current citations
|
||||
✅ Design principles clearly documented and analyzed
|
||||
✅ Scalability and performance patterns thoroughly mapped
|
||||
✅ Integration and communication patterns captured
|
||||
✅ Security and data architecture considerations analyzed
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
✅ Proper routing to implementation research step
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical system architecture patterns
|
||||
❌ Not analyzing design trade-offs and considerations
|
||||
❌ Incomplete scalability or performance patterns analysis
|
||||
❌ Not presenting [C] continue option after content generation
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## ARCHITECTURAL RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for architecture documentation and pattern catalogs
|
||||
- Use architectural conference proceedings and case studies
|
||||
- Research successful system architectures and their evolution
|
||||
- Note architectural decision records (ADRs) and rationales
|
||||
- Research architecture assessment and evaluation frameworks
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
|
||||
Remember: Always emphasize current architectural data and rigorous source verification!
|
||||
@@ -0,0 +1,239 @@
|
||||
# Technical Research Step 4: Implementation Research
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
|
||||
- 💬 FOCUS on implementation approaches and technology adoption
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after implementation research content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- Focus on implementation approaches and technology adoption strategies
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final step in the technical research workflow
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive implementation research with emphasis on practical implementation approaches and technology adoption.
|
||||
|
||||
## IMPLEMENTATION RESEARCH SEQUENCE:
|
||||
|
||||
### 1. Begin Implementation Research
|
||||
|
||||
Start with implementation research approach:
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
|
||||
|
||||
**Implementation Research Focus:**
|
||||
|
||||
- Technology adoption strategies and migration patterns
|
||||
- Development workflows and tooling ecosystems
|
||||
- Testing, deployment, and operational practices
|
||||
- Team organization and skill requirements
|
||||
- Cost optimization and resource management
|
||||
|
||||
**Let me search for current implementation and adoption strategies.**"
|
||||
|
||||
### 2. Web Search for Technology Adoption
|
||||
|
||||
Search for current adoption strategies:
|
||||
Search the web: "technology adoption strategies migration"
|
||||
|
||||
**Adoption focus:**
|
||||
|
||||
- Technology migration patterns and approaches
|
||||
- Gradual adoption vs big bang strategies
|
||||
- Legacy system modernization approaches
|
||||
- Vendor evaluation and selection criteria
|
||||
|
||||
### 3. Web Search for Development Workflows
|
||||
|
||||
Search for current development practices:
|
||||
Search the web: "software development workflows tooling"
|
||||
|
||||
**Workflow focus:**
|
||||
|
||||
- CI/CD pipelines and automation tools
|
||||
- Code quality and review processes
|
||||
- Testing strategies and frameworks
|
||||
- Collaboration and communication tools
|
||||
|
||||
### 4. Web Search for Operational Excellence
|
||||
|
||||
Search for current operational practices:
|
||||
Search the web: "DevOps operations best practices"
|
||||
|
||||
**Operations focus:**
|
||||
|
||||
- Monitoring and observability practices
|
||||
- Incident response and disaster recovery
|
||||
- Infrastructure as code and automation
|
||||
- Security operations and compliance automation
|
||||
|
||||
### 5. Generate Implementation Research Content
|
||||
|
||||
Prepare implementation analysis with web search citations:
|
||||
|
||||
#### Content Structure:
|
||||
|
||||
When saving to document, append these Level 2 and Level 3 sections:
|
||||
|
||||
```markdown
|
||||
## Implementation Approaches and Technology Adoption
|
||||
|
||||
### Technology Adoption Strategies
|
||||
|
||||
[Technology adoption analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Workflows and Tooling
|
||||
|
||||
[Development workflows analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Testing and Quality Assurance
|
||||
|
||||
[Testing approaches analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Practices
|
||||
|
||||
[Deployment practices analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Team Organization and Skills
|
||||
|
||||
[Team organization analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Cost Optimization and Resource Management
|
||||
|
||||
[Cost optimization analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Assessment and Mitigation
|
||||
|
||||
[Risk mitigation analysis with source citations]
|
||||
_Source: [URL]_
|
||||
|
||||
## Technical Research Recommendations
|
||||
|
||||
### Implementation Roadmap
|
||||
|
||||
[Implementation roadmap recommendations]
|
||||
|
||||
### Technology Stack Recommendations
|
||||
|
||||
[Technology stack suggestions]
|
||||
|
||||
### Skill Development Requirements
|
||||
|
||||
[Skill development recommendations]
|
||||
|
||||
### Success Metrics and KPIs
|
||||
|
||||
[Success measurement framework]
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Complete Option
|
||||
|
||||
Show the generated implementation research and present complete option:
|
||||
"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
|
||||
|
||||
**Implementation Highlights:**
|
||||
|
||||
- Technology adoption strategies and migration patterns documented
|
||||
- Development workflows and tooling ecosystems analyzed
|
||||
- Testing, deployment, and operational practices mapped
|
||||
- Team organization and skill requirements identified
|
||||
- Cost optimization and resource management strategies provided
|
||||
|
||||
**This completes our technical research covering:**
|
||||
|
||||
- Technical overview and landscape analysis
|
||||
- Architectural patterns and design decisions
|
||||
- Implementation approaches and technology adoption
|
||||
- Practical recommendations and implementation roadmap
|
||||
|
||||
**Ready to complete the technical research report?**
|
||||
[C] Complete Research - Save final document and conclude
|
||||
|
||||
### 7. Handle Complete Selection
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Complete the technical research workflow
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 5.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Technology adoption strategies identified with current citations
|
||||
✅ Development workflows and tooling thoroughly analyzed
|
||||
✅ Testing and deployment practices clearly documented
|
||||
✅ Team organization and skill requirements mapped
|
||||
✅ Cost optimization and risk mitigation strategies provided
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
✅ Technical research workflow completed successfully
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical technology adoption strategies
|
||||
❌ Not providing practical implementation guidance
|
||||
❌ Incomplete development workflows or operational practices analysis
|
||||
❌ Not presenting completion option for research workflow
|
||||
❌ Appending content without user selecting 'C'
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## IMPLEMENTATION RESEARCH PROTOCOLS:
|
||||
|
||||
- Search for implementation case studies and success stories
|
||||
- Research technology migration patterns and lessons learned
|
||||
- Identify common implementation challenges and solutions
|
||||
- Research development tooling ecosystem evaluations
|
||||
- Analyze operational excellence frameworks and maturity models
|
||||
|
||||
## TECHNICAL RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All technical research steps completed
|
||||
- Comprehensive technical research document generated
|
||||
- All sections appended with source citations
|
||||
- Technical research workflow status updated
|
||||
- Final implementation recommendations provided to user
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
Technical research workflow complete. User may:
|
||||
|
||||
- Use technical research to inform architecture decisions
|
||||
- Conduct additional research on specific technologies
|
||||
- Combine technical research with other research types for comprehensive insights
|
||||
- Move forward with implementation based on technical insights
|
||||
|
||||
Congratulations on completing comprehensive technical research! 🎉
|
||||
@@ -0,0 +1,486 @@
|
||||
# Technical Research Step 5: Technical Synthesis and Completion
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show web search analysis before presenting findings
|
||||
- ⚠️ Present [C] complete option after synthesis content generation
|
||||
- 💾 ONLY save when user chooses C (Complete)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
|
||||
- 🚫 FORBIDDEN to complete workflow until C is selected
|
||||
- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter from previous steps are available
|
||||
- **Research topic = "{{research_topic}}"** - comprehensive technical analysis
|
||||
- **Research goals = "{{research_goals}}"** - achieved through exhaustive technical research
|
||||
- All technical research sections have been completed (overview, architecture, implementation)
|
||||
- Web search capabilities with source verification are enabled
|
||||
- This is the final synthesis step producing the complete technical research document
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Produce a comprehensive, authoritative technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive technical research.
|
||||
|
||||
## COMPREHENSIVE TECHNICAL DOCUMENT SYNTHESIS:
|
||||
|
||||
### 1. Technical Document Structure Planning
|
||||
|
||||
**Complete Technical Research Document Structure:**
|
||||
|
||||
```markdown
|
||||
# [Compelling Technical Title]: Comprehensive {{research_topic}} Technical Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Brief compelling overview of key technical findings and strategic implications]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- Technical Research Introduction and Methodology
|
||||
- Technical Landscape and Architecture Analysis
|
||||
- Implementation Approaches and Best Practices
|
||||
- Technology Stack Evolution and Trends
|
||||
- Integration and Interoperability Patterns
|
||||
- Performance and Scalability Analysis
|
||||
- Security and Compliance Considerations
|
||||
- Strategic Technical Recommendations
|
||||
- Implementation Roadmap and Risk Assessment
|
||||
- Future Technical Outlook and Innovation Opportunities
|
||||
- Technical Research Methodology and Source Documentation
|
||||
- Technical Appendices and Reference Materials
|
||||
```
|
||||
|
||||
### 2. Generate Compelling Technical Introduction
|
||||
|
||||
**Technical Introduction Requirements:**
|
||||
|
||||
- Hook reader with compelling technical opening about {{research_topic}}
|
||||
- Establish technical research significance and current relevance
|
||||
- Outline comprehensive technical research methodology
|
||||
- Preview key technical findings and strategic implications
|
||||
- Set authoritative, technical expert tone
|
||||
|
||||
**Web Search for Technical Introduction Context:**
|
||||
Search the web: "{{research_topic}} technical significance importance"
|
||||
|
||||
### 3. Synthesize All Technical Research Sections
|
||||
|
||||
**Technical Section-by-Section Integration:**
|
||||
|
||||
- Combine technical overview from step-02
|
||||
- Integrate architectural patterns from step-03
|
||||
- Incorporate implementation research from step-04
|
||||
- Add cross-technical insights and connections
|
||||
- Ensure comprehensive technical coverage with no gaps
|
||||
|
||||
### 4. Generate Complete Technical Document Content
|
||||
|
||||
#### Final Technical Document Structure:
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]: Comprehensive {{research_topic}} Technical Research
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive current technical research]
|
||||
|
||||
**Key Technical Findings:**
|
||||
|
||||
- [Most significant architectural insights]
|
||||
- [Critical implementation considerations]
|
||||
- [Important technology trends]
|
||||
- [Strategic technical implications]
|
||||
|
||||
**Technical Recommendations:**
|
||||
|
||||
- [Top 3-5 actionable technical recommendations based on research]
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. Technical Research Introduction and Methodology
|
||||
2. {{research_topic}} Technical Landscape and Architecture Analysis
|
||||
3. Implementation Approaches and Best Practices
|
||||
4. Technology Stack Evolution and Current Trends
|
||||
5. Integration and Interoperability Patterns
|
||||
6. Performance and Scalability Analysis
|
||||
7. Security and Compliance Considerations
|
||||
8. Strategic Technical Recommendations
|
||||
9. Implementation Roadmap and Risk Assessment
|
||||
10. Future Technical Outlook and Innovation Opportunities
|
||||
11. Technical Research Methodology and Source Verification
|
||||
12. Technical Appendices and Reference Materials
|
||||
|
||||
## 1. Technical Research Introduction and Methodology
|
||||
|
||||
### Technical Research Significance
|
||||
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical right now]
|
||||
_Technical Importance: [Strategic technical significance with current context]_
|
||||
_Business Impact: [Business implications of technical research]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Research Methodology
|
||||
|
||||
[Comprehensive description of technical research approach including:]
|
||||
|
||||
- **Technical Scope**: [Comprehensive technical coverage areas]
|
||||
- **Data Sources**: [Authoritative technical sources and verification approach]
|
||||
- **Analysis Framework**: [Structured technical analysis methodology]
|
||||
- **Time Period**: [current focus and technical evolution context]
|
||||
- **Technical Depth**: [Level of technical detail and analysis]
|
||||
|
||||
### Technical Research Goals and Objectives
|
||||
|
||||
**Original Technical Goals:** {{research_goals}}
|
||||
|
||||
**Achieved Technical Objectives:**
|
||||
|
||||
- [Technical Goal 1 achievement with supporting evidence]
|
||||
- [Technical Goal 2 achievement with supporting evidence]
|
||||
- [Additional technical insights discovered during research]
|
||||
|
||||
## 2. {{research_topic}} Technical Landscape and Architecture Analysis
|
||||
|
||||
### Current Technical Architecture Patterns
|
||||
|
||||
[Comprehensive architectural analysis synthesized from step-03 with current context]
|
||||
_Dominant Patterns: [Current architectural approaches]_
|
||||
_Architectural Evolution: [Historical and current evolution patterns]_
|
||||
_Architectural Trade-offs: [Key architectural decisions and implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Design Principles and Best Practices
|
||||
|
||||
[Complete system design analysis]
|
||||
_Design Principles: [Core principles guiding {{research_topic}} implementations]_
|
||||
_Best Practice Patterns: [Industry-standard approaches and methodologies]_
|
||||
_Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Implementation Approaches and Best Practices
|
||||
|
||||
### Current Implementation Methodologies
|
||||
|
||||
[Implementation analysis from step-04 with current context]
|
||||
_Development Approaches: [Current development methodologies and approaches]_
|
||||
_Code Organization Patterns: [Structural patterns and organization strategies]_
|
||||
_Quality Assurance Practices: [Testing, validation, and quality approaches]_
|
||||
_Deployment Strategies: [Current deployment and operations practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Framework and Tooling
|
||||
|
||||
[Comprehensive implementation framework analysis]
|
||||
_Development Frameworks: [Popular frameworks and their characteristics]_
|
||||
_Tool Ecosystem: [Development tools and platform considerations]_
|
||||
_Build and Deployment Systems: [CI/CD and automation approaches]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Technology Stack Evolution and Current Trends
|
||||
|
||||
### Current Technology Stack Landscape
|
||||
|
||||
[Technology stack analysis from step-02 with current updates]
|
||||
_Programming Languages: [Current language trends and adoption patterns]_
|
||||
_Frameworks and Libraries: [Popular frameworks and their use cases]_
|
||||
_Database and Storage Technologies: [Current data storage and management trends]_
|
||||
_API and Communication Technologies: [Integration and communication patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Patterns
|
||||
|
||||
[Comprehensive technology adoption analysis]
|
||||
_Adoption Trends: [Technology adoption rates and patterns]_
|
||||
_Migration Patterns: [Technology migration and evolution trends]_
|
||||
_Emerging Technologies: [New technologies and their potential impact]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Integration and Interoperability Patterns
|
||||
|
||||
### Current Integration Approaches
|
||||
|
||||
[Integration patterns analysis with current context]
|
||||
_API Design Patterns: [Current API design and implementation patterns]_
|
||||
_Service Integration: [Microservices and service integration approaches]_
|
||||
_Data Integration: [Data exchange and integration patterns]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Interoperability Standards and Protocols
|
||||
|
||||
[Comprehensive interoperability analysis]
|
||||
_Standards Compliance: [Industry standards and compliance requirements]_
|
||||
_Protocol Selection: [Communication protocols and selection criteria]_
|
||||
_Integration Challenges: [Common integration challenges and solutions]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Performance and Scalability Analysis
|
||||
|
||||
### Performance Characteristics and Optimization
|
||||
|
||||
[Performance analysis based on research findings]
|
||||
_Performance Benchmarks: [Current performance characteristics and benchmarks]_
|
||||
_Optimization Strategies: [Performance optimization approaches and techniques]_
|
||||
_Monitoring and Measurement: [Performance monitoring and measurement practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability Patterns and Approaches
|
||||
|
||||
[Comprehensive scalability analysis]
|
||||
_Scalability Patterns: [Architectural and design patterns for scalability]_
|
||||
_Capacity Planning: [Capacity planning and resource management approaches]_
|
||||
_Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Security and Compliance Considerations
|
||||
|
||||
### Security Best Practices and Frameworks
|
||||
|
||||
[Security analysis with current context]
|
||||
_Security Frameworks: [Current security frameworks and best practices]_
|
||||
_Threat Landscape: [Current security threats and mitigation approaches]_
|
||||
_Secure Development Practices: [Secure coding and development lifecycle]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Compliance and Regulatory Considerations
|
||||
|
||||
[Comprehensive compliance analysis]
|
||||
_Industry Standards: [Relevant industry standards and compliance requirements]_
|
||||
_Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_
|
||||
_Audit and Governance: [Technical audit and governance practices]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Strategic Technical Recommendations
|
||||
|
||||
### Technical Strategy and Decision Framework
|
||||
|
||||
[Strategic technical recommendations based on comprehensive research]
|
||||
_Architecture Recommendations: [Recommended architectural approaches and patterns]_
|
||||
_Technology Selection: [Recommended technology stack and selection criteria]_
|
||||
_Implementation Strategy: [Recommended implementation approaches and methodologies]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Technical Advantage
|
||||
|
||||
[Analysis of technical competitive positioning]
|
||||
_Technology Differentiation: [Technical approaches that provide competitive advantage]_
|
||||
_Innovation Opportunities: [Areas for technical innovation and differentiation]_
|
||||
_Strategic Technology Investments: [Recommended technology investments and priorities]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Implementation Roadmap and Risk Assessment
|
||||
|
||||
### Technical Implementation Framework
|
||||
|
||||
[Comprehensive implementation guidance based on research findings]
|
||||
_Implementation Phases: [Recommended phased implementation approach]_
|
||||
_Technology Migration Strategy: [Approach for technology adoption and migration]_
|
||||
_Resource Planning: [Technical resources and capabilities planning]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Risk Management
|
||||
|
||||
[Comprehensive technical risk assessment]
|
||||
_Technical Risks: [Major technical risks and mitigation strategies]_
|
||||
_Implementation Risks: [Risks associated with implementation and deployment]_
|
||||
_Business Impact Risks: [Technical risks and their business implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 10. Future Technical Outlook and Innovation Opportunities
|
||||
|
||||
### Emerging Technology Trends
|
||||
|
||||
[Forward-looking technical analysis based on comprehensive research]
|
||||
_Near-term Technical Evolution: [1-2 year technical development expectations]_
|
||||
_Medium-term Technology Trends: [3-5 year expected technical developments]_
|
||||
_Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Innovation and Research Opportunities
|
||||
|
||||
[Technical innovation analysis and recommendations]
|
||||
_Research Opportunities: [Areas for technical research and innovation]_
|
||||
_Emerging Technology Adoption: [Potential new technologies and adoption timelines]_
|
||||
_Innovation Framework: [Approach for fostering technical innovation]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 11. Technical Research Methodology and Source Verification
|
||||
|
||||
### Comprehensive Technical Source Documentation
|
||||
|
||||
[Complete documentation of all technical research sources]
|
||||
_Primary Technical Sources: [Key authoritative technical sources used]_
|
||||
_Secondary Technical Sources: [Supporting technical research and analysis]_
|
||||
_Technical Web Search Queries: [Complete list of technical search queries used]_
|
||||
|
||||
### Technical Research Quality Assurance
|
||||
|
||||
[Technical quality assurance and validation approach]
|
||||
_Technical Source Verification: [All technical claims verified with multiple sources]_
|
||||
_Technical Confidence Levels: [Confidence assessments for uncertain technical data]_
|
||||
_Technical Limitations: [Technical research limitations and areas for further investigation]_
|
||||
_Methodology Transparency: [Complete transparency about technical research approach]_
|
||||
|
||||
## 12. Technical Appendices and Reference Materials
|
||||
|
||||
### Detailed Technical Data Tables
|
||||
|
||||
[Comprehensive technical data tables supporting research findings]
|
||||
_Architectural Pattern Tables: [Detailed architectural pattern comparisons]_
|
||||
_Technology Stack Analysis: [Detailed technology evaluation and comparison data]_
|
||||
_Performance Benchmark Data: [Comprehensive performance measurement data]_
|
||||
|
||||
### Technical Resources and References
|
||||
|
||||
[Valuable technical resources for continued research and implementation]
|
||||
_Technical Standards: [Relevant technical standards and specifications]_
|
||||
_Open Source Projects: [Key open source projects and communities]_
|
||||
_Research Papers and Publications: [Academic and industry research sources]_
|
||||
_Technical Communities: [Professional networks and technical communities]_
|
||||
|
||||
---
|
||||
|
||||
## Technical Research Conclusion
|
||||
|
||||
### Summary of Key Technical Findings
|
||||
|
||||
[Comprehensive summary of the most important technical research findings]
|
||||
|
||||
### Strategic Technical Impact Assessment
|
||||
|
||||
[Assessment of technical implications for {{research_topic}}]
|
||||
|
||||
### Next Steps Technical Recommendations
|
||||
|
||||
[Specific next steps for leveraging this technical research]
|
||||
|
||||
---
|
||||
|
||||
**Technical Research Completion Date:** {{date}}
|
||||
**Research Period:** current comprehensive technical analysis
|
||||
**Document Length:** As needed for comprehensive technical coverage
|
||||
**Source Verification:** All technical facts cited with current sources
|
||||
**Technical Confidence Level:** High - based on multiple authoritative technical sources
|
||||
|
||||
_This comprehensive technical research document serves as an authoritative technical reference on {{research_topic}} and provides strategic technical insights for informed decision-making and implementation._
|
||||
```
|
||||
|
||||
### 5. Present Complete Technical Document and Final Option
|
||||
|
||||
**Technical Document Completion Presentation:**
|
||||
|
||||
"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
|
||||
|
||||
**Technical Document Features:**
|
||||
|
||||
- **Compelling Technical Introduction**: Engaging technical opening that establishes research significance
|
||||
- **Comprehensive Technical TOC**: Complete navigation structure for technical reference
|
||||
- **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Technical Summary**: Key technical findings and strategic implications highlighted
|
||||
- **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research
|
||||
- **Complete Technical Source Citations**: Every technical claim verified with current sources
|
||||
|
||||
**Technical Research Completeness:**
|
||||
|
||||
- Technical landscape and architecture analysis fully documented
|
||||
- Implementation approaches and best practices comprehensively covered
|
||||
- Technology stack evolution and trends detailed
|
||||
- Integration, performance, and security analysis complete
|
||||
- Strategic technical insights and implementation guidance provided
|
||||
|
||||
**Technical Document Standards Met:**
|
||||
|
||||
- Exhaustive technical research with no critical gaps
|
||||
- Professional technical structure and compelling narrative
|
||||
- As long as needed for comprehensive technical coverage
|
||||
- Multiple independent technical sources for all claims
|
||||
- current technical data throughout with proper citations
|
||||
|
||||
**Ready to complete this comprehensive technical research document?**
|
||||
[C] Complete Research - Save final comprehensive technical document
|
||||
|
||||
### 6. Handle Final Technical Completion
|
||||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- Append the complete technical document to the research file
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
||||
- Complete the technical research workflow
|
||||
- Provide final technical document delivery confirmation
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the complete comprehensive technical research document using the full structure above.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Compelling technical introduction with research significance
|
||||
✅ Comprehensive technical table of contents with complete document structure
|
||||
✅ Exhaustive technical research coverage across all technical aspects
|
||||
✅ Executive technical summary with key findings and strategic implications
|
||||
✅ Strategic technical recommendations grounded in comprehensive research
|
||||
✅ Complete technical source verification with current citations
|
||||
✅ Professional technical document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Technical research workflow completed with comprehensive document
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not producing compelling technical introduction
|
||||
❌ Missing comprehensive technical table of contents
|
||||
❌ Incomplete technical research coverage across technical aspects
|
||||
❌ Not providing executive technical summary with key findings
|
||||
❌ Missing strategic technical recommendations based on research
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing technical document without professional structure
|
||||
❌ Not presenting completion option for final technical document
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS:
|
||||
|
||||
This step ensures the final technical research document:
|
||||
|
||||
- Serves as an authoritative technical reference on {{research_topic}}
|
||||
- Provides strategic technical insights for informed decision-making
|
||||
- Includes comprehensive technical coverage with no gaps
|
||||
- Maintains rigorous technical source verification standards
|
||||
- Delivers strategic technical insights and actionable recommendations
|
||||
- Meets professional technical research document quality standards
|
||||
|
||||
## TECHNICAL RESEARCH WORKFLOW COMPLETION:
|
||||
|
||||
When 'C' is selected:
|
||||
|
||||
- All technical research steps completed (1-5)
|
||||
- Comprehensive technical research document generated
|
||||
- Professional technical document structure with intro, TOC, and summary
|
||||
- All technical sections appended with source citations
|
||||
- Technical research workflow status updated to complete
|
||||
- Final comprehensive technical research document delivered to user
|
||||
|
||||
## FINAL TECHNICAL DELIVERABLE:
|
||||
|
||||
Complete authoritative technical research document on {{research_topic}} that:
|
||||
|
||||
- Establishes technical credibility through comprehensive research
|
||||
- Provides strategic technical insights for informed decision-making
|
||||
- Serves as technical reference document for continued use
|
||||
- Maintains highest technical research quality standards with current verification
|
||||
|
||||
Congratulations on completing comprehensive technical research with professional documentation! 🎉
|
||||
Reference in New Issue
Block a user