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

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

@@ -0,0 +1,88 @@
+---
+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 12207 對應**: 組織專案賦能流程 (6.2)
+
+---
+
+## 目的
+
+本標準將 AI 生態系統視為「虛擬組織」。定義如何將 AI 能力（Skills）、基礎設施和品質保證作為組織資產來管理，確保「虛擬人力」具備能力且符合規範。
+
+---
+
+## 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`、架構文件和標準
+- **規範熟悉**：載入適用的開發標準
+- **歷史認知**：載入專案決策和慣例
+
+## 2. 基礎設施管理
+
+| 基礎設施 | 虛擬對應 | 說明 |
+|----------|----------|------|
+| 辦公空間 | 工作目錄 | 專案根目錄和工作區 |
+| 通訊系統 | Prompt/Context | AI 與人類的溝通管道 |
+| 知識庫 | 文件和標準 | `.standards/`、`core/`、`skills/` |
+| 品保部門 | 測試和 Lint | 自動化品質檢查 |
+
+## 3. 品質保證
+
+### 3.1 品質政策
+
+| 政策 | 實作 |
+|------|------|
+| 程式碼審查 | AI 和人類都必須審查重要變更 |
+| 測試要求 | 新功能必須有對應測試 |
+| 標準遵循 | 所有產出必須符合已安裝的標準 |
+| 持續改善 | 定期回顧和更新標準 |
+
+### 3.2 稽核
+
+定期檢查虛擬組織的健康度：
+
+| 稽核項目 | 頻率 | 負責人 |
+|----------|------|--------|
+| 技能有效性 | 每個版本 | 技術主管 |
+| 標準合規 | 每次提交 | 自動化 |
+| 安全審計 | 每季 | 安全團隊 |
+
+## 相關標準
+
+- [AI 協議標準](ai-agreement-standards.md)
+- [專案情境記憶](project-context-memory.md)
+- [情境感知載入](context-aware-loading.md)

package/bundled/locales/zh-TW/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-TW/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-CN/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-TW/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-tw
 

package/bundled/locales/zh-TW/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-CN/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 |