feat: BR 上游业务规划域建模 + BizDevOps 全生命周期审查

.claude/CLAUDE.md

@@ -35,7 +35,7 @@ devpace 分为两个独立层次，**产品层不得依赖开发层**：
 
 ## 开发守则
 
-1. **概念模型始终完整**：BR→PF→CR 价值链从第一天就存在，不可省略任何环节。内容可为空但结构必须完整
+1. **概念模型始终完整**：Opportunity→Epic→BR→PF→CR 价值链从第一天就存在，不可省略任何环节。内容可为空但结构必须完整
 2. **Markdown 是唯一格式**：消费者是 LLM + 人类，不使用 YAML/JSON 作为状态文件格式
 3. **Schema 是契约**：`knowledge/_schema/` 中的格式定义是强约束，Skill 输出必须符合 Schema
 4. **plugin.json 必须与文件系统同步**：新增/删除 Skill 后立即更新 `.claude-plugin/plugin.json`
@@ -60,14 +60,13 @@ devpace 分为两个独立层次，**产品层不得依赖开发层**：
 | 质量门系统 | `docs/design/design.md §6` | Gate 1/2/3 定义 |
 | 变更管理 | `docs/design/design.md §7` | 设计原则、四种场景、操作流程 |
 | BizDevOps 理论 | `knowledge/theory.md` | 方法论参考（/pace-theory 运行时数据源） |
-| 需求场景 S1-S12 | `docs/planning/requirements.md` | 验收标准 |
-| 功能需求 F1-F3、非功能需求 NF1-NF10 | `docs/planning/requirements.md` | 特性规格与质量约束 |
+| 需求场景 S1-S42 | `docs/planning/requirements.md` | 验收标准 |
+| 功能需求 F1-F12、非功能需求 NF1-NF11 | `docs/planning/requirements.md` | 特性规格与质量约束 |
 | 战略规划 | `docs/planning/roadmap.md` | 阶段、里程碑、任务定义 |
 | 操作跟踪 | `docs/planning/progress.md` | 当前任务状态、会话历史、变更记录 |
 | 运行时行为规则 | `rules/devpace-rules.md` | 插件加载后 Claude 的行为 |
 | 文件格式契约 | `knowledge/_schema/*.md` | state/project/CR 的字段定义 |
 | 度量指标定义 | `knowledge/metrics.md` | 指标名称、计算方式、用途 |
-| 组件开发基础原则（新手首读） | `knowledge/dev-principles.md` | 跨组件通用的 10 条第一性原理 |
 
 ### 开发规范索引（.claude/rules/，自动加载）
 

README.md

@@ -34,11 +34,10 @@ Next session, Claude reports: "Last time we stopped at auth module, continue?" 
 ## Full Development Lifecycle
 
 ```
- Goal         Features       Code Changes      Quality         Ship
-You define ──→ Plan together ──→ Claude codes ──→ Auto + You ──→ Optional auto
-                │                   │               │              │
-             pace-plan          pace-dev        pace-review    pace-release
-             pace-change                                       pace-feedback
+Opportunity ──→ Epic ──→ Requirements ──→ Features ──→ Code Changes ──→ Quality ──→ Ship
+        │          │           │              │              │              │           │
+     pace-biz   pace-biz   pace-biz       pace-plan      pace-dev     pace-review  pace-release
+                                          pace-change                              pace-feedback
 ```
 
 Requirements can change anytime — `/pace-change` auto-analyzes impact, adjusts the plan, and waits for your confirmation.
@@ -83,38 +82,23 @@ After installing, type `/pace-` in Claude Code. If devpace is loaded, you'll see
 
 ## Commands
 
-### Daily Use
+Most of the time you don't need commands — saying "help me implement X" equals `/pace-dev`, "where are we" equals `/pace-status`.
+
+### Start Here (5 commands cover 90% of daily work)
 
 | Command | Purpose |
 |---------|---------|
-| `/pace-init` | First-time setup (once, supports `--from PRD` for auto feature tree) |
-| `/pace-dev` | Start coding |
-| `/pace-status` | Check progress |
+| `/pace-init` | First-time setup (once) |
+| `/pace-dev` | Start coding — or just say "help me implement X" |
+| `/pace-status` | Check progress — or say "where are we" |
 | `/pace-review` | Approve changes |
 | `/pace-next` | Not sure what's next? Get AI recommendations |
 
-### When Requirements Change or a Cycle Completes
-
-| Command | When to use |
-|---------|------------|
-| `/pace-change` | Add requirements, pause, change scope, reprioritize |
-| `/pace-plan` | Cycle done, plan the next one |
-| `/pace-retro` | Review how things went |
+### More Commands
 
-### Specialized Features (Optional)
+As your project grows, devpace offers change management, iteration planning, business alignment, release orchestration, and more. See [User Guide](docs/user-guide.md) for all 19 commands.
 
-| Command | Scenario |
-|---------|----------|
-| `/pace-test` | Requirements-traceable test management |
-| `/pace-guard` | Risk fabric: Pre-flight scan + Runtime monitoring + Trend analysis + Graduated response |
-| `/pace-release` | Release orchestration: Changelog + Version bump + Git Tag + GitHub Release |
-| `/pace-sync` | External tool bridge: sync task state ↔ GitHub Issues (labels + comments) |
-| `/pace-role` | Switch perspective (PM / Tester / Ops / etc.) |
-| `/pace-theory` | Learn the methodology behind devpace |
-| `/pace-feedback` | Collect post-launch feedback |
-| `/pace-trace` | View full reasoning trace of AI decisions |
-
-Most of the time you don't need commands — saying "help me implement X" equals `/pace-dev`, "where are we" equals `/pace-status`.
+Quick reference: `/pace-change` (requirements changed) · `/pace-plan` (plan iterations) · `/pace-retro` (review metrics) · `/pace-biz` (business planning) · `/pace-release` (ship it)
 
 ## Core Capabilities
 
@@ -124,6 +108,8 @@ Most of the time you don't need commands — saying "help me implement X" equals
 |-----------|-------------|
 | Requirement changes | Add features, pause, change scope — auto impact analysis, orderly adjustment, Claude won't change the plan unilaterally |
 | Complexity awareness | Auto-assesses task complexity, small changes fast-track, large changes full process, complexity drift auto-detected |
+| Technical debt management | `tech-debt` CR type + iteration capacity reservation + trend tracking |
+| Architecture decisions | `/pace-trace arch` manages cross-CR Architecture Decision Records (ADR) |
 
 ### Quality & Traceability
 
@@ -132,6 +118,7 @@ Most of the time you don't need commands — saying "help me implement X" equals
 | Quality gates | Code quality + requirement consistency auto-check + adversarial review, human approval cannot be skipped |
 | Goal traceability | From business goals to code changes, always traceable |
 | Test verification | Requirements-driven — strategy generation, coverage analysis, AI acceptance verification, change impact regression |
+| Semantic drift detection | Continuous monitoring of code-requirement alignment during development, Review includes semantic consistency score |
 
 ### Development Rhythm
 
@@ -142,7 +129,8 @@ Most of the time you don't need commands — saying "help me implement X" equals
 | Progressive autonomy | Assisted / Standard / Autonomous — more guidance for new users, less for experienced ones |
 | DORA proxy metrics | Deploy frequency / Lead time / Failure rate / MTTR proxy values, Elite~Low benchmarks + trend comparison |
 | CI/CD awareness | Auto-detects CI tool type, Gate 4 auto-queries CI status, zero config |
-| Risk fabric | Pre-flight 5-dimension risk scan + Runtime monitoring + Graduated autonomous response (High requires human confirmation) |
+| Risk fabric | OWASP-aware security scanning + Pre-flight 5-dimension risk scan + Runtime monitoring + Graduated autonomous response (High requires human confirmation) |
+| Delivery prediction | AI-powered iteration delivery probability forecasting, bottleneck identification, and risk early warning |
 | Cross-project insights | High-confidence insights exportable/importable to other projects, reducing redundant learning |
 
 ## Workflow

README_zh.md

@@ -34,11 +34,10 @@
 ## 覆盖完整研发生命周期
 
 ```
-  目标         功能         代码变更          质量          发布
-你来定义 ──→ 一起规划 ──→ Claude 写代码 ──→ 自动+你审批 ──→ 可选自动
-               │                │               │              │
-           pace-plan        pace-dev       pace-review    pace-release
-           pace-change                                    pace-feedback
+机会 ──→ 专题 ──→ 需求 ──→ 功能 ──→ 代码变更 ──→ 质量 ──→ 发布
+ │        │       │        │          │          │       │
+pace-biz pace-biz pace-biz pace-plan   pace-dev  pace-review pace-release
+                           pace-change                    pace-feedback
 ```
 
 需求随时可变——`/pace-change` 自动分析影响、调整计划、等你确认。
@@ -83,38 +82,23 @@ claude --plugin-dir /path/to/devpace
 
 ## 命令
 
-### 日常使用
+大多数时候不需要敲命令——说"帮我实现 X"等于 `/pace-dev`，说"做到哪了"等于 `/pace-status`。
+
+### 从这里开始（5 个命令覆盖 90% 日常工作）
 
 | 命令 | 作用 |
 |------|------|
-| <nobr>`/pace-init`</nobr> | 首次初始化（只需一次，支持 `--from PRD` 自动分解功能树） |
-| <nobr>`/pace-dev`</nobr> | 开始写代码 |
-| <nobr>`/pace-status`</nobr> | 看进度 |
-| <nobr>`/pace-review`</nobr> | 审批变更 |
-| <nobr>`/pace-next`</nobr> | 不确定做什么时，看 AI 推荐的下一步 |
-
-### 需求变了或一轮做完时
+| `/pace-init` | 首次初始化（只需一次） |
+| `/pace-dev` | 开始写代码——或者直接说"帮我实现 X" |
+| `/pace-status` | 看进度——或者说"做到哪了" |
+| `/pace-review` | 审批变更 |
+| `/pace-next` | 不确定做什么时，看 AI 推荐的下一步 |
 
-| 命令 | 什么时候用 |
-|------|----------|
-| <nobr>`/pace-change`</nobr> | 加需求、暂停、改范围、调优先级 |
-| <nobr>`/pace-plan`</nobr> | 一轮做完了，规划下一轮 |
-| <nobr>`/pace-retro`</nobr> | 复盘做得怎么样 |
+### 更多命令
 
-### 专项功能（可选，不使用时不受影响）
+随着项目发展，devpace 提供变更管理、迭代规划、业务对齐、发布编排等更多能力。查看[用户指南](docs/user-guide_zh.md)了解全部 19 个命令。
 
-| 命令 | 场景 |
-|------|------|
-| <nobr>`/pace-test`</nobr> | 需求追溯驱动的测试管理 |
-| <nobr>`/pace-guard`</nobr> | 风险织网：Pre-flight 扫描 + Runtime 监控 + 趋势分析 + 分级响应 |
-| <nobr>`/pace-release`</nobr> | 发布编排：Changelog + 版本 bump + Git Tag + GitHub Release |
-| <nobr>`/pace-sync`</nobr> | 外部工具桥接：任务状态 ↔ GitHub Issues 同步（标签 + 评论） |
-| <nobr>`/pace-role`</nobr> | 切换视角（产品经理/测试/运维等） |
-| <nobr>`/pace-theory`</nobr> | 了解背后的方法论 |
-| <nobr>`/pace-feedback`</nobr> | 收集上线后反馈 |
-| <nobr>`/pace-trace`</nobr> | 查看 AI 决策的完整推理轨迹 |
-
-大多数时候不需要敲命令——说"帮我实现 X"等于 `/pace-dev`，说"做到哪了"等于 `/pace-status`。
+常用：`/pace-change`（需求变了）· `/pace-plan`（规划迭代）· `/pace-retro`（复盘度量）· `/pace-biz`（业务规划）· `/pace-release`（发布）
 
 ## 核心能力
 
@@ -124,6 +108,8 @@ claude --plugin-dir /path/to/devpace
 |------|------|
 | <nobr>需求变更</nobr> | 加功能、暂停、改范围——自动分析影响，有序调整，Claude 不擅自改计划 |
 | <nobr>复杂度感知</nobr> | 自动评估任务复杂度，小变更快速通过、大变更完整流程，复杂度漂移自动检测 |
+| <nobr>技术债务管理</nobr> | `tech-debt` CR 类型 + 迭代容量预留 + 趋势追踪 |
+| <nobr>架构决策记录</nobr> | `/pace-trace arch` 管理跨 CR 的 ADR（Architecture Decision Record） |
 
 ### 质量与追溯
 
@@ -132,6 +118,7 @@ claude --plugin-dir /path/to/devpace
 | <nobr>质量门禁</nobr> | 代码质量 + 需求一致性自动检查 + 对抗审查，人类审批不可跳过 |
 | <nobr>目标追溯</nobr> | 从业务目标到代码变更，始终可追溯 |
 | <nobr>测试验证</nobr> | 需求追溯驱动——策略生成、覆盖率分析、AI 验收验证、变更影响回归 |
+| <nobr>语义漂移检测</nobr> | 开发过程中持续监控代码与需求的对齐度，Review 包含语义一致性评分 |
 
 ### 研发节奏
 
@@ -142,7 +129,8 @@ claude --plugin-dir /path/to/devpace
 | <nobr>渐进自主性</nobr> | 辅助/标准/自主三级——新用户多引导，熟练用户少干预 |
 | <nobr>DORA 代理度量</nobr> | 部署频率/前置时间/失败率/MTTR 代理值，Elite~Low 基准分级 + 趋势对比 |
 | <nobr>CI/CD 感知</nobr> | 自动检测 CI 工具类型，Gate 4 自动查询 CI 状态，零配置即用 |
-| <nobr>风险织网</nobr> | Pre-flight 5 维风险扫描 + Runtime 实时监控 + 分级自主响应（High 必须人类确认） |
+| <nobr>风险织网</nobr> | OWASP 安全扫描 + Pre-flight 5 维风险扫描 + Runtime 实时监控 + 分级自主响应（High 必须人类确认） |
+| <nobr>交付预测</nobr> | AI 预测迭代交付概率、识别瓶颈、发出风险预警 |
 | <nobr>跨项目经验</nobr> | 高置信度经验可导出/导入到其他项目，减少重复学习 |
 
 ## 工作流程