@rdmind/rdmind 0.0.9-alpha.0 → 0.0.9-alpha.2

package/.knowledge/.ext/.bmad-core/templates/market-research-tmpl.yaml

@@ -0,0 +1,253 @@
+# <!-- Powered by BMAD™ Core -->
+template:
+  id: market-research-template-v2
+  name: Market Research Report
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/market-research.md
+    title: 'Market Research Report: {{project_product_name}}'
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: 'Market Research Elicitation Actions'
+    options:
+      - 'Expand market sizing calculations with sensitivity analysis'
+      - 'Deep dive into a specific customer segment'
+      - 'Analyze an emerging market trend in detail'
+      - 'Compare this market to an analogous market'
+      - 'Stress test market assumptions'
+      - 'Explore adjacent market opportunities'
+      - 'Challenge market definition and boundaries'
+      - 'Generate strategic scenarios (best/base/worst case)'
+      - 'If only we had considered [X market factor]...'
+      - 'Proceed to next section'
+
+sections:
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.
+
+  - id: research-objectives
+    title: Research Objectives & Methodology
+    instruction: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.
+    sections:
+      - id: objectives
+        title: Research Objectives
+        instruction: |
+          List the primary objectives of this market research:
+          - What decisions will this research inform?
+          - What specific questions need to be answered?
+          - What are the success criteria for this research?
+      - id: methodology
+        title: Research Methodology
+        instruction: |
+          Describe the research approach:
+          - Data sources used (primary/secondary)
+          - Analysis frameworks applied
+          - Data collection timeframe
+          - Limitations and assumptions
+
+  - id: market-overview
+    title: Market Overview
+    sections:
+      - id: market-definition
+        title: Market Definition
+        instruction: |
+          Define the market being analyzed:
+          - Product/service category
+          - Geographic scope
+          - Customer segments included
+          - Value chain position
+      - id: market-size-growth
+        title: Market Size & Growth
+        instruction: |
+          Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
+          - Top-down: Start with industry data, narrow down
+          - Bottom-up: Build from customer/unit economics
+          - Value theory: Based on value provided vs. alternatives
+        sections:
+          - id: tam
+            title: Total Addressable Market (TAM)
+            instruction: Calculate and explain the total market opportunity
+          - id: sam
+            title: Serviceable Addressable Market (SAM)
+            instruction: Define the portion of TAM you can realistically reach
+          - id: som
+            title: Serviceable Obtainable Market (SOM)
+            instruction: Estimate the portion you can realistically capture
+      - id: market-trends
+        title: Market Trends & Drivers
+        instruction: Analyze key trends shaping the market using appropriate frameworks like PESTEL
+        sections:
+          - id: key-trends
+            title: Key Market Trends
+            instruction: |
+              List and explain 3-5 major trends:
+              - Trend 1: Description and impact
+              - Trend 2: Description and impact
+              - etc.
+          - id: growth-drivers
+            title: Growth Drivers
+            instruction: Identify primary factors driving market growth
+          - id: market-inhibitors
+            title: Market Inhibitors
+            instruction: Identify factors constraining market growth
+
+  - id: customer-analysis
+    title: Customer Analysis
+    sections:
+      - id: segment-profiles
+        title: Target Segment Profiles
+        instruction: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay
+        repeatable: true
+        sections:
+          - id: segment
+            title: 'Segment {{segment_number}}: {{segment_name}}'
+            template: |
+              - **Description:** {{brief_overview}}
+              - **Size:** {{number_of_customers_market_value}}
+              - **Characteristics:** {{key_demographics_firmographics}}
+              - **Needs & Pain Points:** {{primary_problems}}
+              - **Buying Process:** {{purchasing_decisions}}
+              - **Willingness to Pay:** {{price_sensitivity}}
+      - id: jobs-to-be-done
+        title: Jobs-to-be-Done Analysis
+        instruction: Uncover what customers are really trying to accomplish
+        sections:
+          - id: functional-jobs
+            title: Functional Jobs
+            instruction: List practical tasks and objectives customers need to complete
+          - id: emotional-jobs
+            title: Emotional Jobs
+            instruction: Describe feelings and perceptions customers seek
+          - id: social-jobs
+            title: Social Jobs
+            instruction: Explain how customers want to be perceived by others
+      - id: customer-journey
+        title: Customer Journey Mapping
+        instruction: Map the end-to-end customer experience for primary segments
+        template: |
+          For primary customer segment:
+
+          1. **Awareness:** {{discovery_process}}
+          2. **Consideration:** {{evaluation_criteria}}
+          3. **Purchase:** {{decision_triggers}}
+          4. **Onboarding:** {{initial_expectations}}
+          5. **Usage:** {{interaction_patterns}}
+          6. **Advocacy:** {{referral_behaviors}}
+
+  - id: competitive-landscape
+    title: Competitive Landscape
+    sections:
+      - id: market-structure
+        title: Market Structure
+        instruction: |
+          Describe the overall competitive environment:
+          - Number of competitors
+          - Market concentration
+          - Competitive intensity
+      - id: major-players
+        title: Major Players Analysis
+        instruction: |
+          For top 3-5 competitors:
+          - Company name and brief description
+          - Market share estimate
+          - Key strengths and weaknesses
+          - Target customer focus
+          - Pricing strategy
+      - id: competitive-positioning
+        title: Competitive Positioning
+        instruction: |
+          Analyze how competitors are positioned:
+          - Value propositions
+          - Differentiation strategies
+          - Market gaps and opportunities
+
+  - id: industry-analysis
+    title: Industry Analysis
+    sections:
+      - id: porters-five-forces
+        title: Porter's Five Forces Assessment
+        instruction: Analyze each force with specific evidence and implications
+        sections:
+          - id: supplier-power
+            title: 'Supplier Power: {{power_level}}'
+            template: '{{analysis_and_implications}}'
+          - id: buyer-power
+            title: 'Buyer Power: {{power_level}}'
+            template: '{{analysis_and_implications}}'
+          - id: competitive-rivalry
+            title: 'Competitive Rivalry: {{intensity_level}}'
+            template: '{{analysis_and_implications}}'
+          - id: threat-new-entry
+            title: 'Threat of New Entry: {{threat_level}}'
+            template: '{{analysis_and_implications}}'
+          - id: threat-substitutes
+            title: 'Threat of Substitutes: {{threat_level}}'
+            template: '{{analysis_and_implications}}'
+      - id: adoption-lifecycle
+        title: Technology Adoption Lifecycle Stage
+        instruction: |
+          Identify where the market is in the adoption curve:
+          - Current stage and evidence
+          - Implications for strategy
+          - Expected progression timeline
+
+  - id: opportunity-assessment
+    title: Opportunity Assessment
+    sections:
+      - id: market-opportunities
+        title: Market Opportunities
+        instruction: Identify specific opportunities based on the analysis
+        repeatable: true
+        sections:
+          - id: opportunity
+            title: 'Opportunity {{opportunity_number}}: {{name}}'
+            template: |
+              - **Description:** {{what_is_the_opportunity}}
+              - **Size/Potential:** {{quantified_potential}}
+              - **Requirements:** {{needed_to_capture}}
+              - **Risks:** {{key_challenges}}
+      - id: strategic-recommendations
+        title: Strategic Recommendations
+        sections:
+          - id: go-to-market
+            title: Go-to-Market Strategy
+            instruction: |
+              Recommend approach for market entry/expansion:
+              - Target segment prioritization
+              - Positioning strategy
+              - Channel strategy
+              - Partnership opportunities
+          - id: pricing-strategy
+            title: Pricing Strategy
+            instruction: |
+              Based on willingness to pay analysis and competitive landscape:
+              - Recommended pricing model
+              - Price points/ranges
+              - Value metric
+              - Competitive positioning
+          - id: risk-mitigation
+            title: Risk Mitigation
+            instruction: |
+              Key risks and mitigation strategies:
+              - Market risks
+              - Competitive risks
+              - Execution risks
+              - Regulatory/compliance risks
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: data-sources
+        title: A. Data Sources
+        instruction: List all sources used in the research
+      - id: calculations
+        title: B. Detailed Calculations
+        instruction: Include any complex calculations or models
+      - id: additional-analysis
+        title: C. Additional Analysis
+        instruction: Any supplementary analysis not included in main body

package/.knowledge/.ext/.bmad-core/templates/prd-tmpl.yaml

@@ -0,0 +1,203 @@
+# <!-- Powered by BMAD™ Core -->
+template:
+  id: prd-template-v2
+  name: 产品需求文档
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/prd.md
+    title: '{{project_name}} 产品需求文档 (PRD)'
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: goals-context
+    title: 目标和背景
+    instruction: |
+      问问有没有项目brief文档。如果没有项目brief，强烈建议先用project-brief-tmpl建一个（它提供必要的基础：问题陈述、目标用户、成功指标、MVP范围、约束条件）。如果用户坚持不用brief就写PRD，在目标章节收集这些信息。如果有项目brief，review并用它来填充目标（期望结果的bullet列表）和背景（1-2段关于解决什么问题以及为什么），这样我们能确定PRD MVP的范围。无论如何这对确定需求都很关键。包含变更日志表格。
+    sections:
+      - id: goals
+        title: 目标
+        type: bullet-list
+        instruction: 一行期望结果的bullet列表，PRD成功后会交付的 - 用户和项目期望
+      - id: background
+        title: 背景
+        type: paragraphs
+        instruction: 1-2段简短总结背景，比如brief中学到的，不重复目标，解决什么问题以及为什么，当前情况或需求是什么
+      - id: changelog
+        title: 变更日志
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: 跟踪文档版本和变更
+
+  - id: requirements
+    title: 需求
+    instruction: 在两个子章节下起草功能和非功能需求列表
+    elicit: true
+    sections:
+      - id: functional
+        title: 功能需求
+        type: numbered-list
+        prefix: FR
+        instruction: 每个需求都是一个bullet markdown和以FR开头的标识符序列
+        examples:
+          - 'FR6: Todo List使用AI检测并警告可能重复但措辞不同的todo项。'
+      - id: non-functional
+        title: 非功能需求
+        type: numbered-list
+        prefix: NFR
+        instruction: 每个需求都是一个bullet markdown和以NFR开头的标识符序列
+        examples:
+          - 'NFR1: AWS服务使用应尽量保持在免费额度内。'
+
+  - id: ui-goals
+    title: 用户界面设计目标
+    condition: PRD has UX/UI requirements
+    instruction: |
+      捕获高级UI/UX愿景来指导设计架构师并告知story创建。步骤：
+
+      1. 基于项目上下文用有根据的猜测预填充所有子章节
+      2. 向用户展示完整的渲染章节
+      3. 清楚告诉用户哪里做了假设
+      4. 对不清楚/缺失的元素或需要更多规格的领域问针对性问题
+      5. 这不是详细的UI规格 - 专注于产品愿景和用户目标
+    elicit: true
+    choices:
+      accessibility: [None, WCAG AA, WCAG AAA]
+      platforms: [Web Responsive, Mobile Only, Desktop Only, Cross-Platform]
+    sections:
+      - id: ux-vision
+        title: 整体UX愿景
+      - id: interaction-paradigms
+        title: 关键交互范式
+      - id: core-screens
+        title: 核心页面和视图
+        instruction: 从产品角度看，交付PRD价值和目标需要哪些最关键的页面或视图？这应该是概念性的高级别，用来驱动粗略的Epic或User Stories
+        examples:
+          - '登录页面'
+          - '主仪表板'
+          - '项目详情页'
+          - '设置页面'
+      - id: accessibility
+        title: '无障碍性: {None|WCAG AA|WCAG AAA|自定义需求}'
+      - id: branding
+        title: 品牌
+        instruction: 任何必须融入的已知品牌元素或风格指南？
+        examples:
+          - '复制1900年代早期黑白电影的外观和感觉，包括页面或状态转换时复制胶片损坏或投影机故障的动画效果。'
+          - '附上我们企业品牌的完整调色板和tokens。'
+      - id: target-platforms
+        title: '目标设备和平台: {Web响应式|仅移动端|仅桌面端|跨平台}'
+        examples:
+          - 'Web响应式，以及所有移动平台'
+          - '仅iPhone'
+          - 'ASCII Windows桌面'
+
+  - id: technical-assumptions
+    title: 技术假设
+    instruction: |
+      收集将指导架构师的技术决策。步骤：
+
+      1. 检查.bmad-core/data/technical-preferences.yaml或附加的technical-preferences文件是否存在 - 用它预填充选择
+      2. 询问用户：语言、框架、启动模板、库、API、部署目标
+      3. 对未知的，基于项目目标和MVP范围提供指导
+      4. 记录所有技术选择及理由（为什么这个选择适合项目）
+      5. 这些成为架构师的约束 - 要具体和完整
+    elicit: true
+    choices:
+      repository: [Monorepo, Polyrepo]
+      architecture: [Monolith, Microservices, Serverless]
+      testing: [Unit Only, Unit + Integration, Full Testing Pyramid]
+    sections:
+      - id: repository-structure
+        title: '仓库结构: {Monorepo|Polyrepo|Multi-repo}'
+      - id: service-architecture
+        title: 服务架构
+        instruction: '关键决策 - 记录高级服务架构（如，单体、微服务、Monorepo内的Serverless函数）。'
+      - id: testing-requirements
+        title: 测试需求
+        instruction: '关键决策 - 记录测试需求，仅单元测试、集成测试、e2e、手动测试、需要手动测试便利方法）。'
+      - id: additional-assumptions
+        title: 额外技术假设和请求
+        instruction: 在起草这个文档的整个过程中，如果提出或发现任何其他适合架构师的技术假设，在这里添加为额外的bullet项
+
+  - id: epic-list
+    title: Epic列表
+    instruction: |
+      展示所有epic的高级列表供用户批准。每个epic应该有标题和简短（1句话）的目标陈述。这让用户在深入细节前review整体结构。
+
+      关键：Epic必须按敏捷最佳实践逻辑顺序：
+
+      - 每个epic应该交付重要的、端到端的、完全可部署的可测试功能增量
+      - Epic 1必须建立基础项目基础设施（app设置、Git、CI/CD、核心服务），除非我们在现有app上添加新功能，同时也要交付初始功能，即使简单如健康检查路由或显示简单canary页面 - 记住这点当我们为第一个epic生成stories时！
+      - 每个后续epic基于之前epic的功能构建，交付部署时为用户或业务提供有形价值的主要功能块
+      - 不是每个项目都需要多个epic，epic需要交付价值。例如，完成的API可以交付价值，即使UI未完成并计划在单独的epic中。
+      - 倾向于更少的epic，但让用户知道你的理由，如果某些看起来太大或专注于不同事物，提供拆分选项。
+      - 横切关注点应该贯穿epic和stories，而不是最终的stories。例如，将日志框架作为epic的最后一个story，或作为项目的最终epic或story会很糟糕，因为我们从一开始就没有日志。
+    elicit: true
+    examples:
+      - 'Epic 1: 基础和核心基础设施：建立项目设置、认证和基本用户管理'
+      - 'Epic 2: 核心业务实体：创建和管理主要领域对象的CRUD操作'
+      - 'Epic 3: 用户工作流和交互：启用关键用户旅程和业务流程'
+      - 'Epic 4: 报告和分析：为用户提供洞察和数据可视化'
+
+  - id: epic-details
+    title: Epic {{epic_number}} {{epic_title}}
+    repeatable: true
+    instruction: |
+      epic列表批准后，将每个epic及其所有stories和验收标准作为一个完整的review单元展示。
+
+      为每个epic提供扩展目标（2-3句话描述所有stories将实现的目标和价值）。
+
+      关键Story排序需求：
+
+      - 每个epic内的Stories必须逻辑顺序
+      - 每个story应该是"垂直切片"，除了项目基础的早期使能stories外，交付完整功能
+      - 没有story应该依赖后续story或epic的工作
+      - 识别并记录任何直接先决条件stories
+      - 专注于"什么"和"为什么"而不是"如何"（将技术实现留给架构师），但要足够精确以支持story到story的逻辑顺序操作。
+      - 确保每个story交付明确的用户或业务价值，尽量避免使能器并将它们构建到交付价值的stories中。
+      - 为AI代理执行调整story大小：每个story必须可由单个AI代理在一个专注会话中完成，无上下文溢出
+      - 想想"初级开发者工作2-4小时" - stories必须小、专注和自包含
+      - 如果story看起来复杂，进一步分解，只要它能交付垂直切片
+    elicit: true
+    template: '{{epic_goal}}'
+    sections:
+      - id: story
+        title: Story {{epic_number}}.{{story_number}} {{story_title}}
+        repeatable: true
+        template: |
+          作为{{user_type}}，
+          我想要{{action}}，
+          以便{{benefit}}。
+        sections:
+          - id: acceptance-criteria
+            title: 验收标准
+            type: numbered-list
+            item_template: '{{criterion_number}}: {{criteria}}'
+            repeatable: true
+            instruction: |
+              定义清晰、全面和可测试的验收标准：
+
+              - 从功能角度精确定义"完成"意味着什么
+              - 明确无误并作为验证基础
+              - 包含PRD中的任何关键非功能需求
+              - 考虑后端/数据组件的本地可测试性
+              - 在适用时指定UI/UX需求和框架遵循
+              - 避免应该在其他stories或PRD章节中的横切关注点
+
+  - id: checklist-results
+    title: Checklist结果报告
+    instruction: 在运行checklist和起草提示之前，提供输出完整更新的PRD。如果输出，向用户确认你将继续运行checklist并生成报告。用户确认后，执行pm-checklist并在此章节中填充结果。
+
+  - id: next-steps
+    title: 下一步
+    sections:
+      - id: ux-expert-prompt
+        title: UX专家提示
+        instruction: 这个章节将包含UX专家的提示，保持简短和切题，以使用此文档作为输入启动创建架构模式。
+      - id: architect-prompt
+        title: 架构师提示
+        instruction: 这个章节将包含架构师的提示，保持简短和切题，以使用此文档作为输入启动创建架构模式。

package/.knowledge/.ext/.bmad-core/templates/project-brief-tmpl.yaml

@@ -0,0 +1,222 @@
+# <!-- Powered by BMAD™ Core -->
+template:
+  id: project-brief-template-v2
+  name: Project Brief
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/brief.md
+    title: 'Project Brief: {{project_name}}'
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: 'Project Brief 启发行动'
+    options:
+      - '扩展部分，增加更具体的细节'
+      - '与类似成功产品进行验证'
+      - '用边缘情况压力测试假设'
+      - '探索替代解决方案'
+      - '分析资源/约束权衡'
+      - '生成风险缓解策略'
+      - '从MVP最小化视角挑战范围'
+      - '头脑风暴创意功能可能性'
+      - '如果我们有[资源/能力/时间]...'
+      - '继续下一部分'
+
+sections:
+  - id: introduction
+    instruction: |
+      这个模板指导创建全面的Project Brief，作为产品开发的基础输入。
+
+      首先询问用户喜欢哪种模式：
+
+      1. **交互模式** - 协作完成每个部分
+      2. **YOLO模式** - 生成完整草稿供审查和优化
+
+      开始前，了解有哪些输入可用（头脑风暴结果、市场研究、竞品分析、初步想法）并收集项目上下文。
+
+  - id: executive-summary
+    title: Executive Summary
+    instruction: |
+      创建简洁的概述，抓住项目的本质。包括：
+      - 用1-2句话描述产品概念
+      - 要解决的主要问题
+      - 目标市场识别
+      - 关键价值主张
+    template: '{{executive_summary_content}}'
+
+  - id: problem-statement
+    title: Problem Statement
+    instruction: |
+      清晰且有证据地阐述问题。解决：
+      - 当前状态和痛点
+      - 问题的影响（如果可能，量化）
+      - 为什么现有解决方案不够好
+      - 现在解决这个问题的紧迫性和重要性
+    template: '{{detailed_problem_description}}'
+
+  - id: proposed-solution
+    title: Proposed Solution
+    instruction: |
+      从高层次描述解决方案。包括：
+      - 核心概念和方法
+      - 与现有解决方案的关键差异化
+      - 为什么这个解决方案会在其他地方失败的地方成功
+      - 产品的高层次愿景
+    template: '{{solution_description}}'
+
+  - id: target-users
+    title: Target Users
+    instruction: |
+      具体定义和描述目标用户。对每个用户细分包括：
+      - 人口统计/企业统计档案
+      - 当前行为和工作流
+      - 具体需求和痛点
+      - 他们想要实现的目标
+    sections:
+      - id: primary-segment
+        title: '主要用户细分: {{segment_name}}'
+        template: '{{primary_user_description}}'
+      - id: secondary-segment
+        title: '次要用户细分: {{segment_name}}'
+        condition: Has secondary user segment
+        template: '{{secondary_user_description}}'
+
+  - id: goals-metrics
+    title: Goals & Success Metrics
+    instruction: 建立清晰的目标和如何衡量成功。让目标变得SMART（具体、可衡量、可实现、相关、有时限）
+    sections:
+      - id: business-objectives
+        title: Business Objectives
+        type: bullet-list
+        template: '- {{objective_with_metric}}'
+      - id: user-success-metrics
+        title: User Success Metrics
+        type: bullet-list
+        template: '- {{user_metric}}'
+      - id: kpis
+        title: Key Performance Indicators (KPIs)
+        type: bullet-list
+        template: '- {{kpi}}: {{definition_and_target}}'
+
+  - id: mvp-scope
+    title: MVP Scope
+    instruction: 清楚定义最小可行产品。明确什么包含在内，什么不包含。帮助用户区分必须有的和锦上添花的。
+    sections:
+      - id: core-features
+        title: Core Features (Must Have)
+        type: bullet-list
+        template: '- **{{feature}}:** {{description_and_rationale}}'
+      - id: out-of-scope
+        title: Out of Scope for MVP
+        type: bullet-list
+        template: '- {{feature_or_capability}}'
+      - id: mvp-success-criteria
+        title: MVP Success Criteria
+        template: '{{mvp_success_definition}}'
+
+  - id: post-mvp-vision
+    title: Post-MVP Vision
+    instruction: 概述长期产品方向，不要过度承诺具体细节
+    sections:
+      - id: phase-2-features
+        title: Phase 2 Features
+        template: '{{next_priority_features}}'
+      - id: long-term-vision
+        title: Long-term Vision
+        template: '{{one_two_year_vision}}'
+      - id: expansion-opportunities
+        title: Expansion Opportunities
+        template: '{{potential_expansions}}'
+
+  - id: technical-considerations
+    title: Technical Considerations
+    instruction: 记录已知的技术约束和偏好。注意这些是初步想法，不是最终决定。
+    sections:
+      - id: platform-requirements
+        title: Platform Requirements
+        template: |
+          - **目标平台:** {{platforms}}
+          - **浏览器/操作系统支持:** {{specific_requirements}}
+          - **性能要求:** {{performance_specs}}
+      - id: technology-preferences
+        title: Technology Preferences
+        template: |
+          - **前端:** {{frontend_preferences}}
+          - **后端:** {{backend_preferences}}
+          - **数据库:** {{database_preferences}}
+          - **托管/基础设施:** {{infrastructure_preferences}}
+      - id: architecture-considerations
+        title: Architecture Considerations
+        template: |
+          - **仓库结构:** {{repo_thoughts}}
+          - **服务架构:** {{service_thoughts}}
+          - **集成要求:** {{integration_needs}}
+          - **安全/合规:** {{security_requirements}}
+
+  - id: constraints-assumptions
+    title: Constraints & Assumptions
+    instruction: 清楚说明限制和假设，设定现实的期望
+    sections:
+      - id: constraints
+        title: Constraints
+        template: |
+          - **预算:** {{budget_info}}
+          - **时间线:** {{timeline_info}}
+          - **资源:** {{resource_info}}
+          - **技术:** {{technical_constraints}}
+      - id: key-assumptions
+        title: Key Assumptions
+        type: bullet-list
+        template: '- {{assumption}}'
+
+  - id: risks-questions
+    title: Risks & Open Questions
+    instruction: 主动识别未知和潜在挑战
+    sections:
+      - id: key-risks
+        title: Key Risks
+        type: bullet-list
+        template: '- **{{risk}}:** {{description_and_impact}}'
+      - id: open-questions
+        title: Open Questions
+        type: bullet-list
+        template: '- {{question}}'
+      - id: research-areas
+        title: Areas Needing Further Research
+        type: bullet-list
+        template: '- {{research_topic}}'
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: research-summary
+        title: A. Research Summary
+        condition: Has research findings
+        instruction: |
+          如果适用，总结以下关键发现：
+          - 市场研究
+          - 竞品分析
+          - 用户访谈
+          - 技术可行性研究
+      - id: stakeholder-input
+        title: B. Stakeholder Input
+        condition: Has stakeholder feedback
+        template: '{{stakeholder_feedback}}'
+      - id: references
+        title: C. References
+        template: '{{relevant_links_and_docs}}'
+
+  - id: next-steps
+    title: Next Steps
+    sections:
+      - id: immediate-actions
+        title: Immediate Actions
+        type: numbered-list
+        template: '{{action_item}}'
+      - id: pm-handoff
+        title: PM Handoff
+        content: |
+          这个Project Brief为{{project_name}}提供了完整的上下文。请以'PRD生成模式'开始，彻底审查brief，与用户协作按模板指示逐部分创建PRD，询问任何必要的澄清或建议改进。