選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

step-06-research-synthesis.md 21KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493
  1. # Technical Research Step 6: Technical Synthesis and Completion
  2. ## MANDATORY EXECUTION RULES (READ FIRST):
  3. - 🛑 NEVER generate content without web search verification
  4. - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
  5. - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
  6. - ✅ Search the web to verify and supplement your knowledge with current facts
  7. - 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
  8. - 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
  9. - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
  10. - 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
  11. - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  12. ## EXECUTION PROTOCOLS:
  13. - 🎯 Show web search analysis before presenting findings
  14. - ⚠️ Present [C] complete option after synthesis content generation
  15. - 💾 ONLY save when user chooses C (Complete)
  16. - 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
  17. - 🚫 FORBIDDEN to complete workflow until C is selected
  18. - 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
  19. ## CONTEXT BOUNDARIES:
  20. - Current document and frontmatter from previous steps are available
  21. - **Research topic = "{{research_topic}}"** - comprehensive technical analysis
  22. - **Research goals = "{{research_goals}}"** - achieved through exhaustive technical research
  23. - All technical research sections have been completed (overview, architecture, implementation)
  24. - Web search capabilities with source verification are enabled
  25. - This is the final synthesis step producing the complete technical research document
  26. ## YOUR TASK:
  27. Produce a comprehensive, authoritative technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive technical research.
  28. ## COMPREHENSIVE TECHNICAL DOCUMENT SYNTHESIS:
  29. ### 1. Technical Document Structure Planning
  30. **Complete Technical Research Document Structure:**
  31. ```markdown
  32. # [Compelling Technical Title]: Comprehensive {{research_topic}} Technical Research
  33. ## Executive Summary
  34. [Brief compelling overview of key technical findings and strategic implications]
  35. ## Table of Contents
  36. - Technical Research Introduction and Methodology
  37. - Technical Landscape and Architecture Analysis
  38. - Implementation Approaches and Best Practices
  39. - Technology Stack Evolution and Trends
  40. - Integration and Interoperability Patterns
  41. - Performance and Scalability Analysis
  42. - Security and Compliance Considerations
  43. - Strategic Technical Recommendations
  44. - Implementation Roadmap and Risk Assessment
  45. - Future Technical Outlook and Innovation Opportunities
  46. - Technical Research Methodology and Source Documentation
  47. - Technical Appendices and Reference Materials
  48. ```
  49. ### 2. Generate Compelling Technical Introduction
  50. **Technical Introduction Requirements:**
  51. - Hook reader with compelling technical opening about {{research_topic}}
  52. - Establish technical research significance and current relevance
  53. - Outline comprehensive technical research methodology
  54. - Preview key technical findings and strategic implications
  55. - Set authoritative, technical expert tone
  56. **Web Search for Technical Introduction Context:**
  57. Search the web: "{{research_topic}} technical significance importance"
  58. ### 3. Synthesize All Technical Research Sections
  59. **Technical Section-by-Section Integration:**
  60. - Combine technical overview from step-02
  61. - Integrate architectural patterns from step-03
  62. - Incorporate implementation research from step-04
  63. - Add cross-technical insights and connections
  64. - Ensure comprehensive technical coverage with no gaps
  65. ### 4. Generate Complete Technical Document Content
  66. #### Final Technical Document Structure:
  67. ```markdown
  68. # [Compelling Title]: Comprehensive {{research_topic}} Technical Research
  69. ## Executive Summary
  70. [2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive current technical research]
  71. **Key Technical Findings:**
  72. - [Most significant architectural insights]
  73. - [Critical implementation considerations]
  74. - [Important technology trends]
  75. - [Strategic technical implications]
  76. **Technical Recommendations:**
  77. - [Top 3-5 actionable technical recommendations based on research]
  78. ## Table of Contents
  79. 1. Technical Research Introduction and Methodology
  80. 2. {{research_topic}} Technical Landscape and Architecture Analysis
  81. 3. Implementation Approaches and Best Practices
  82. 4. Technology Stack Evolution and Current Trends
  83. 5. Integration and Interoperability Patterns
  84. 6. Performance and Scalability Analysis
  85. 7. Security and Compliance Considerations
  86. 8. Strategic Technical Recommendations
  87. 9. Implementation Roadmap and Risk Assessment
  88. 10. Future Technical Outlook and Innovation Opportunities
  89. 11. Technical Research Methodology and Source Verification
  90. 12. Technical Appendices and Reference Materials
  91. ## 1. Technical Research Introduction and Methodology
  92. ### Technical Research Significance
  93. [Compelling technical narrative about why {{research_topic}} research is critical right now]
  94. _Technical Importance: [Strategic technical significance with current context]_
  95. _Business Impact: [Business implications of technical research]_
  96. _Source: [URL]_
  97. ### Technical Research Methodology
  98. [Comprehensive description of technical research approach including:]
  99. - **Technical Scope**: [Comprehensive technical coverage areas]
  100. - **Data Sources**: [Authoritative technical sources and verification approach]
  101. - **Analysis Framework**: [Structured technical analysis methodology]
  102. - **Time Period**: [current focus and technical evolution context]
  103. - **Technical Depth**: [Level of technical detail and analysis]
  104. ### Technical Research Goals and Objectives
  105. **Original Technical Goals:** {{research_goals}}
  106. **Achieved Technical Objectives:**
  107. - [Technical Goal 1 achievement with supporting evidence]
  108. - [Technical Goal 2 achievement with supporting evidence]
  109. - [Additional technical insights discovered during research]
  110. ## 2. {{research_topic}} Technical Landscape and Architecture Analysis
  111. ### Current Technical Architecture Patterns
  112. [Comprehensive architectural analysis synthesized from step-03 with current context]
  113. _Dominant Patterns: [Current architectural approaches]_
  114. _Architectural Evolution: [Historical and current evolution patterns]_
  115. _Architectural Trade-offs: [Key architectural decisions and implications]_
  116. _Source: [URL]_
  117. ### System Design Principles and Best Practices
  118. [Complete system design analysis]
  119. _Design Principles: [Core principles guiding {{research_topic}} implementations]_
  120. _Best Practice Patterns: [Industry-standard approaches and methodologies]_
  121. _Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_
  122. _Source: [URL]_
  123. ## 3. Implementation Approaches and Best Practices
  124. ### Current Implementation Methodologies
  125. [Implementation analysis from step-04 with current context]
  126. _Development Approaches: [Current development methodologies and approaches]_
  127. _Code Organization Patterns: [Structural patterns and organization strategies]_
  128. _Quality Assurance Practices: [Testing, validation, and quality approaches]_
  129. _Deployment Strategies: [Current deployment and operations practices]_
  130. _Source: [URL]_
  131. ### Implementation Framework and Tooling
  132. [Comprehensive implementation framework analysis]
  133. _Development Frameworks: [Popular frameworks and their characteristics]_
  134. _Tool Ecosystem: [Development tools and platform considerations]_
  135. _Build and Deployment Systems: [CI/CD and automation approaches]_
  136. _Source: [URL]_
  137. ## 4. Technology Stack Evolution and Current Trends
  138. ### Current Technology Stack Landscape
  139. [Technology stack analysis from step-02 with current updates]
  140. _Programming Languages: [Current language trends and adoption patterns]_
  141. _Frameworks and Libraries: [Popular frameworks and their use cases]_
  142. _Database and Storage Technologies: [Current data storage and management trends]_
  143. _API and Communication Technologies: [Integration and communication patterns]_
  144. _Source: [URL]_
  145. ### Technology Adoption Patterns
  146. [Comprehensive technology adoption analysis]
  147. _Adoption Trends: [Technology adoption rates and patterns]_
  148. _Migration Patterns: [Technology migration and evolution trends]_
  149. _Emerging Technologies: [New technologies and their potential impact]_
  150. _Source: [URL]_
  151. ## 5. Integration and Interoperability Patterns
  152. ### Current Integration Approaches
  153. [Integration patterns analysis with current context]
  154. _API Design Patterns: [Current API design and implementation patterns]_
  155. _Service Integration: [Microservices and service integration approaches]_
  156. _Data Integration: [Data exchange and integration patterns]_
  157. _Source: [URL]_
  158. ### Interoperability Standards and Protocols
  159. [Comprehensive interoperability analysis]
  160. _Standards Compliance: [Industry standards and compliance requirements]_
  161. _Protocol Selection: [Communication protocols and selection criteria]_
  162. _Integration Challenges: [Common integration challenges and solutions]_
  163. _Source: [URL]_
  164. ## 6. Performance and Scalability Analysis
  165. ### Performance Characteristics and Optimization
  166. [Performance analysis based on research findings]
  167. _Performance Benchmarks: [Current performance characteristics and benchmarks]_
  168. _Optimization Strategies: [Performance optimization approaches and techniques]_
  169. _Monitoring and Measurement: [Performance monitoring and measurement practices]_
  170. _Source: [URL]_
  171. ### Scalability Patterns and Approaches
  172. [Comprehensive scalability analysis]
  173. _Scalability Patterns: [Architectural and design patterns for scalability]_
  174. _Capacity Planning: [Capacity planning and resource management approaches]_
  175. _Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_
  176. _Source: [URL]_
  177. ## 7. Security and Compliance Considerations
  178. ### Security Best Practices and Frameworks
  179. [Security analysis with current context]
  180. _Security Frameworks: [Current security frameworks and best practices]_
  181. _Threat Landscape: [Current security threats and mitigation approaches]_
  182. _Secure Development Practices: [Secure coding and development lifecycle]_
  183. _Source: [URL]_
  184. ### Compliance and Regulatory Considerations
  185. [Comprehensive compliance analysis]
  186. _Industry Standards: [Relevant industry standards and compliance requirements]_
  187. _Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_
  188. _Audit and Governance: [Technical audit and governance practices]_
  189. _Source: [URL]_
  190. ## 8. Strategic Technical Recommendations
  191. ### Technical Strategy and Decision Framework
  192. [Strategic technical recommendations based on comprehensive research]
  193. _Architecture Recommendations: [Recommended architectural approaches and patterns]_
  194. _Technology Selection: [Recommended technology stack and selection criteria]_
  195. _Implementation Strategy: [Recommended implementation approaches and methodologies]_
  196. _Source: [URL]_
  197. ### Competitive Technical Advantage
  198. [Analysis of technical competitive positioning]
  199. _Technology Differentiation: [Technical approaches that provide competitive advantage]_
  200. _Innovation Opportunities: [Areas for technical innovation and differentiation]_
  201. _Strategic Technology Investments: [Recommended technology investments and priorities]_
  202. _Source: [URL]_
  203. ## 9. Implementation Roadmap and Risk Assessment
  204. ### Technical Implementation Framework
  205. [Comprehensive implementation guidance based on research findings]
  206. _Implementation Phases: [Recommended phased implementation approach]_
  207. _Technology Migration Strategy: [Approach for technology adoption and migration]_
  208. _Resource Planning: [Technical resources and capabilities planning]_
  209. _Source: [URL]_
  210. ### Technical Risk Management
  211. [Comprehensive technical risk assessment]
  212. _Technical Risks: [Major technical risks and mitigation strategies]_
  213. _Implementation Risks: [Risks associated with implementation and deployment]_
  214. _Business Impact Risks: [Technical risks and their business implications]_
  215. _Source: [URL]_
  216. ## 10. Future Technical Outlook and Innovation Opportunities
  217. ### Emerging Technology Trends
  218. [Forward-looking technical analysis based on comprehensive research]
  219. _Near-term Technical Evolution: [1-2 year technical development expectations]_
  220. _Medium-term Technology Trends: [3-5 year expected technical developments]_
  221. _Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_
  222. _Source: [URL]_
  223. ### Innovation and Research Opportunities
  224. [Technical innovation analysis and recommendations]
  225. _Research Opportunities: [Areas for technical research and innovation]_
  226. _Emerging Technology Adoption: [Potential new technologies and adoption timelines]_
  227. _Innovation Framework: [Approach for fostering technical innovation]_
  228. _Source: [URL]_
  229. ## 11. Technical Research Methodology and Source Verification
  230. ### Comprehensive Technical Source Documentation
  231. [Complete documentation of all technical research sources]
  232. _Primary Technical Sources: [Key authoritative technical sources used]_
  233. _Secondary Technical Sources: [Supporting technical research and analysis]_
  234. _Technical Web Search Queries: [Complete list of technical search queries used]_
  235. ### Technical Research Quality Assurance
  236. [Technical quality assurance and validation approach]
  237. _Technical Source Verification: [All technical claims verified with multiple sources]_
  238. _Technical Confidence Levels: [Confidence assessments for uncertain technical data]_
  239. _Technical Limitations: [Technical research limitations and areas for further investigation]_
  240. _Methodology Transparency: [Complete transparency about technical research approach]_
  241. ## 12. Technical Appendices and Reference Materials
  242. ### Detailed Technical Data Tables
  243. [Comprehensive technical data tables supporting research findings]
  244. _Architectural Pattern Tables: [Detailed architectural pattern comparisons]_
  245. _Technology Stack Analysis: [Detailed technology evaluation and comparison data]_
  246. _Performance Benchmark Data: [Comprehensive performance measurement data]_
  247. ### Technical Resources and References
  248. [Valuable technical resources for continued research and implementation]
  249. _Technical Standards: [Relevant technical standards and specifications]_
  250. _Open Source Projects: [Key open source projects and communities]_
  251. _Research Papers and Publications: [Academic and industry research sources]_
  252. _Technical Communities: [Professional networks and technical communities]_
  253. ---
  254. ## Technical Research Conclusion
  255. ### Summary of Key Technical Findings
  256. [Comprehensive summary of the most important technical research findings]
  257. ### Strategic Technical Impact Assessment
  258. [Assessment of technical implications for {{research_topic}}]
  259. ### Next Steps Technical Recommendations
  260. [Specific next steps for leveraging this technical research]
  261. ---
  262. **Technical Research Completion Date:** {{date}}
  263. **Research Period:** current comprehensive technical analysis
  264. **Document Length:** As needed for comprehensive technical coverage
  265. **Source Verification:** All technical facts cited with current sources
  266. **Technical Confidence Level:** High - based on multiple authoritative technical sources
  267. _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._
  268. ```
  269. ### 5. Present Complete Technical Document and Final Option
  270. **Technical Document Completion Presentation:**
  271. "I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
  272. **Technical Document Features:**
  273. - **Compelling Technical Introduction**: Engaging technical opening that establishes research significance
  274. - **Comprehensive Technical TOC**: Complete navigation structure for technical reference
  275. - **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed
  276. - **Executive Technical Summary**: Key technical findings and strategic implications highlighted
  277. - **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research
  278. - **Complete Technical Source Citations**: Every technical claim verified with current sources
  279. **Technical Research Completeness:**
  280. - Technical landscape and architecture analysis fully documented
  281. - Implementation approaches and best practices comprehensively covered
  282. - Technology stack evolution and trends detailed
  283. - Integration, performance, and security analysis complete
  284. - Strategic technical insights and implementation guidance provided
  285. **Technical Document Standards Met:**
  286. - Exhaustive technical research with no critical gaps
  287. - Professional technical structure and compelling narrative
  288. - As long as needed for comprehensive technical coverage
  289. - Multiple independent technical sources for all claims
  290. - current technical data throughout with proper citations
  291. **Ready to complete this comprehensive technical research document?**
  292. [C] Complete Research - Save final comprehensive technical document
  293. ### 6. Handle Final Technical Completion
  294. #### If 'C' (Complete Research):
  295. - **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
  296. - Append the complete technical document to the research file
  297. - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
  298. - Complete the technical research workflow
  299. - Provide final technical document delivery confirmation
  300. ## APPEND TO DOCUMENT:
  301. When user selects 'C', append the complete comprehensive technical research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
  302. ## SUCCESS METRICS:
  303. ✅ Compelling technical introduction with research significance
  304. ✅ Comprehensive technical table of contents with complete document structure
  305. ✅ Exhaustive technical research coverage across all technical aspects
  306. ✅ Executive technical summary with key findings and strategic implications
  307. ✅ Strategic technical recommendations grounded in comprehensive research
  308. ✅ Complete technical source verification with current citations
  309. ✅ Professional technical document structure and compelling narrative
  310. ✅ [C] complete option presented and handled correctly
  311. ✅ Technical research workflow completed with comprehensive document
  312. ## FAILURE MODES:
  313. ❌ Not producing compelling technical introduction
  314. ❌ Missing comprehensive technical table of contents
  315. ❌ Incomplete technical research coverage across technical aspects
  316. ❌ Not providing executive technical summary with key findings
  317. ❌ Missing strategic technical recommendations based on research
  318. ❌ Relying solely on training data without web verification for current facts
  319. ❌ Producing technical document without professional structure
  320. ❌ Not presenting completion option for final technical document
  321. ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  322. ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  323. ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  324. ## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS:
  325. This step ensures the final technical research document:
  326. - Serves as an authoritative technical reference on {{research_topic}}
  327. - Provides strategic technical insights for informed decision-making
  328. - Includes comprehensive technical coverage with no gaps
  329. - Maintains rigorous technical source verification standards
  330. - Delivers strategic technical insights and actionable recommendations
  331. - Meets professional technical research document quality standards
  332. ## TECHNICAL RESEARCH WORKFLOW COMPLETION:
  333. When 'C' is selected:
  334. - All technical research steps completed (1-5)
  335. - Comprehensive technical research document generated
  336. - Professional technical document structure with intro, TOC, and summary
  337. - All technical sections appended with source citations
  338. - Technical research workflow status updated to complete
  339. - Final comprehensive technical research document delivered to user
  340. ## FINAL TECHNICAL DELIVERABLE:
  341. Complete authoritative technical research document on {{research_topic}} that:
  342. - Establishes technical credibility through comprehensive research
  343. - Provides strategic technical insights for informed decision-making
  344. - Serves as technical reference document for continued use
  345. - Maintains highest technical research quality standards with current verification
  346. ## On Complete
  347. Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
  348. If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
  349. Congratulations on completing comprehensive technical research with professional documentation! 🎉