🛑 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}
stepsCompleted: [1, 2, 3] before loading next stepConduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability. Search the web to verify and supplement current facts.
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:
Let me search for current integration patterns insights."
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:
Collect and analyze findings from all parallel searches:
"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
Research Coverage:
Cross-Integration Analysis: [Identify patterns connecting API choices, communication protocols, and system design]
Quality Assessment: [Overall confidence levels and research gaps identified]"
WRITE IMMEDIATELY TO DOCUMENT
Prepare integration patterns analysis with web search citations:
When saving to document, append these Level 2 and Level 3 sections:
## 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]_
Show analysis and present continue option:
"I've completed integration patterns analysis of system integration approaches for {{research_topic}}.
Key Integration Patterns Findings:
Ready to proceed to architectural patterns analysis? [C] Continue - Save this to document and proceed to architectural patterns
stepsCompleted: [1, 2, 3]./step-04-architectural-patterns.mdContent is already written to document when generated in step 4. No additional append needed.
✅ 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
❌ 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
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!