cc-devflow 4.3.0 → 4.4.1

package/.claude/docs/templates/BACKLOG_TEMPLATE.md

@@ -1,261 +0,0 @@
-# Product Backlog: {{PROJECT_NAME}}
-
-**Updated**: {{UPDATED_DATE}} 北京时间
-**Total Items**: {{TOTAL_COUNT}}
-**P1 Count**: {{P1_COUNT}} | **P2 Count**: {{P2_COUNT}} | **P3 Count**: {{P3_COUNT}}
-
-**Input**:
-- candidates 列表（包含 RM-ID, title, priority, derived_from, description）
-- dependencies 依赖关系
-- timeline 时间线分配
-
-**Prerequisites**: roadmap-planner agent 正在基于 core-roadmap 命令的上下文生成此文档
-
-## Execution Flow (Backlog 生成流程)
-```
-1. Load context from command
-   → Parse candidates array
-   → Parse dependencies array
-   → Parse timeline object
-   → Validate all fields present
-
-2. Load BACKLOG_TEMPLATE.md
-   → Read template from .claude/docs/templates/BACKLOG_TEMPLATE.md
-   → Prepare to fill all sections
-
-3. Group candidates by priority
-   → Separate into P1 (MVP Must-Have), P2 (Important), P3 (Nice-to-Have)
-   → Sort by RM-ID within each priority group
-   → Count items in each priority
-
-4. Generate Priority 1 section
-   → For each P1 candidate:
-      • Generate detailed entry with all fields
-      • Extract business value from description
-      • Estimate effort (S/M/L based on effort_weeks)
-      • Identify dependencies from dependencies array
-      • Extract derived_from source
-      • Assign target milestone from timeline
-      • Set status = "Backlog"
-
-5. Generate Priority 2 section
-   → Similar to P1 but for P2 candidates
-
-6. Generate Priority 3 section
-   → Similar to P1 but for P3 candidates
-
-7. Generate Dependency Matrix
-   → For each RM-ID:
-      • Find what it blocks (RM-IDs that depend on this)
-      • Find what blocks it (REQ-IDs or RM-IDs this depends on)
-   → Format as markdown table
-   → Use "-" for no dependencies
-
-8. Validate completeness
-   → All candidates included
-   → All have priority assigned
-   → Dependency matrix complete
-   → No {{PLACEHOLDER}} remaining
-   → If incomplete: ERROR "Complete missing sections"
-
-9. Write devflow/BACKLOG.md
-   → Write complete file
-   → Use UTF-8 encoding
-
-10. Return: SUCCESS (BACKLOG.md generated)
-```
-
-**重要**: 这是一个自执行模板。roadmap-planner agent 应该按照 Execution Flow 生成完整的 BACKLOG.md 文件。
-
----
-
-## Priority 1 (MVP Must-Have)
-
-_P1 是必须完成的核心功能，没有这些功能产品无法交付价值。_
-
-### {{RM_ID_1}}: {{TITLE_1}}
-
-- **Description**: {{DESCRIPTION_1}}
-- **Business Value**: {{BUSINESS_VALUE_1}}
-  _为什么这是 P1？为什么用户需要这个功能？_
-
-- **Effort**: {{EFFORT_1}} (S/M/L)
-  - S (Small): 1 周以内
-  - M (Medium): 1-3 周
-  - L (Large): 3 周以上
-
-- **Dependencies**: {{DEPENDENCIES_1}}
-  _此功能依赖哪些已有需求？格式: REQ-009 (completed), REQ-010 (in progress)_
-
-- **Derived From**: {{DERIVED_FROM_1}}
-  _来源：REQ-001, Tech Stack, User Feedback, etc._
-
-- **Target Milestone**: {{MILESTONE_1}}
-  _计划在哪个里程碑完成？格式: M1-Q1-2025_
-
-- **Status**: {{STATUS_1}}
-  _Backlog | Ready | In Progress | Blocked | Completed_
-
----
-
-### {{RM_ID_2}}: {{TITLE_2}}
-
-- **Description**: {{DESCRIPTION_2}}
-- **Business Value**: {{BUSINESS_VALUE_2}}
-- **Effort**: {{EFFORT_2}} (S/M/L)
-- **Dependencies**: {{DEPENDENCIES_2}}
-- **Derived From**: {{DERIVED_FROM_2}}
-- **Target Milestone**: {{MILESTONE_2}}
-- **Status**: {{STATUS_2}}
-
----
-
-_重复以上结构为每个 P1 需求创建条目_
-
----
-
-## Priority 2 (Important)
-
-_P2 是重要功能，能够显著提升用户体验或解决重要问题，但不影响 MVP 交付。_
-
-### {{RM_ID_3}}: {{TITLE_3}}
-
-- **Description**: {{DESCRIPTION_3}}
-- **Business Value**: {{BUSINESS_VALUE_3}}
-  _为什么这是 P2？相比 P1 的区别是什么？_
-
-- **Effort**: {{EFFORT_3}} (S/M/L)
-- **Dependencies**: {{DEPENDENCIES_3}}
-- **Derived From**: {{DERIVED_FROM_3}}
-- **Target Milestone**: {{MILESTONE_3}}
-- **Status**: {{STATUS_3}}
-
----
-
-_重复以上结构为每个 P2 需求创建条目_
-
----
-
-## Priority 3 (Nice-to-Have)
-
-_P3 是锦上添花的功能，有更好没有也不影响核心价值。_
-
-### {{RM_ID_4}}: {{TITLE_4}}
-
-- **Description**: {{DESCRIPTION_4}}
-- **Business Value**: {{BUSINESS_VALUE_4}}
-  _为什么这是 P3？什么情况下会提升到 P2 或 P1？_
-
-- **Effort**: {{EFFORT_4}} (S/M/L)
-- **Dependencies**: {{DEPENDENCIES_4}}
-- **Derived From**: {{DERIVED_FROM_4}}
-- **Target Milestone**: {{MILESTONE_4}}
-- **Status**: {{STATUS_4}}
-
----
-
-_重复以上结构为每个 P3 需求创建条目_
-
----
-
-## Dependency Matrix
-
-| RM-ID | Blocks | Blocked By |
-|-------|--------|------------|
-| {{RM_ID_1}} | {{BLOCKS_1}} | {{BLOCKED_BY_1}} |
-| {{RM_ID_2}} | {{BLOCKS_2}} | {{BLOCKED_BY_2}} |
-| {{RM_ID_3}} | {{BLOCKS_3}} | {{BLOCKED_BY_3}} |
-| {{RM_ID_4}} | {{BLOCKS_4}} | {{BLOCKED_BY_4}} |
-
-_填充规则:_
-- **Blocks**: 此需求完成后可以解锁的其他需求（逗号分隔）
-  - 例如: `RM-003, RM-005`
-  - 如果没有: `-`
-
-- **Blocked By**: 此需求依赖的其他需求（逗号分隔）
-  - 格式: `REQ-001 (completed)`, `REQ-010 (in progress)`, `RM-002 (backlog)`
-  - 如果没有: `-`
-
-_说明: 此矩阵用于快速识别需求间的依赖关系，避免优先级冲突_
-
----
-
-## Backlog Management Notes
-
-### 优先级调整指南
-
-**何时提升 P3 → P2**:
-- 用户强烈要求
-- 技术依赖需要（为了完成 P1/P2，需要先完成此功能）
-- 竞争压力（竞品已有类似功能）
-
-**何时提升 P2 → P1**:
-- 成为 MVP 的阻塞项
-- 影响核心用户体验
-- 安全或合规要求
-
-**何时降低优先级**:
-- 用户需求不明确
-- 技术复杂度过高，风险大
-- 有更好的替代方案
-
-### 准入标准 (Definition of Ready)
-
-一个 backlog item 准备好进入开发 (运行 /flow:init) 的标准：
-- [ ] Description 清晰明确
-- [ ] Business Value 已明确
-- [ ] Effort 已评估
-- [ ] Dependencies 已识别并满足（依赖的需求已完成）
-- [ ] Derived From 已标注
-- [ ] 已分配到具体的 Milestone
-- [ ] 用户已确认需求
-
-### 完成标准 (Definition of Done)
-
-一个 backlog item 被认为完成的标准：
-- [ ] 通过 /flow:init, /flow:spec, /flow:dev 流程
-- [ ] 所有 TASKS.md 中的任务完成
-- [ ] 通过 /flow:verify (测试 + 安全审查)
-- [ ] 代码已合并到主分支
-- [ ] 文档已更新
-- [ ] 用户验收通过
-
----
-
-## Appendix: Priority Guidelines
-
-### P1 (MVP Must-Have) - 优先级评估标准
-
-| 标准 | 说明 | 示例 |
-|------|------|------|
-| **核心价值** | 没有此功能产品无法交付核心价值 | 用户认证（没有认证就无法使用） |
-| **阻塞依赖** | 其他高优先级功能依赖此功能 | 权限管理（多个功能需要权限控制） |
-| **用户痛点** | 解决用户最迫切的问题 | 性能优化（启动慢导致用户流失） |
-| **合规要求** | 法律、安全、合规必须 | 数据加密（隐私合规要求） |
-
-### P2 (Important) - 优先级评估标准
-
-| 标准 | 说明 | 示例 |
-|------|------|------|
-| **体验提升** | 显著提升用户体验但不影响核心功能 | 输入框增强（Markdown 预览） |
-| **运营需求** | 支持运营、分析、监控 | 数据分析模块 |
-| **扩展性** | 为未来扩展打基础 | 多账号支持 |
-| **差异化** | 与竞品形成差异化 | AI 辅助功能 |
-
-### P3 (Nice-to-Have) - 优先级评估标准
-
-| 标准 | 说明 | 示例 |
-|------|------|------|
-| **锦上添花** | 有更好，没有也不影响 | 快捷键自定义 |
-| **小众需求** | 只有少数用户需要 | 高级配置项 |
-| **实验性** | 需要验证是否有价值 | 新 UI 风格 |
-| **技术优化** | 技术层面的优化，用户无感知 | 代码重构 |
-
----
-
-**生成说明**:
-1. 所有 `{{PLACEHOLDER}}` 必须被实际内容替换
-2. Business Value 应具体说明为什么这个功能重要
-3. Effort 估算基于历史 Velocity
-4. Dependency Matrix 应与 ROADMAP.md 保持一致
-5. 所有日期使用北京时间

package/.claude/docs/templates/BRAINSTORM_TEMPLATE.md

@@ -1,148 +0,0 @@
----
-req_id: "{REQ_ID}"
-title: "{TITLE}"
-created_at: "{ISO8601_TIMESTAMP}"
-brainstorm_version: "1.0"
-status: "draft"
----
-
-# {REQ_ID} Brainstorm Record
-
-> **[PROTOCOL]**: 后续所有开发必须与本文档保持一致。如有偏离，需更新本文档并说明原因。
-
-## 原始需求（用户原话）
-
-> {用户的原始描述，一字不改，保留所有细节}
-
-## 核心问题定义
-
-### 解决什么问题？
-
-{一句话定义核心问题，例如："用户无法在移动端完成支付"}
-
-### 为谁解决？
-
-{用户画像，例如："日均活跃用户 10,000+，年龄 25-45，移动端为主"}
-
-### 现状痛点
-
-- {痛点1：具体描述，包含数据或用户反馈}
-- {痛点2}
-- {痛点3}
-
-## 成功标准
-
-### 如何判断需求完成？（验收标准）
-
-- [ ] {可度量的标准1，例如："支付成功率 ≥ 95%"}
-- [ ] {可度量的标准2}
-- [ ] {可度量的标准3}
-
-### 如何判断需求成功？（业务指标）
-
-- {业务指标1，例如："订单转化率提升 10%"}
-- {业务指标2}
-
-## 约束条件
-
-| 类型 | 约束 | 原因 |
-|------|------|------|
-| 技术 | {约束，例如："必须兼容 iOS 12+"} | {原因} |
-| 时间 | {约束，例如："2 周内上线"} | {原因} |
-| 资源 | {约束，例如："1 前端 + 1 后端"} | {原因} |
-| 安全 | {约束，例如："敏感数据需加密"} | {原因} |
-| 法规 | {约束，例如："符合 GDPR"} | {原因} |
-
-## 方案探索
-
-### 方案 A: {名称} ⭐ 推荐
-
-**描述**:
-{方案概述，100-200 字}
-
-**优势**:
-- {优势1}
-- {优势2}
-
-**劣势**:
-- {劣势1}
-- {劣势2}
-
-**适用场景**:
-{何时选择这个方案}
-
-**实现要点**:
-1. {关键步骤1}
-2. {关键步骤2}
-
----
-
-### 方案 B: {名称}
-
-**描述**:
-{方案概述}
-
-**优势**:
-- {优势1}
-
-**劣势**:
-- {劣势1}
-
-**适用场景**:
-{何时选择这个方案}
-
----
-
-### 方案 C: {名称}
-
-**描述**:
-{方案概述}
-
-**优势**:
-- {优势1}
-
-**劣势**:
-- {劣势1}
-
-**适用场景**:
-{何时选择这个方案}
-
-## 最终决策
-
-**选定方案**: 方案 {X}
-
-**选择理由**:
-{为什么选这个方案，而非其他方案}
-
-**否决理由**:
-- 方案 {Y}: {为什么不选}
-- 方案 {Z}: {为什么不选}
-
-## 关键决策记录
-
-| 决策点 | 决策 | 理由 | 日期 |
-|--------|------|------|------|
-| {问题1} | {选择} | {为什么} | {YYYY-MM-DD} |
-| {问题2} | {选择} | {为什么} | {YYYY-MM-DD} |
-
-## 风险识别
-
-| 风险 | 概率 | 影响 | 缓解策略 |
-|------|------|------|----------|
-| {风险1} | 高/中/低 | 高/中/低 | {应对措施} |
-| {风险2} | 高/中/低 | 高/中/低 | {应对措施} |
-
-## 变更历史
-
-| 版本 | 日期 | 变更内容 | 变更原因 |
-|------|------|----------|----------|
-| 1.0 | {YYYY-MM-DD} | 初始版本 | 头脑风暴完成 |
-
----
-
-**⚠️ 追溯声明**:
-本文档是 {REQ_ID} 的「北极星」。后续 PRD、EPIC、TASKS、实现都必须与本文档保持一致。
-如发现偏离，必须：
-1. 确认偏离原因
-2. 更新本文档
-3. 记录变更历史

package/.claude/docs/templates/CHECKLIST_TEMPLATE.md

@@ -1,52 +0,0 @@
-# {{TYPE}} Checklist: {{REQ_ID}}
-
-**Purpose**: {{TYPE_DESCRIPTION}}
-**Created**: {{TIMESTAMP}}
-**PRD Reference**: PRD.md
-**Quality Dimensions**: Completeness, Clarity, Consistency, Measurability, Coverage
-
----
-
-## Requirement Completeness
-
-- [ ] CHK001 - Are all {{TYPE}} requirements documented in PRD? [Completeness, Spec §FR-XXX]
-- [ ] CHK002 - Are success criteria defined for {{TYPE}} features? [Completeness]
-- [ ] CHK003 - Are error handling scenarios specified? [Completeness, Gap]
-
-## Requirement Clarity
-
-- [ ] CHK004 - Is '{{VAGUE_TERM}}' quantified with specific metrics? [Clarity, Spec §NFR-XXX]
-- [ ] CHK005 - Are {{TYPE}} behaviors explicitly specified? [Clarity]
-- [ ] CHK006 - Are technical constraints clearly documented? [Clarity]
-
-## Requirement Consistency
-
-- [ ] CHK007 - Are {{TYPE}} requirements consistent across sections? [Consistency]
-- [ ] CHK008 - Are terminology and naming conventions consistent? [Consistency]
-- [ ] CHK009 - Are data formats consistent between requirements? [Consistency]
-
-## Acceptance Criteria Quality
-
-- [ ] CHK010 - Can {{TYPE}} requirements be objectively verified? [Measurability]
-- [ ] CHK011 - Are acceptance criteria in Given-When-Then format? [Measurability]
-- [ ] CHK012 - Are performance metrics quantified with specific numbers? [Measurability]
-
-## Scenario Coverage
-
-- [ ] CHK013 - Are edge cases defined for {{TYPE}} scenarios? [Coverage, Gap]
-- [ ] CHK014 - Are error states and recovery paths specified? [Coverage]
-- [ ] CHK015 - Are boundary conditions addressed? [Coverage]
-
----
-
-## Notes
-
-- Check items off as completed: change `[ ]` to `[x]`
-- Items are numbered sequentially (CHK001-CHKnnn)
-- Quality dimensions: [Completeness], [Clarity], [Consistency], [Measurability], [Coverage]
-- References:
-  - `[Spec §X.Y]` - Links to existing PRD requirement
-  - `[Gap]` - Missing requirement identified
-  - `[Ambiguity]` - Unclear requirement needs clarification
-  - `[Conflict]` - Requirement conflicts with another
-  - `[Assumption]` - Needs validation

package/.claude/docs/templates/CLARIFICATION_REPORT_TEMPLATE.md

@@ -1,206 +0,0 @@
-# Clarification Report: {{REQ_ID}}
-
-**Session ID**: {{SESSION_ID}}
-**Date**: {{DATE}}
-**Duration**: {{SCAN_DURATION}}s (scan) + interactive Q&A
-**Status**: {{STATUS}}
-
----
-
-## Metadata
-
-| Field | Value |
-|-------|-------|
-| Requirement | {{REQ_ID}} |
-| Session ID | {{SESSION_ID}} |
-| Questions | {{QUESTIONS_ANSWERED}} / {{QUESTIONS_TOTAL}} |
-| Generated | {{GENERATED_AT}} |
-
----
-
-## Coverage Summary
-
-**Legend**: ✅ Clear | ⚠️ Partial | ❌ Missing | 🔄 Resolved | ⏭️ Deferred
-
-| Category | Status | Issues | Resolution |
-|----------|--------|--------|------------|
-| Functional Scope | {{DIM_1_STATUS}} | {{DIM_1_ISSUES}} | {{DIM_1_RESOLUTION}} |
-| Data Model | {{DIM_2_STATUS}} | {{DIM_2_ISSUES}} | {{DIM_2_RESOLUTION}} |
-| UX Flow | {{DIM_3_STATUS}} | {{DIM_3_ISSUES}} | {{DIM_3_RESOLUTION}} |
-| Non-Functional Quality | {{DIM_4_STATUS}} | {{DIM_4_ISSUES}} | {{DIM_4_RESOLUTION}} |
-| Integration & Dependencies | {{DIM_5_STATUS}} | {{DIM_5_ISSUES}} | {{DIM_5_RESOLUTION}} |
-| Edge Cases | {{DIM_6_STATUS}} | {{DIM_6_ISSUES}} | {{DIM_6_RESOLUTION}} |
-| Constraints & Tradeoffs | {{DIM_7_STATUS}} | {{DIM_7_ISSUES}} | {{DIM_7_RESOLUTION}} |
-| Terminology | {{DIM_8_STATUS}} | {{DIM_8_ISSUES}} | {{DIM_8_RESOLUTION}} |
-| Completion Signals | {{DIM_9_STATUS}} | {{DIM_9_ISSUES}} | {{DIM_9_RESOLUTION}} |
-| Misc & Placeholders | {{DIM_10_STATUS}} | {{DIM_10_ISSUES}} | {{DIM_10_RESOLUTION}} |
-| Security & Privacy | {{DIM_11_STATUS}} | {{DIM_11_ISSUES}} | {{DIM_11_RESOLUTION}} |
-
-**Summary**:
-- ✅ Clear: {{CLEAR_COUNT}} categories
-- 🔄 Resolved: {{RESOLVED_COUNT}} categories
-- ⏭️ Deferred: {{DEFERRED_COUNT}} categories
-- ❌ Outstanding: {{OUTSTANDING_COUNT}} categories
-
----
-
-## Scan Details
-
-### High-Priority Issues (Priority ≥ 50)
-
-{{#HIGH_PRIORITY_ISSUES}}
-| Issue ID | Dimension | Description | Impact | Uncertainty | Priority |
-|----------|-----------|-------------|--------|-------------|----------|
-{{#ISSUES}}
-| {{ISSUE_ID}} | {{DIM_NAME}} | {{DESCRIPTION}} | {{IMPACT}}/10 | {{UNCERTAINTY}}/10 | {{PRIORITY}} |
-{{/ISSUES}}
-{{/HIGH_PRIORITY_ISSUES}}
-
-{{^HIGH_PRIORITY_ISSUES}}
-No high-priority issues detected.
-{{/HIGH_PRIORITY_ISSUES}}
-
----
-
-## Clarification Session
-
-### Session {{DATE}}
-
-{{#QUESTIONS}}
-#### {{QUESTION_ID}}: {{DIM_NAME}}
-
-**Question**: {{QUESTION_TEXT}}
-
-**Type**: {{QUESTION_TYPE}}
-
-{{#IS_MULTIPLE_CHOICE}}
-| Option | Description |
-|--------|-------------|
-{{#OPTIONS}}
-| **{{OPTION_ID}}** | {{OPTION_TEXT}} - {{OPTION_DESC}} |
-{{/OPTIONS}}
-
-**Recommended**: {{RECOMMENDED_OPTION}} ⭐
-> {{RECOMMENDED_RATIONALE}}
-{{/IS_MULTIPLE_CHOICE}}
-
-{{#IS_SHORT_ANSWER}}
-**Format**: Short answer (≤5 words)
-**Suggested**: {{SUGGESTED_VALUE}}
-{{/IS_SHORT_ANSWER}}
-
-**User Answer**: {{ANSWER}}
-
-**Rationale**: {{ANSWER_RATIONALE}}
-
-**Impact**: {{ANSWER_IMPACT}}
-
-- Q: {{QUESTION_TEXT}} → A: {{ANSWER}}
-
----
-
-{{/QUESTIONS}}
-
-{{^QUESTIONS}}
-No questions generated - research.md appears sufficiently clear.
-{{/QUESTIONS}}
-
----
-
-## Integration Summary
-
-### Sections Updated
-
-{{#UPDATED_SECTIONS}}
-| Section | Update Type | Description |
-|---------|-------------|-------------|
-{{#SECTIONS}}
-| {{SECTION_NAME}} | {{UPDATE_TYPE}} | {{UPDATE_DESC}} |
-{{/SECTIONS}}
-{{/UPDATED_SECTIONS}}
-
-{{^UPDATED_SECTIONS}}
-No sections updated (clarification-only session or no material changes required).
-{{/UPDATED_SECTIONS}}
-
----
-
-## Deferred Items
-
-{{#DEFERRED_ITEMS}}
-| Category | Reason | Recommendation |
-|----------|--------|----------------|
-{{#ITEMS}}
-| {{CATEGORY}} | {{REASON}} | {{RECOMMENDATION}} |
-{{/ITEMS}}
-{{/DEFERRED_ITEMS}}
-
-{{^DEFERRED_ITEMS}}
-No items deferred.
-{{/DEFERRED_ITEMS}}
-
----
-
-## Outstanding Items
-
-{{#OUTSTANDING_ITEMS}}
-> ⚠️ The following items remain unresolved but are low-impact:
-
-{{#ITEMS}}
-- **{{CATEGORY}}**: {{DESCRIPTION}}
-{{/ITEMS}}
-{{/OUTSTANDING_ITEMS}}
-
-{{^OUTSTANDING_ITEMS}}
-No outstanding items.
-{{/OUTSTANDING_ITEMS}}
-
----
-
-## Next Steps
-
-{{#ALL_RESOLVED}}
-✅ **Clarification complete**. All critical ambiguities have been resolved.
-
-Recommended next command: `/flow:spec {{REQ_ID}}`
-{{/ALL_RESOLVED}}
-
-{{#HAS_OUTSTANDING}}
-⚠️ **Clarification partially complete**. Some low-impact items remain.
-
-Options:
-1. Proceed with `/flow:spec {{REQ_ID}}` (acceptable risk)
-2. Re-run `/flow:spec {{REQ_ID}} --overwrite` after planning phase
-{{/HAS_OUTSTANDING}}
-
-{{#HAS_DEFERRED}}
-⏭️ **Items deferred to planning phase**:
-{{#DEFERRED_SUMMARY}}
-- {{ITEM}}
-{{/DEFERRED_SUMMARY}}
-
-These will be addressed during `/flow:spec` task planning or `/flow:dev` implementation.
-{{/HAS_DEFERRED}}
-
-{{#NO_QUESTIONS}}
-✅ **No critical ambiguities detected**. research.md is sufficiently specified.
-
-Recommended next command: `/flow:spec {{REQ_ID}}`
-{{/NO_QUESTIONS}}
-
----
-
-## Validation Checklist
-
-- [ ] CLR-001 All Q&A pairs recorded in session section
-- [ ] CLR-002 No duplicate questions asked
-- [ ] CLR-003 Questions ≤ 5 (actual: {{QUESTIONS_COUNT}})
-- [ ] CLR-004 Coverage summary complete for all 11 dimensions
-- [ ] CLR-005 No contradictory statements remain in research.md
-- [ ] CLR-006 Terminology consistent across updated sections
-
----
-
-**Generated by**: clarify-analyst agent
-**Template Version**: 1.0.0
-**Based on**: spec-kit /speckit.clarify pattern