universal-dev-standards 5.0.0-rc.8 → 5.0.0

package/bundled/locales/zh-CN/core/verification-evidence.md

@@ -0,0 +1,118 @@
+---
+source: ../../../core/verification-evidence.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-03-24
+status: current
+---
+
+> **语言**: [English](../../../core/verification-evidence.md) | 简体中文
+
+# 验证证据标准
+
+**版本**: 1.0.0
+**最后更新**: 2026-03-20
+**适用范围**: 所有 AI 辅助开发工作流
+**范围**: universal
+**灵感来源**: [Superpowers](https://github.com/obra/superpowers) — verification-before-completion (MIT)
+
+---
+
+## 目的
+
+建立"铁律"：无验证证据不可声称完成。防止 AI 代理虚构成功结果，确保每个完成声明都有可执行的证据支持。
+
+---
+
+## 术语表
+
+| 术语 | 定义 |
+|------|------|
+| 验证证据 | 验证命令执行及其结果的结构化记录 |
+| 铁律 | 绝对规则：无证据 = 不可声称完成 |
+| RED-GREEN 循环 | 通过显示测试修复前失败、修复后通过来证明 Bug 修复 |
+| 退出码 | 命令的数字返回值（0 = 成功，非零 = 失败） |
+
+---
+
+## 铁律
+
+> **无验证证据 = 不可声称完成。**
+
+代理声称"已完成"不是证据。验证必须是可独立执行且产生可观察输出的。
+
+---
+
+## 证据格式
+
+每次验证必须产生结构化的证据记录：
+
+```json
+{
+  "command": "pnpm test -- --filter core",
+  "exit_code": 0,
+  "output": "Tests: 47 passed, 0 failed\nDuration: 3.2s",
+  "timestamp": "2026-03-20T14:30:00Z"
+}
+```
+
+### 必需字段
+
+| 字段 | 类型 | 必需 | 描述 |
+|------|------|------|------|
+| `command` | string | 是 | 执行的确切命令 |
+| `exit_code` | number | 是 | 命令的退出码 |
+| `output` | string | 是 | 命令输出（可截断） |
+| `timestamp` | string | 是 | ISO 8601 时间戳 |
+
+---
+
+## 验证类型
+
+| 类型 | 描述 | 命令示例 |
+|------|------|---------|
+| **测试套件** | 运行项目测试套件 | `pnpm test` |
+| **类型检查** | 验证类型正确性 | `pnpm tsc --noEmit` |
+| **Lint** | 检查代码风格 | `pnpm lint` |
+| **构建** | 验证构建成功 | `pnpm build` |
+| **手动验证** | 运行特定验证脚本 | `curl http://localhost:3000/health` |
+
+---
+
+## RED-GREEN 循环（Bug 修复）
+
+修复 Bug 时，必须展示两个证据：
+
+1. **RED**：修复前测试失败
+2. **GREEN**：修复后测试通过
+
+```json
+[
+  {
+    "phase": "RED",
+    "command": "pnpm test -- auth.test.ts",
+    "exit_code": 1,
+    "output": "FAIL: expected 200, received 401"
+  },
+  {
+    "phase": "GREEN",
+    "command": "pnpm test -- auth.test.ts",
+    "exit_code": 0,
+    "output": "PASS: all 3 tests passed"
+  }
+]
+```
+
+---
+
+## 相关标准
+
+- [系统化调试](systematic-debugging.md)
+- [测试治理](test-governance.md)
+- [测试标准](testing-standards.md)
+
+---
+
+## 许可证
+
+本标准采用 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 发布。

package/bundled/locales/zh-CN/core/virtual-organization-standards.md

@@ -0,0 +1,104 @@
+---
+source: ../../../core/virtual-organization-standards.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-03-24
+status: current
+---
+
+> **语言**: [English](../../../core/virtual-organization-standards.md) | 简体中文
+
+# 虚拟组织标准
+
+**版本**: 1.0.0
+**最后更新**: 2026-01-29
+**适用范围**: 项目设置和 AI 工具配置
+**范围**: universal
+**行业标准**: ISO 12207 §6.2
+**参考**: [iso.org](https://www.iso.org/standard/63712.html)
+**ISO 12207 映射**: 组织项目赋能过程（6.2）
+
+---
+
+## 目的
+
+本标准将 AI 生态系统视为"虚拟组织"。它定义如何将 AI 能力（技能）、基础设施和品质保证作为组织资产来管理，确保"虚拟劳动力"是有能力且合规的。
+
+---
+
+## 1. 虚拟劳动力管理（人力资源）
+
+在 Vibe Coding 中，"人力资源管理"转化为管理 AI 代理的能力。
+
+### 1.1 技能管理
+
+技能是虚拟员工的"资质"。
+
+- **获取**: 技能必须明确安装（如通过 `skills/` 目录或插件）
+- **胜任力**: 技能必须在特定项目上下文中验证
+- **角色定义**: 代理应被分配"角色"（技能集合），而非通用的
+
+| 角色 | 推荐技能集 |
+|------|-----------|
+| **架构师代理** | `system-design`、`diagram-generation`、`codebase-analysis` |
+| **测试代理** | `test-runner`、`coverage-analyzer`、`mock-generator` |
+| **重构代理** | `static-analysis`、`code-metrics`、`refactoring-patterns` |
+
+### 1.2 入职（上下文加载）
+
+"入职"AI 代理意味着加载正确的上下文和配置。
+
+- **项目引导**: 加载 `README.md`、架构文档和标准
+- **规则对齐**: 加载 `core/ai-agreement-standards.md`
+
+---
+
+## 2. 基础设施管理（工具）
+
+### 2.1 工具集成
+
+AI 代理的"办公环境"包括：
+
+- **MCP 服务器**: 通过 Model Context Protocol 标准化集成
+- **API 访问**: 密钥和端点的安全管理
+- **沙箱**: 代码执行的隔离环境（防止系统损坏）
+
+### 2.2 知识库
+
+AI 代理的"企业图书馆"：
+
+- **向量数据库**: 用于大规模文档检索
+- **代码片段库**: 可复用的代码模式和模板
+
+---
+
+## 3. 品质管理系统（QMS）
+
+### 3.1 品质策略
+
+| 方面 | 实施方式 |
+|------|---------|
+| **代码品质** | 自动化 linting、类型检查、代码审查 |
+| **测试品质** | 测试覆盖率门槛、测试金字塔比例 |
+| **文档品质** | 文档模板、审查流程 |
+| **安全品质** | 安全扫描、依赖审计 |
+
+### 3.2 持续改进
+
+- 定期回顾 AI 代理的产出品质
+- 根据项目需求更新技能集
+- 维护品质指标的趋势分析
+
+---
+
+## 相关标准
+
+- [AI 协议标准](ai-agreement-standards.md)
+- [AI 指令标准](../../../core/ai-instruction-standards.md)
+- [情境感知加载](context-aware-loading.md)
+
+---
+
+## 许可证
+
+本标准采用 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 发布。

package/bundled/locales/zh-CN/core/workflow-enforcement.md

@@ -0,0 +1,132 @@
+# 工作流程强制执行标准
+
+**适用范围**：所有使用结构化开发方法论的软件项目
+**范围**：通用
+
+## 概述
+
+本标准定义了机器可强制执行的工作流程闸门，防止在开发方法论（SDD、TDD、BDD）中跳过阶段。除了依赖开发者的自律外，工作流程闸门在阶段转换时提供自动化检查。
+
+## 核心原则
+
+> **引导而非阻断。** 当前置条件失败时，总是提供可操作的指引：缺少什么、为什么重要、以及如何修复。
+
+## 执行模式
+
+项目可通过 `.uds/config.yaml` 配置执行行为：
+
+| 模式 | 行为 | 使用场景 |
+|------|------|---------|
+| `enforce` | 阻断阶段转换 + 显示指引 | 承诺流程纪律的团队 |
+| `suggest` | 显示警告 + 允许覆盖 | 渐进式采用的团队 |
+| `off` | 不执行任何检查 | 选择退出 |
+
+**默认值**：`enforce`
+
+```yaml
+# .uds/config.yaml
+workflow:
+  enforcement_mode: enforce  # enforce | suggest | off
+```
+
+## 阶段闸门架构
+
+### 运作方式
+
+1. 用户调用工作流程命令（例如 `/sdd implement`）
+2. AI 助手检查该阶段的前置条件
+3. 如果前置条件通过 → 正常进行
+4. 如果前置条件失败：
+   - **enforce 模式**：停止、解释、引导到正确阶段
+   - **suggest 模式**：警告、允许覆盖
+   - **off 模式**：完全跳过检查
+
+### 闸门类型
+
+| 闸门类型 | 阻断 | 描述 |
+|---------|------|------|
+| **硬闸门** | 是 | 必须通过才能继续（例如：规格必须为已核准才能实作） |
+| **软闸门** | 否 | 建议性警告（例如：建议在 commit 中引用规格） |
+
+## SDD 阶段闸门
+
+```
+discuss → create → review → approve → implement → verify
+```
+
+| 阶段 | 前置条件 |
+|------|---------|
+| discuss | 无（入口点） |
+| create | 检查孤儿规格（软闸门） |
+| review | 规格存在且状态 = Draft |
+| approve | 规格存在且状态 = Review，所有评论已处理 |
+| implement | 规格存在且状态 = Approved |
+| verify | 实作存在，所有 AC 有代码 + 测试 |
+
+## TDD 阶段闸门
+
+```
+RED → GREEN → REFACTOR → (重复)
+```
+
+| 阶段 | 前置条件 |
+|------|---------|
+| RED | 功能/行为已明确定义 |
+| GREEN | 至少一个失败的测试存在（不是错误，而是断言失败） |
+| REFACTOR | 所有测试通过 |
+
+**关键强制规则**：AI 不得在失败测试存在之前撰写实作代码。这是 TDD 的基本契约。
+
+## BDD 阶段闸门
+
+```
+DISCOVERY → FORMULATION → AUTOMATION → LIVING DOCS
+```
+
+| 阶段 | 前置条件 |
+|------|---------|
+| DISCOVERY | 行为/功能已识别 |
+| FORMULATION | 探索阶段产出的具体范例存在 |
+| AUTOMATION | 包含 Gherkin 场景的 `.feature` 文件存在 |
+| LIVING DOCS | 步骤定义已实作，所有场景通过 |
+
+## 提交闸门
+
+| 检查 | 类型 | 触发 |
+|------|------|------|
+| 存在已暂存的变更 | 硬闸门 | 所有提交 |
+| 无合并冲突 | 硬闸门 | 所有提交 |
+| 测试通过 | 硬闸门 | feat/fix 提交 |
+| 规格引用 | 软闸门 | 有活跃规格的 feat/fix 提交 |
+
+## 实作注意事项
+
+### 对于 AI 助手
+
+AI 助手应该：
+1. 在执行任何工作流程阶段**之前**检查闸门
+2. 使用项目配置中的执行模式
+3. 当闸门失败时提供清晰、可操作的指引
+4. 在开始新工作流程前检查是否有可恢复的工作流程状态
+5. 在 `.workflow-state/` 中追踪阶段转换
+
+### 对于 CLI 工具
+
+CLI 工具可通过以下方式整合闸门：
+1. `WorkflowGate` 模块 — 验证阶段转换
+2. Pre-commit hooks — 警告工作流程合规性
+3. `uds check` — 报告工作流程状态
+
+### 对于 Git Hooks
+
+Git 层级的执行应为**仅警告**（非阻断），以避免让开发者感到挫折。AI 层级处理阻断性执行，因为它可以解释和引导。
+
+## 与其他标准的关系
+
+| 标准 | 关系 |
+|------|------|
+| [工作流状态协议](workflow-state-protocol.md) | 闸门检查由此协议管理的状态文件 |
+| [规格驱动开发](spec-driven-development.md) | SDD 阶段闸门强制 SDD 工作流程 |
+| [测试标准](testing-standards.md) | TDD/BDD 闸门强制测试方法论 |
+| [提交消息指南](commit-message-guide.md) | 提交闸门强制规格追踪性 |
+| [签入标准](checkin-standards.md) | Pre-commit 闸门补充签入规则 |

package/bundled/locales/zh-CN/docs/CHEATSHEET.md

@@ -1,6 +1,6 @@
 # UDS 速查表
 
-> Quick reference for all UDS features | Last updated: 2026-03-17
+> Quick reference for all UDS features | Last updated: 2026-03-24
 
 **Language**: [English](../../../docs/CHEATSHEET.md) | [繁體中文](../../zh-TW/docs/CHEATSHEET.md) | 简体中文
 
@@ -24,6 +24,7 @@
 
 | Command | 说明 |
 |---------|-------------|
+| `/ac-coverage` | "[UDS] Generate AC-to-test traceability matrix and coverage report" |
 | `/atdd` | [UDS] Guide through Acceptance Test-Driven Development workflow |
 | `/bdd` | [UDS] Guide through Behavior-Driven Development workflow |
 | `/brainstorm` | "[UDS] Structured AI-assisted brainstorming before spec creation" |
@@ -62,31 +63,42 @@
 
 | Skill | 说明 |
 |-------|-------------|
+| `ac-coverage-assistant` | "[UDS] Analyze AC-to-test traceability and coverage" |
 | `ai-collaboration-standards` | Prevent AI hallucination and ensure evidence-based responses |
 | `ai-friendly-architecture` | Design AI-friendly architecture with explicit patterns, laye |
 | `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, .cursor |
+| `api-design-assistant` | Guide API design following REST, GraphQL, and gRPC best prac |
 | `atdd-assistant` | "[UDS] Guide through Acceptance Test-Driven Development work |
 | `audit-assistant` | "[UDS] UDS Health & Feedback System \| UDS 健康檢查與回饋系統" |
 | `bdd-assistant` | "[UDS] Guide through Behavior-Driven Development workflow" |
 | `brainstorm-assistant` | "[UDS] Structured AI-assisted brainstorming before spec crea |
 | `changelog-guide` | "[UDS] Generate and maintain CHANGELOG.md entries" |
 | `checkin-assistant` | "[UDS] Pre-commit quality gates verification" |
+| `ci-cd-assistant` | Guide CI/CD pipeline design, configuration, and optimization |
 | `code-review-assistant` | "[UDS] Perform systematic code review with checklist" |
 | `commit-standards` | "[UDS] Generate commit messages following Conventional Commi |
+| `database-assistant` | Guide database design, migration, and query optimization. |
 | `dev-workflow-guide` | "[UDS] Guide for mapping software development phases to UDS  |
 | `docs-generator` | "[UDS] Generate usage documentation from project sources" |
 | `documentation-guide` | Guide documentation structure, content requirements, and pro |
+| `durable-execution-assistant` | "[UDS] Guide workflow failure recovery with checkpoints, ret |
 | `error-code-guide` | Design consistent error codes following the PREFIX_CATEGORY_ |
 | `forward-derivation` | "[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables f |
 | `git-workflow-guide` | Guide Git branching strategies, branch naming, and merge ope |
+| `incident-response-assistant` | Guide incident response, root cause analysis, and post-morte |
 | `logging-guide` | Implement structured logging with proper log levels and sens |
 | `methodology-system` | "[UDS] Manage development methodology workflow" |
+| `metrics-dashboard-assistant` | "[UDS] Track development metrics, code quality indicators, a |
+| `migration-assistant` | "[UDS] Guide code migration, framework upgrades, and technol |
+| `pr-automation-assistant` | Guide pull request creation, review automation, and merge st |
 | `project-discovery` | "[UDS] Assess project health, architecture, and risks before |
 | `project-structure-guide` | Guide for organizing project directories following language- |
 | `refactoring-assistant` | "[UDS] Guide refactoring decisions and strategy selection" |
 | `release-standards` | "[UDS] Guide release process and changelogs" |
 | `requirement-assistant` | "[UDS] Write user stories and requirements following INVEST  |
 | `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logi |
+| `security-assistant` | Guide security review and vulnerability assessment following |
+| `security-scan-assistant` | Guide automated security scanning, dependency auditing, and  |
 | `spec-driven-dev` | "[UDS] Create or review specification documents for Spec-Dri |
 | `tdd-assistant` | "[UDS] Guide through Test-Driven Development workflow" |
 | `test-coverage-assistant` | "[UDS] Analyze test coverage and provide recommendations" |
@@ -116,18 +128,24 @@
 
 | Standard | 说明 |
 |----------|-------------|
+| `acceptance-criteria-traceability` | Acceptance Criteria Traceability Standards |
 | `acceptance-test-driven-development` | Acceptance Test-Driven Development (ATDD) Standards |
 | `accessibility-standards` | This standard defines comprehensive guidelines for |
+| `agent-dispatch` | Define standards for dispatching AI sub-agents in  |
 | `ai-agreement-standards` | This standard formalizes the interaction between H |
 | `ai-friendly-architecture` | This standard defines architecture and documentati |
 | `ai-instruction-standards` | This standard defines best practices for creating  |
 | `anti-hallucination` | This standard defines strict guidelines for AI ass |
+| `api-design-standards` | This standard defines comprehensive guidelines for |
 | `behavior-driven-development` | Behavior-Driven Development (BDD) Standards |
+| `branch-completion` | Define a standardized workflow for completing deve |
+| `change-batching-standards` | Change Batching Standards |
 | `changelog-standards` | This standard defines how to write and maintain a  |
 | `checkin-standards` | This standard defines quality gates that MUST be p |
 | `code-review-checklist` | This standard provides a comprehensive checklist f |
 | `commit-message-guide` | Standardized commit messages improve code review e |
 | `context-aware-loading` | This standard defines a protocol for AI tools to s |
+| `database-standards` | This standard defines guidelines for database desi |
 | `deployment-standards` | This standard defines guidelines for safely deploy |
 | `developer-memory` | This standard defines a structured system for capt |
 | `documentation-structure` | This standard defines a consistent documentation s |
@@ -135,8 +153,11 @@
 | `error-code-standards` | Error Code Standards |
 | `forward-derivation-standards` | This standard defines the principles and workflows |
 | `git-workflow` | This standard defines Git branching strategies and |
+| `git-worktree` | Define a lifecycle for using Git worktrees to isol |
 | `logging-standards` | Logging Standards |
+| `model-selection` | Define a cost-effective strategy for selecting AI  |
 | `performance-standards` | This standard defines comprehensive guidelines for |
+| `pipeline-integration-standards` | Pipeline Integration Standards |
 | `project-context-memory` | This standard defines a structured system for capt |
 | `project-structure` | This standard defines conventions for project dire |
 | `refactoring-standards` | This standard defines comprehensive guidelines for |
@@ -145,12 +166,15 @@
 | `security-standards` | This standard defines comprehensive security guide |
 | `spec-driven-development` | Spec-Driven Development (SDD) Standards |
 | `structured-task-definition` | Structured Task Definition Standards |
+| `systematic-debugging` | Define a structured, four-phase debugging workflow |
 | `test-completeness-dimensions` | This document defines a systematic framework for e |
 | `test-driven-development` | Test-Driven Development (TDD) Standards |
 | `test-governance` | Test Governance Standards |
 | `testing-standards` | This standard defines actionable testing rules and |
+| `verification-evidence` | Establish an "Iron Law" that no task can be claime |
 | `versioning` | This standard defines how to version software rele |
 | `virtual-organization-standards` | This standard treats the AI ecosystem as a "Virtua |
+| `workflow-enforcement` | Workflow Enforcement Standards |
 | `workflow-state-protocol` | Workflow State Protocol |
 
 ## 📜 脚本
@@ -164,6 +188,7 @@
 | `check-cli-docs-sync.sh` | CLI-to-Documentation Sync Checker |
 | `check-commands-sync.ps1` | Check Commands Sync |
 | `check-commands-sync.sh` | Commands Sync Checker |
+| `check-commit-spec-reference.sh` | Commit-msg Spec Reference Suggestion — WARNING ONL |
 | `check-docs-integrity.ps1` | Check Docs Integrity |
 | `check-docs-integrity.sh` | Documentation Integrity Checker |
 | `check-docs-sync.ps1` | Check Docs Sync |
@@ -186,6 +211,7 @@
 | `check-usage-docs-sync.sh` | check-usage-docs-sync.sh |
 | `check-version-sync.ps1` | Check Version Sync |
 | `check-version-sync.sh` | Version Sync Checker |
+| `check-workflow-compliance.sh` | Workflow Compliance Check — WARNING ONLY (non-bloc |
 | `convert-md-to-yaml.mjs` | Markdown to AI-YAML Conversion Script |
 | `fix-manifest-paths.ps1` | Fix Manifest Paths |
 | `fix-manifest-paths.sh` | Manifest Path Fixer |

package/bundled/locales/zh-CN/docs/CLI-INIT-OPTIONS.md

@@ -728,7 +728,7 @@ You are an AI assistant that prioritizes accuracy over confidence...
 ---
 
 ## Commit Message Standards
-Reference: .standards/commit-message-guide.md
+Reference: .standards/commit-message.ai.yaml
 
 ### Format Structure
 <type>(<scope>): <subject>
@@ -864,6 +864,8 @@ uds init --experimental
 |------|----------|------|
 | 非交互模式 | `-y, --yes` | 跳过交互提示，使用默认值 |
 | 实验性功能 | `-E, --experimental` | 启用实验性功能（开发方法论选择） |
+| AGENTS.md | `--agents-md` | 生成 AGENTS.md 通用摘要（默认：未选 codex/opencode 时自动生成） |
+| 不生成 AGENTS.md | `--no-agents-md` | 跳过 AGENTS.md 生成 |
 | 模式（已弃用） | `-m, --mode` | 安装模式（skills, full）- 请改用 `--skills-location` |
 
 ### 完整 CLI 示例
@@ -888,6 +890,12 @@ uds init -y \
 # 企业级完整设置
 uds init -y --content-mode full
 
+# 生成 AGENTS.md 通用摘要（--yes 模式默认生成）
+uds init -y --agents-md
+
+# 跳过 AGENTS.md 生成
+uds init -y --no-agents-md
+
 # 繁体中文团队
 uds init -y --commit-lang traditional-chinese --locale zh-cn
 

package/bundled/locales/zh-CN/docs/FEATURE-REFERENCE.md

@@ -1,7 +1,7 @@
 # UDS 功能参考手册
 
 > Universal Development Standards - 完整功能文档
-> Auto-generated | Last updated: 2026-03-17
+> Auto-generated | Last updated: 2026-03-24
 
 **Language**: [English](../../../docs/FEATURE-REFERENCE.md) | [繁體中文](../../zh-TW/docs/FEATURE-REFERENCE.md) | 简体中文
 
@@ -10,14 +10,14 @@
 ## 目录
 
 1. [CLI 指令](#cli-commands) (9)
-2. [斜线命令](#slash-commands) (33)
-3. [技能](#skills) (29)
+2. [斜线命令](#slash-commands) (45)
+3. [技能](#skills) (40)
 4. [代理](#agents) (5)
 5. [工作流程](#workflows) (5)
-6. [核心规范](#core-standards) (36)
-7. [脚本](#scripts) (39)
+6. [核心规范](#core-standards) (48)
+7. [脚本](#scripts) (41)
 
-**Total Features: 156**
+**Total Features: 182**
 
 ---
 
@@ -50,6 +50,8 @@
 | `--locale` | Locale extension (zh-tw) |
 | `--skills-location` | Skills location (marketplace, user, project, none) [default: marketplace] |
 | `--content-mode` | Content mode for integration files (minimal, index, full) [default: index] |
+| `--agents-md` | Generate AGENTS.md universal summary |
+| `--no-agents-md` | Skip AGENTS.md generation |
 | `-y, --yes` | Use defaults, skip interactive prompts |
 | `-E, --experimental` | Enable experimental features (methodology) |
 
@@ -148,6 +150,7 @@
 
 | Command | 说明 |
 |---------|-------------|
+| `/ac-coverage` | "[UDS] Generate AC-to-test traceability matrix and coverage report" |
 | `/atdd` | [UDS] Guide through Acceptance Test-Driven Development workflow |
 | `/bdd` | [UDS] Guide through Behavior-Driven Development workflow |
 | `/brainstorm` | "[UDS] Structured AI-assisted brainstorming before spec creation" |
@@ -188,31 +191,42 @@
 
 | Skill | 说明 |
 |-------|-------------|
+| `ac-coverage-assistant` | "[UDS] Analyze AC-to-test traceability and coverage" |
 | `ai-collaboration-standards` | Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. |
 | `ai-friendly-architecture` | Design AI-friendly architecture with explicit patterns, layered documentation, and semantic boundaries. |
 | `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, .cursorrules, etc.) with proper structure. |
+| `api-design-assistant` | Guide API design following REST, GraphQL, and gRPC best practices. |
 | `atdd-assistant` | "[UDS] Guide through Acceptance Test-Driven Development workflow" |
 | `audit-assistant` | "[UDS] UDS Health & Feedback System \| UDS 健康檢查與回饋系統" |
 | `bdd-assistant` | "[UDS] Guide through Behavior-Driven Development workflow" |
 | `brainstorm-assistant` | "[UDS] Structured AI-assisted brainstorming before spec creation" |
 | `changelog-guide` | "[UDS] Generate and maintain CHANGELOG.md entries" |
 | `checkin-assistant` | "[UDS] Pre-commit quality gates verification" |
+| `ci-cd-assistant` | Guide CI/CD pipeline design, configuration, and optimization. |
 | `code-review-assistant` | "[UDS] Perform systematic code review with checklist" |
 | `commit-standards` | "[UDS] Generate commit messages following Conventional Commits standard" |
+| `database-assistant` | Guide database design, migration, and query optimization. |
 | `dev-workflow-guide` | "[UDS] Guide for mapping software development phases to UDS commands and features" |
 | `docs-generator` | "[UDS] Generate usage documentation from project sources" |
 | `documentation-guide` | Guide documentation structure, content requirements, and project documentation best practices. |
+| `durable-execution-assistant` | "[UDS] Guide workflow failure recovery with checkpoints, retries, and rollback" |
 | `error-code-guide` | Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. |
 | `forward-derivation` | "[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications" |
 | `git-workflow-guide` | Guide Git branching strategies, branch naming, and merge operations. |
+| `incident-response-assistant` | Guide incident response, root cause analysis, and post-mortem documentation. |
 | `logging-guide` | Implement structured logging with proper log levels and sensitive data handling. |
 | `methodology-system` | "[UDS] Manage development methodology workflow" |
+| `metrics-dashboard-assistant` | "[UDS] Track development metrics, code quality indicators, and project health" |
+| `migration-assistant` | "[UDS] Guide code migration, framework upgrades, and technology modernization" |
+| `pr-automation-assistant` | Guide pull request creation, review automation, and merge strategies. |
 | `project-discovery` | "[UDS] Assess project health, architecture, and risks before adding features" |
 | `project-structure-guide` | Guide for organizing project directories following language-specific best practices. |
 | `refactoring-assistant` | "[UDS] Guide refactoring decisions and strategy selection" |
 | `release-standards` | "[UDS] Guide release process and changelogs" |
 | `requirement-assistant` | "[UDS] Write user stories and requirements following INVEST criteria" |
 | `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logic, Data, and Runtime dimensions" |
+| `security-assistant` | Guide security review and vulnerability assessment following OWASP standards. |
+| `security-scan-assistant` | Guide automated security scanning, dependency auditing, and secret detection. |
 | `spec-driven-dev` | "[UDS] Create or review specification documents for Spec-Driven Development" |
 | `tdd-assistant` | "[UDS] Guide through Test-Driven Development workflow" |
 | `test-coverage-assistant` | "[UDS] Analyze test coverage and provide recommendations" |
@@ -248,27 +262,36 @@
 
 | Standard | 版本 | 说明 |
 |----------|---------|-------------|
+| `acceptance-criteria-traceability` | - |  |
 | `acceptance-test-driven-development` | 1.1.0 |  |
 | `accessibility-standards` | 1.0.0 | This standard defines comprehensive guidelines for creating accessible software  |
+| `agent-dispatch` | 1.0.0 | Define standards for dispatching AI sub-agents in parallel, coordinating their w |
 | `ai-agreement-standards` | 1.0.0 | This standard formalizes the interaction between Human (Acquirer) and AI (Suppli |
 | `ai-friendly-architecture` | 1.0.0 | This standard defines architecture and documentation practices that maximize the |
 | `ai-instruction-standards` | 1.0.0 | This standard defines best practices for creating and maintaining AI instruction |
 | `anti-hallucination` | 1.5.0 | This standard defines strict guidelines for AI assistants to prevent hallucinati |
+| `api-design-standards` | 1.0.0 | This standard defines comprehensive guidelines for designing, building, and main |
 | `behavior-driven-development` | 1.1.0 |  |
+| `branch-completion` | 1.0.0 | Define a standardized workflow for completing development branches, including pr |
+| `change-batching-standards` | - |  |
 | `changelog-standards` | 1.0.2 | This standard defines how to write and maintain a CHANGELOG.md file to communica |
-| `checkin-standards` | 1.4.0 | This standard defines quality gates that MUST be passed before committing code t |
+| `checkin-standards` | 1.5.0 | This standard defines quality gates that MUST be passed before committing code t |
 | `code-review-checklist` | 1.3.0 | This standard provides a comprehensive checklist for reviewing code changes, ens |
 | `commit-message-guide` | 1.3.0 | Standardized commit messages improve code review efficiency, facilitate automate |
 | `context-aware-loading` | 1.0.0 | This standard defines a protocol for AI tools to selectively load development st |
+| `database-standards` | 1.0.0 | This standard defines guidelines for database design, querying, migration, and o |
 | `deployment-standards` | 1.0.0 | This standard defines guidelines for safely deploying software to production, co |
 | `developer-memory` | 1.0.0 | This standard defines a structured system for capturing, retrieving, and surfaci |
 | `documentation-structure` | 1.5.0 | This standard defines a consistent documentation structure for software projects |
 | `documentation-writing-standards` | 1.2.0 | This standard defines documentation requirements based on project types and prov |
-| `error-code-standards` | 1.1.0 |  |
-| `forward-derivation-standards` | 1.1.0 | This standard defines the principles and workflows for Forward Derivation—automa |
+| `error-code-standards` | 1.2.0 |  |
+| `forward-derivation-standards` | 1.2.0 | This standard defines the principles and workflows for Forward Derivation—automa |
 | `git-workflow` | 1.4.0 | This standard defines Git branching strategies and workflows to ensure consisten |
+| `git-worktree` | 1.0.0 | Define a lifecycle for using Git worktrees to isolate development work, ensuring |
 | `logging-standards` | 1.2.0 |  |
+| `model-selection` | 1.0.0 | Define a cost-effective strategy for selecting AI model tiers based on task comp |
 | `performance-standards` | 1.1.0 | This standard defines comprehensive guidelines for software performance engineer |
+| `pipeline-integration-standards` | - |  |
 | `project-context-memory` | 1.1.0 | This standard defines a structured system for capturing, retrieving, and enforci |
 | `project-structure` | 1.2.0 | This standard defines conventions for project directory structure beyond documen |
 | `refactoring-standards` | 2.1.0 | This standard defines comprehensive guidelines for code refactoring, covering ev |
@@ -277,12 +300,15 @@
 | `security-standards` | 1.1.0 | This standard defines comprehensive security guidelines for software development |
 | `spec-driven-development` | 2.1.0 |  |
 | `structured-task-definition` | 1.0.0 |  |
+| `systematic-debugging` | 1.0.0 | Define a structured, four-phase debugging workflow that prevents the common anti |
 | `test-completeness-dimensions` | 1.1.0 | This document defines a systematic framework for evaluating test completeness. I |
 | `test-driven-development` | 1.2.0 |  |
 | `test-governance` | - |  |
 | `testing-standards` | 3.0.0 | This standard defines actionable testing rules and conventions for AI agents and |
+| `verification-evidence` | 1.0.0 | Establish an "Iron Law" that no task can be claimed as complete without verifica |
 | `versioning` | 1.2.0 | This standard defines how to version software releases using Semantic Versioning |
 | `virtual-organization-standards` | 1.0.0 | This standard treats the AI ecosystem as a "Virtual Organization." It defines ho |
+| `workflow-enforcement` | - |  |
 | `workflow-state-protocol` | 1.0.0 |  |
 
 ---
@@ -298,6 +324,7 @@
 | `check-cli-docs-sync.sh` | CLI-to-Documentation Sync Checker |
 | `check-commands-sync.ps1` | Check Commands Sync |
 | `check-commands-sync.sh` | Commands Sync Checker |
+| `check-commit-spec-reference.sh` | Commit-msg Spec Reference Suggestion — WARNING ONLY (non-blocking) |
 | `check-docs-integrity.ps1` | Check Docs Integrity |
 | `check-docs-integrity.sh` | Documentation Integrity Checker |
 | `check-docs-sync.ps1` | Check Docs Sync |
@@ -320,6 +347,7 @@
 | `check-usage-docs-sync.sh` | check-usage-docs-sync.sh |
 | `check-version-sync.ps1` | Check Version Sync |
 | `check-version-sync.sh` | Version Sync Checker |
+| `check-workflow-compliance.sh` | Workflow Compliance Check — WARNING ONLY (non-blocking) |
 | `convert-md-to-yaml.mjs` | Markdown to AI-YAML Conversion Script |
 | `fix-manifest-paths.ps1` | Fix Manifest Paths |
 | `fix-manifest-paths.sh` | Manifest Path Fixer |