您最多选择25个主题 主题必须以字母或数字开头,可以包含连字符 (-),并且长度不得超过35个字符

step-04-regulatory-focus.md 6.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206
  1. # Domain Research Step 4: Regulatory Focus
  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 REGULATORY ANALYST, not content generator
  8. - 💬 FOCUS on compliance requirements and regulatory landscape
  9. - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
  10. - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
  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] continue option after regulatory content generation
  15. - 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY
  16. - 💾 ONLY save when user chooses C (Continue)
  17. - 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
  18. - 🚫 FORBIDDEN to load next step until C is selected
  19. ## CONTEXT BOUNDARIES:
  20. - Current document and frontmatter from previous steps are available
  21. - **Research topic = "{{research_topic}}"** - established from initial discussion
  22. - **Research goals = "{{research_goals}}"** - established from initial discussion
  23. - Focus on regulatory and compliance requirements for the domain
  24. - Web search capabilities with source verification are enabled
  25. ## YOUR TASK:
  26. Conduct focused regulatory and compliance analysis with emphasis on requirements that impact {{research_topic}}. Search the web to verify and supplement current facts.
  27. ## REGULATORY FOCUS SEQUENCE:
  28. ### 1. Begin Regulatory Analysis
  29. Start with regulatory research approach:
  30. "Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
  31. **Regulatory Focus Areas:**
  32. - Specific regulations and compliance frameworks
  33. - Industry standards and best practices
  34. - Licensing and certification requirements
  35. - Data protection and privacy regulations
  36. - Environmental and safety requirements
  37. **Let me search for current regulatory requirements.**"
  38. ### 2. Web Search for Specific Regulations
  39. Search for current regulatory information:
  40. Search the web: "{{research_topic}} regulations compliance requirements"
  41. **Regulatory focus:**
  42. - Specific regulations applicable to the domain
  43. - Compliance frameworks and standards
  44. - Recent regulatory changes or updates
  45. - Enforcement agencies and oversight bodies
  46. ### 3. Web Search for Industry Standards
  47. Search for current industry standards:
  48. Search the web: "{{research_topic}} standards best practices"
  49. **Standards focus:**
  50. - Industry-specific technical standards
  51. - Best practices and guidelines
  52. - Certification requirements
  53. - Quality assurance frameworks
  54. ### 4. Web Search for Data Privacy Requirements
  55. Search for current privacy regulations:
  56. Search the web: "data privacy regulations {{research_topic}}"
  57. **Privacy focus:**
  58. - GDPR, CCPA, and other data protection laws
  59. - Industry-specific privacy requirements
  60. - Data governance and security standards
  61. - User consent and data handling requirements
  62. ### 5. Generate Regulatory Analysis Content
  63. Prepare regulatory content with source citations:
  64. #### Content Structure:
  65. When saving to document, append these Level 2 and Level 3 sections:
  66. ```markdown
  67. ## Regulatory Requirements
  68. ### Applicable Regulations
  69. [Specific regulations analysis with source citations]
  70. _Source: [URL]_
  71. ### Industry Standards and Best Practices
  72. [Industry standards analysis with source citations]
  73. _Source: [URL]_
  74. ### Compliance Frameworks
  75. [Compliance frameworks analysis with source citations]
  76. _Source: [URL]_
  77. ### Data Protection and Privacy
  78. [Privacy requirements analysis with source citations]
  79. _Source: [URL]_
  80. ### Licensing and Certification
  81. [Licensing requirements analysis with source citations]
  82. _Source: [URL]_
  83. ### Implementation Considerations
  84. [Practical implementation considerations with source citations]
  85. _Source: [URL]_
  86. ### Risk Assessment
  87. [Regulatory and compliance risk assessment]
  88. ```
  89. ### 6. Present Analysis and Continue Option
  90. Show the generated regulatory analysis and present continue option:
  91. "I've completed **regulatory requirements analysis** for {{research_topic}}.
  92. **Key Regulatory Findings:**
  93. - Specific regulations and frameworks identified
  94. - Industry standards and best practices mapped
  95. - Compliance requirements clearly documented
  96. - Implementation considerations provided
  97. - Risk assessment completed
  98. **Ready to proceed to technical trends?**
  99. [C] Continue - Save this to the document and move to technical trends
  100. ### 7. Handle Continue Selection
  101. #### If 'C' (Continue):
  102. - **CONTENT ALREADY WRITTEN TO DOCUMENT**
  103. - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
  104. - Load: `./step-05-technical-trends.md`
  105. ## APPEND TO DOCUMENT:
  106. Content is already written to document when generated in step 5. No additional append needed.
  107. ## SUCCESS METRICS:
  108. ✅ Applicable regulations identified with current citations
  109. ✅ Industry standards and best practices documented
  110. ✅ Compliance frameworks clearly mapped
  111. ✅ Data protection requirements analyzed
  112. ✅ Implementation considerations provided
  113. ✅ [C] continue option presented and handled correctly
  114. ✅ Content properly appended to document when C selected
  115. ## FAILURE MODES:
  116. ❌ Relying on training data instead of web search for current facts
  117. ❌ Missing critical regulatory requirements for the domain
  118. ❌ Not providing implementation considerations for compliance
  119. ❌ Not completing risk assessment for regulatory compliance
  120. ❌ Not presenting [C] continue option after content generation
  121. ❌ Appending content without user selecting 'C'
  122. ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  123. ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  124. ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  125. ## REGULATORY RESEARCH PROTOCOLS:
  126. - Search for specific regulations by name and number
  127. - Identify regulatory bodies and enforcement agencies
  128. - Research recent regulatory changes and updates
  129. - Map industry standards to regulatory requirements
  130. - Consider regional and jurisdictional differences
  131. ## SOURCE VERIFICATION:
  132. - Always cite regulatory agency websites
  133. - Use official government and industry association sources
  134. - Note effective dates and implementation timelines
  135. - Present compliance requirement levels and obligations
  136. ## NEXT STEP:
  137. After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
  138. Remember: Search the web to verify regulatory facts and provide practical implementation considerations!