universal-dev-standards 5.8.0 → 5.11.0

package/bundled/locales/zh-CN/skills/logging-guide/SKILL.md

@@ -283,3 +283,36 @@ logger.error('处理订单失败', {
 此技能採用 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 授权。
 
 **來源**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/logging` completes, the AI assistant should suggest:
+
+> **日誌標準已掌握。建議下一步 / Logging standards understood. Suggested next steps:**
+> - 根據日誌指南在程式碼中實作結構化日誌 ⭐ **Recommended / 推薦** — 立即將日誌標準應用到專案 / Apply logging standards to the project immediately
+> - 執行 `/errors` 設計錯誤碼以配合日誌系統 — 讓錯誤追蹤更有效率 / Make error tracking more efficient
+> - 執行 `/sdd` 將可觀測性需求納入規格 — 確保日誌需求在規格中有定義 / Ensure logging requirements are defined in specs
+
+---
+
+## Related Standards
+
+- [Logging Standards](../../core/logging-standards.md)
+- [Error Code Standards](../../core/error-code-standards.md)
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.0.0 | 2025-12-30 | Initial release |
+
+---
+
+## License
+
+This skill is released under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
+
+**Source**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/locales/zh-CN/skills/project-structure-guide/SKILL.md

@@ -149,3 +149,22 @@ project/
 - [核心：文档结构](../../core/documentation-structure.md)
 - [指南：文件归档决策指南](../../core/guides/file-placement-guide.md)
 - [AI：项目结构选项](../../../../options/project-structure/)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/project-structure` completes, the AI assistant should suggest:
+
+> **專案結構已建立或審查完成。建議下一步 / Project structure created or reviewed. Suggested next steps:**
+> - 執行 `/sdd` 開始規格驅動開發，將專案結構納入正式規格 ⭐ **Recommended / 推薦** — 確保結構決策有規格追蹤 / Ensures structure decisions are tracked in specs
+> - 執行 `/docs` 產生專案文件（README、ARCHITECTURE.md 等） — 讓結構決策有文件記錄 / Document structure decisions
+> - 執行 `/ai-friendly-architecture` 設定 AI 上下文配置 — 讓 AI 助手更好地理解專案結構 / Help AI assistants understand the project structure
+
+---
+
+## Related Standards
+
+- [Core: Project Structure](../../core/project-structure.md)
+- [Core: Documentation Structure](../../core/documentation-structure.md)
+- [Guide: File Placement Decision Guide](../../core/guides/file-placement-guide.md)
+- [AI: Project Structure Options](../../ai/options/project-structure/)

package/bundled/locales/zh-CN/skills/retrospective-assistant/SKILL.md

@@ -28,3 +28,41 @@ description: |
 
 - 核心规范：[retrospective-standards.md](../../../../core/retrospective-standards.md)
 - 详细指南：[guide.md](./guide.md)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/retrospective` completes:
+
+> **Retrospective complete. Suggested next steps:**
+> - Commit the retrospective report: `/commit`
+> - Create ADRs for architectural decisions identified: `/adr`
+> - Track action items in your issue tracker
+> - Schedule next retrospective
+
+> **回顧完成。建議下一步：**
+> - 提交回顧報告：`/commit`
+> - 為識別的架構決策建立 ADR：`/adr`
+> - 在 issue tracker 中追蹤行動項目
+> - 排定下次回顧
+
+## AI Agent Behavior | AI 代理行為
+
+When `/retrospective` is invoked:
+
+1. **Check type** — Sprint (default) or Release
+2. **Gather data** — Scan git log, check `docs/retrospectives/` for previous actions
+3. **Guide technique** — Use Start-Stop-Continue by default, or specified technique
+4. **Generate report** — Write to `docs/retrospectives/RETRO-YYYY-MM-DD-[type].md`
+5. **Review past actions** — Check previous retro for open action items
+6. **Offer next steps** — Show guidance above
+
+When `/retrospective actions` is invoked:
+1. Scan `docs/retrospectives/` for all retro files
+2. Parse action items from each
+3. Display open/in-progress items as table
+
+## Reference | 參考
+
+- Core Standard: [retrospective-standards.md](../../core/retrospective-standards.md)
+- Detailed Guide: [guide.md](./guide.md)

package/bundled/locales/zh-CN/skills/testing-guide/SKILL.md

@@ -232,3 +232,39 @@ test('method_scenario_expected', () => {
 本 Skill 以 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 授权發布。
 
 **來源**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/testing` completes, the AI assistant should suggest:
+
+> **測試標準與最佳實踐已掌握。建議下一步 / Testing standards and best practices understood. Suggested next steps:**
+> - 執行 `/tdd` 開始測試驅動開發（紅-綠-重構循環） ⭐ **Recommended / 推薦** — 將測試知識立即轉化為實踐 / Turn testing knowledge into practice immediately
+> - 執行 `/coverage` 分析目前程式碼覆蓋率 — 找出測試缺口 / Identify testing gaps
+> - 執行 `/bdd` 撰寫行為驅動的 Given-When-Then 場景 — 從使用者角度定義測試 / Define tests from user perspective
+
+---
+
+## Related Standards
+
+- [Testing Standards](../../core/testing-standards.md) - Actionable rules
+- [Testing Theory](./testing-theory.md) - Educational knowledge base
+- [Code Review Checklist](../../core/code-review-checklist.md)
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.2.0 | 2026-01-29 | Added links to new testing-theory.md knowledge base |
+| 1.1.0 | 2025-12-29 | Added Testing Theory Essentials YAML section |
+| 1.0.0 | 2025-12-24 | Initial: Standard sections (Purpose, Related Standards, Version History, License) |
+
+---
+
+## License
+
+This skill is released under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
+
+**Source**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/locales/zh-TW/CHANGELOG.md

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 5.8.0
-translation_version: 5.8.0
-last_synced: 2026-05-12
+source_version: 5.11.0
+translation_version: 5.11.0
+last_synced: 2026-05-14
 status: current
 ---
 
@@ -17,6 +17,41 @@ status: current
 
 ## [Unreleased]
 
+## [5.11.0] - 2026-05-14
+
+### 新增 / Added
+- **`spec-driven-development`** SPEC Type Agent 變體：`acceptance-criteria-traceability.ai.yaml` 與 SDD 模板新增 `spec-type: feature | agent | infrastructure` 欄位，以及 Agent SPEC 五段式模板（能力範圍 / 決策邊界 / 可觀測性 / 失敗模式 / 跨 Agent 不變量）。讓 Builder/QA/Planner 風格的 SPEC 可獨立於 feature SPEC 追蹤，並透過新增的 `agent-id` 欄位連回特定 Agent。(XSPEC-205)
+- **`reverse-engineering-standards`** 移植清單雙向驗證：新增路由驅動的發現方法（禁止以 filesystem-glob 為起點）、target→source 雙向掃描，以及對「無對應來源產物」的發現的 `[GAP]` 標記協議。搭配 `testing.ai.yaml` 新增 `migration_testing` 區段，要求以 3 步驟 schema parity pattern 並由 CI gate 強制執行。關閉 UDS Issue #96 與 #97。(XSPEC-206)
+
+### 修復 / Fixed
+- **`uds update` 對 schema 3.x manifest 誤報「CLAUDE.md.md：無法判斷來源」還原失敗**（`cli/src/utils/integration-generator.js`、`cli/src/commands/update.js`）：schema 3.x manifest 在 `manifest.integrations` 存的是**檔名**（如 `"CLAUDE.md"`）而非工具名。`integration-generator.js:56` 的 `getToolFileName` fallback 無條件附加 `".md"`，導致 `getToolFilePath("CLAUDE.md")` 回傳 `"CLAUDE.md.md"`，被當成遺失檔案而無法還原（`getSourcePathFromRelative` 對該合成路徑沒有 mapping）。Commit `79532b3`（5.10.0）修了反向案例（工具名輸入），但漏這個檔名變體。修補：從 `SUPPORTED_AI_TOOLS` 預計算 `KNOWN_TOOL_FILES`，對已知整合檔名或已含已知副檔名（`.md`/`.yaml`/`.yml`/`.json`）的輸入短路回傳。`integration-generator.test.js` 新增 5 個 regression test。(XSPEC-208 BUG-208-01)
+- **`uds update` / `uds check` 誤報「Integration UDS Block Integrity：GEMINI.md/AGENTS.md 遺失」警告**（`cli/src/commands/update.js`、`cli/src/i18n/messages.js`）：`manifest.integrationBlockHashes` 每次安裝都累加但從不清理。當 `manifest.aiTools` 縮減（如 `["claude-code","gemini-cli"]` → `["claude-code"]`），GEMINI.md 的 hash 仍殘留，`check.js:1491 checkIntegrationBlocksIntegrity` 誤報該檔遺失。修補：在 integration 重生步驟後，依 `manifest.aiTools`（宣告的設定，而非 `results.integrations`，後者在暫時性寫入失敗時會 over-prune）反推預期檔名集合並移除孤兒 hash。被清理的檔名透過新增 i18n key `prunedOrphanedBlockHashes`（en / zh-TW / zh-CN）回報。`update.test.js` 新增 3 個 regression test。在 machine-setup `uds update` 5.1.0-beta.4 → 5.10.0 觸發；於 5.10.0 → 5.11.0 驗證修復。(XSPEC-208 BUG-208-02)
+
+## [5.10.0] - 2026-05-13
+
+### 新增
+- **`multi-environment-e2e-testing`**（`ai/standards/multi-environment-e2e-testing.ai.yaml`）：新增多部署目標 E2E 測試設定標準。核心原則：「執行指令即文件」。涵蓋：BASE_URL 內嵌於測試框架設定（不依賴 .env）；各環境含自我檢查前置條件的 runner 腳本；環境能力矩陣 commit 至 repo；CI Gate 映射；憑證處理規則。關閉 UDS Issue #95。（XSPEC-204）
+
+### 修改
+- **`mock-boundary`**（v1.0.0 → v1.1.0）：新增 Level 1 / Level 2 mock 層次區分。Level 1 = 程式碼級 mock，受 STUB 標記規則管制。Level 2 = 基礎設施級 stub server（WireMock、MockSoap），受環境分層規則管制，**不受** STUB 部署封鎖規則管轄。新增 `external_dependency_testability_matrix` 模板（✅/⚠️/❌ 各服務 × 環境）。新增規則：`level-2-stub-server-rules`、`no-stub-server-in-prd`。關閉 UDS Issue #94 盲點二。（XSPEC-204）
+- **`deployment-standards`**（v1.0.0 → v1.1.0）：新增 `environment_stratification_matrix` 區塊——有外部依賴的專案必須在測試計畫階段建立此矩陣；模板包含 10 大流程 × 三層環境對照表。新增 `stub_server_cicd_rules` 區塊——選項 A（sidecar 部署）/ 選項 B（推遲至 PRD Smoke）；production artifact 排除規則；PRD 禁止規則；禁止狀態定義。關閉 UDS Issue #94 盲點一與盲點三。（XSPEC-204）
+- **`verification-evidence`**（v1.0.0 → v1.1.0）：新增 Iron Law（環境維度）：有外部服務依賴的 AC 驗收證據必須標明 `environment_layer`。在 evidence format 新增 `environment_layer` 欄位（有外部服務依賴的功能為必填）。新增規則 VE-005、VE-006。（XSPEC-204）
+- **`test-completeness-dimensions`**（v1.2.0 → v1.3.0）：新增第 11 維度：**環境可驗證性（Environment Verifiability）**——有外部服務依賴的 AC 須標明最低可驗證環境層次（local/UAT/PRD），追蹤 PRD-only 項目，要求 smoke 測試計畫。更新功能類型對照：外部整合 → [1,3,7,11]；新增類型「外部依賴工作流程」→ [1,3,4,5,9,10,11]。更新 use-checklist 規則。（XSPEC-204）
+
+### 修正
+- **`uds update` 整合工具名稱誤當檔案路徑的假警報**：`manifest.integrations` 包含 `"claude-code"`、`"opencode"` 等工具識別碼時，update 指令將其直接推入 `allTrackedFiles` 當作檔案路徑，導致 `existsSync("claude-code")` 回傳 false，觸發假的「⚠ N 個檔案缺失」警告與「✗ claude-code: 無法判斷來源」還原失敗。修正方式：先用 `getToolFilePath(int)` 轉換為真實路徑（如 `"CLAUDE.md"`）再推入清單；無法對應的 entry 跳過。問題出現於 `uds update` 5.7.2 → 5.8.0。
+
+## [5.9.0] - 2026-05-13
+
+### 新增
+- **`feature-discovery-standards`**（`ai/standards/feature-discovery-standards.ai.yaml`、`core/feature-discovery-standards.md`）：新增標準，定義遺留系統功能窮舉發現的語言無關方法論。確立 **Deterministic-First 原則**（AI 在 Discovery Phase 禁止透過推論產生功能清單）。定義七種軟體形式分類法（web/cli/gui/daemon/library/mobile/embedded），各含偵測信號與提取工具。定義五個靜態地基（入口點→呼叫圖→字串挖掘→資源檔→外部介面）、動態觀察協議（三平台）、人力觀察協議（confidence: 0.7 規則）與多層交叉比對矩陣模板。流水線位置：Discovery → feature-manifest → behavior-snapshot。（XSPEC-202）
+- **`ai/language-packs/language-pack-php-to-csharp.ai.yaml`**：UDS 首個語言包，提供 PHP→C#（ASP.NET Core）移植風險標籤，含 7 個標籤（SESSION_HANDLING、ORM_DIFFERENCES、TIMEZONE_HANDLING、FILE_UPLOAD_PATH、REGEX_DIFFERENCES、ARRAY_FUNCTIONS、EXCEPTION_HIERARCHY）各附詳細說明。（XSPEC-203）
+- **`ai/language-packs/README.md`**：語言包命名規範、使用指南與貢獻說明。（XSPEC-203）
+
+### 變更
+- **`feature-manifest-standard`**（v1.0.0 → v1.1.0）：重構 `migration_risks` 為語言無關架構。移除硬編的 `php_to_csharp` 區塊（已移入 `ai/language-packs/`）。新增 `language_packs` Extension Point（`extension_point: true`）。新增三個通用風險標籤：CONCURRENCY_MODEL、PACKAGE_ECOSYSTEM、TYPE_SYSTEM。（XSPEC-203）
+- **`behavior-snapshot`**（v1.0.0 → v1.1.0）：從純 HTTP 擴充為多模態格式。新增 `adapter` 欄位（預設 `http`，向下相容）。新增 `adapters` 區段，含 4 種 schema：`http` / `cli` / `file` / `event`。新增 `adapter-selection` 與 `backward-compatibility` 規則。現有不含 `adapter` 欄位的 HTTP 快照無需修改。（XSPEC-203）
+
 ## [5.8.0] - 2026-05-12
 
 ### 新增

package/bundled/locales/zh-TW/CLAUDE.md

@@ -14,7 +14,7 @@ status: current
 
 Universal Development Standards 是一個語言無關、框架無關的文件化標準框架。它提供：
 
-- **核心規範** (`core/`)：71 個基礎開發標準
+- **核心規範** (`core/`)：125 個基礎開發標準
 - **AI 技能** (`skills/`)：用於 AI 輔助開發的 Claude Code 技能
 - **CLI 工具** (`cli/`)：用於採用標準的 Node.js CLI
 - **整合** (`integrations/`)：各種 AI 工具的配置

package/bundled/locales/zh-TW/README.md

@@ -14,7 +14,7 @@ status: current
 
 > **語言**: [English](../../README.md) | 繁體中文 | [简体中文](../zh-CN/README.md)
 
-**版本**: 5.8.0 | **發布日期**: 2026-04-13 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
+**版本**: 5.11.0 | **發布日期**: 2026-05-14 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
 
 語言無關、框架無關的軟體專案文件標準。透過 AI 原生工作流，確保不同技術堆疊之間的一致性、品質和可維護性。
 
@@ -63,8 +63,8 @@ npx universal-dev-standards init
 <!-- UDS_STATS_TABLE_START -->
 | 類別 | 數量 | 說明 |
 |----------|-------|-------------|
-| **核心標準** | 78 | 通用開發準則 |
-| **AI Skills** | 48 | 互動式技能 |
+| **核心標準** | 125 | 通用開發準則 |
+| **AI Skills** | 54 | 互動式技能 |
 | **斜線命令** | 48 | 快速操作 |
 | **CLI 指令** | 6 | list, init, configure, check, update, skills |
 <!-- UDS_STATS_TABLE_END -->

package/bundled/locales/zh-TW/SECURITY.md

@@ -13,8 +13,7 @@ status: current
 <!-- UDS_SUPPORTED_VERSIONS_START -->
 | 版本 | 支援狀態 |
 |------|--------|
-| 5.1.0-beta.5 | ✅ 預發布版本 |
-| 5.0.0 | ✅ 最新正式版 |
+| 5.11.0 | ✅ 最新正式版 |
 | < 5.0.0 | ❌ 已終止支援 |
 <!-- UDS_SUPPORTED_VERSIONS_END -->
 

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

@@ -1,14 +1,6 @@
----
-source: ../../../docs/CHEATSHEET.md
-source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-04-22
-status: current
----
-
 # UDS 速查表
 
-> Quick reference for all UDS features | Last updated: 2026-03-24
+> Quick reference for all UDS features | Last updated: 2026-05-14
 
 **Language**: [English](../../../docs/CHEATSHEET.md) | 繁體中文 | [简体中文](../../zh-CN/docs/CHEATSHEET.md)
 
@@ -33,15 +25,19 @@ status: current
 | Command | 說明 |
 |---------|-------------|
 | `/ac-coverage` | "[UDS] Generate AC-to-test traceability matrix and coverage report" |
+| `/api-design` | "[UDS] Guide API design following REST, GraphQL and gRPC best practices" |
 | `/atdd` | [UDS] Guide through Acceptance Test-Driven Development workflow |
+| `/audit` | "[UDS] UDS health check and feedback system, diagnose installation integrity and detect development patterns" |
 | `/bdd` | [UDS] Guide through Behavior-Driven Development workflow |
 | `/brainstorm` | "[UDS] Structured AI-assisted brainstorming before spec creation" |
 | `/changelog` | "[UDS] Generate and maintain CHANGELOG.md entries" |
 | `/check` | [UDS] Verify standards adoption status |
 | `/checkin` | "[UDS] Pre-commit quality gates verification" |
+| `/ci-cd` | "[UDS] Guide CI/CD pipeline design, configuration and optimization" |
 | `/commit` | [UDS] Generate commit messages following Conventional Commits standard |
 | `/config` | [UDS] Configure project development standards |
 | `/coverage` | [UDS] Analyze test coverage and provide recommendations |
+| `/database` | "[UDS] Guide database design, migration planning and query optimization" |
 | `/derive-all` | [UDS] Derive all test structures (BDD, TDD, ATDD) from SDD specification |
 | `/derive-atdd` | [UDS] Derive ATDD acceptance tests from SDD specification |
 | `/derive-bdd` | [UDS] Derive BDD Gherkin scenarios from SDD specification |
@@ -51,9 +47,16 @@ status: current
 | `/discover` | "[UDS] Assess project health, architecture, and risks before adding features" |
 | `/docgen` | "[UDS] Generate usage documentation from project sources" |
 | `/docs` | [UDS] Manage, guide, and generate documentation. |
+| `/durable` | "[UDS] Guide workflow failure recovery with checkpoints, retries and rollback strategies" |
+| `/e2e` | [UDS] Generate E2E test skeletons from BDD scenarios with framework detection |
 | `/guide` | [UDS] Access Universal Development Standards guides and references. |
+| `/incident` | "[UDS] Guide incident response, root cause analysis and post-mortem documentation" |
 | `/init` | [UDS] Initialize development standards in current project |
 | `/methodology` | [UDS] Manage development methodology workflow |
+| `/metrics` | "[UDS] Track development metrics, code quality indicators and project health" |
+| `/migrate` | "[UDS] Guide code migration, framework upgrades and technology modernization" |
+| `/observability` | "[UDS] Guide observability setup, metrics design, alerting, and maturity assessment" |
+| `/pr` | "[UDS] Guide Pull Request creation, review automation and merge strategies" |
 | `/refactor` | [UDS] Guide refactoring decisions and strategy selection |
 | `/release` | [UDS] Manage release process and changelogs. |
 | `/requirement` | [UDS] Write user stories and requirements following INVEST criteria |
@@ -62,8 +65,12 @@ status: current
 | `/reverse-tdd` | [UDS] Analyze BDD-TDD coverage gaps |
 | `/reverse` | [UDS] Reverse engineer code to Specs, BDD, or TDD coverage. |
 | `/review` | [UDS] Perform systematic code review with checklist |
+| `/runbook` | "[UDS] Guide runbook creation, maintenance, drills, and coverage reporting" |
+| `/scan` | "[UDS] Guide automated security scanning, dependency auditing and secret detection" |
 | `/sdd-retro` | [UDS] Create retroactive specs for untracked feat/fix commits |
 | `/sdd` | [UDS] Create or review specification documents for Spec-Driven Development |
+| `/security` | "[UDS] Guide security review and vulnerability assessment following OWASP standards" |
+| `/slo` | "[UDS] Guide SLI selection, SLO setting, and Error Budget management" |
 | `/tdd` | [UDS] Guide through Test-Driven Development workflow |
 | `/update` | [UDS] Update development standards to latest version |
 
@@ -71,10 +78,11 @@ status: current
 
 | Skill | 說明 |
 |-------|-------------|
-| `ac-coverage-assistant` | "[UDS] Analyze AC-to-test traceability and coverage" |
+| `ac-coverage` | "[UDS] Analyze AC-to-test traceability and coverage" |
+| `adr-assistant` | [UDS] Create, manage, and track Architecture Decision Record |
 | `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 |
+| `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, AGENTS. |
 | `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 健康檢查與回饋系統" |
@@ -85,29 +93,42 @@ status: current
 | `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 |
+| `contract-test-assistant` | [UDS] Guide contract testing strategy for APIs and microserv |
 | `database-assistant` | Guide database design, migration, and query optimization. |
+| `deploy-assistant` | Guide reliable deployments without CI/CD platforms (GitHub A |
+| `dev-methodology` | "[UDS] Manage development methodology workflow" |
 | `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 |
+| `e2e-assistant` | "[UDS] Generate E2E test skeletons from BDD scenarios" |
 | `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 |
+| `journey-test-assistant` | "[UDS] 從專案描述生成連貫使用者旅程測試計畫（TESTPLAN）與 E2E 骨架" |
 | `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 |
+| `observability-assistant` | Guide observability setup, metrics design, and alerting conf |
+| `orchestrate` | Orchestrate multi-task execution plans using Claude's native |
+| `plan` | Generate plan.json from Spec documents, OpenSpec changes, or |
 | `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- |
+| `push` | AI-assisted safety layer for git push operations with qualit |
 | `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  |
+| `retrospective-assistant` | [UDS] Guide structured team retrospectives for Sprint and Re |
 | `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logi |
+| `runbook-assistant` | Guide runbook creation, maintenance, and drill exercises. |
 | `security-assistant` | Guide security review and vulnerability assessment following |
 | `security-scan-assistant` | Guide automated security scanning, dependency auditing, and  |
+| `skill-builder` | "[UDS] Identify repeated processes and build Skills with the |
+| `slo-assistant` | Guide SLI selection, SLO setting, and Error Budget managemen |
+| `spec-derivation` | "[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables f |
 | `spec-driven-dev` | "[UDS] Create or review specification documents for Spec-Dri |
+| `sweep` | Scan codebase for debug artifacts and code quality issues; o |
 | `tdd-assistant` | "[UDS] Guide through Test-Driven Development workflow" |
 | `test-coverage-assistant` | "[UDS] Analyze test coverage and provide recommendations" |
 | `testing-guide` | Testing pyramid and test writing standards for UT/IT/ST/E2E. |
@@ -139,46 +160,123 @@ status: current
 | `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 |
+| `adr-standards` | Architecture Decision Records capture the context, |
+| `adversarial-test` | 對抗性測試標準 |
+| `agent-behavior-discipline` | This standard defines four behavioral disciplines  |
+| `agent-communication-protocol` | Define a unified communication protocol for AI age |
 | `agent-dispatch` | Define standards for dispatching AI sub-agents in  |
 | `ai-agreement-standards` | This standard formalizes the interaction between H |
+| `ai-command-behavior` | This standard defines a structure for specifying A |
 | `ai-friendly-architecture` | This standard defines architecture and documentati |
 | `ai-instruction-standards` | This standard defines best practices for creating  |
+| `ai-response-navigation` | This standard defines navigation behavior for AI r |
+| `alerting-standards` | Alerting Standards |
 | `anti-hallucination` | This standard defines strict guidelines for AI ass |
+| `anti-sycophancy-prompting` | This standard defines techniques and rules for des |
 | `api-design-standards` | This standard defines comprehensive guidelines for |
 | `behavior-driven-development` | Behavior-Driven Development (BDD) Standards |
+| `behavior-snapshot` | Behavior Snapshot Standard |
 | `branch-completion` | Define a standardized workflow for completing deve |
+| `browser-compatibility-standards` | This standard defines supported browser and device |
+| `capability-declaration` | Capability Declaration Standard |
+| `cd-deployment-strategies` | CD Deployment Strategies（CD 部署策略） |
 | `change-batching-standards` | Change Batching Standards |
 | `changelog-standards` | This standard defines how to write and maintain a  |
+| `chaos-engineering-standards` | Chaos Engineering Standards |
+| `chaos-injection-tests` | Chaos Injection Tests |
 | `checkin-standards` | This standard defines quality gates that MUST be p |
+| `circuit-breaker` | Circuit Breaker Standard |
 | `code-review-checklist` | This standard provides a comprehensive checklist f |
 | `commit-message-guide` | Standardized commit messages improve code review e |
+| `container-security` | 容器安全標準 |
+| `containerization-standards` | Containerization Standards |
 | `context-aware-loading` | This standard defines a protocol for AI tools to s |
+| `contract-testing-standards` | Contract testing verifies that a provider (API ser |
+| `cost-budget-test` | Cost Budget Test Standards |
+| `cross-flow-regression` | This standard defines cross-flow regression testin |
+| `data-migration-testing` | Data Migration Testing |
 | `database-standards` | This standard defines guidelines for database desi |
 | `deployment-standards` | This standard defines guidelines for safely deploy |
+| `deprecation-standards` | Deprecation & Sunset Standards |
+| `design-document-standards` | Design Document Standards |
 | `developer-memory` | This standard defines a structured system for capt |
+| `disaster-recovery-drill` | Disaster Recovery Drill Standards |
+| `documentation-lifecycle` | This standard defines **when** to update documenta |
 | `documentation-structure` | This standard defines a consistent documentation s |
 | `documentation-writing-standards` | This standard defines documentation requirements b |
+| `dual-phase-output` | Dual-Phase LLM Output Standard |
+| `environment-standards` | Environment Management Standards |
 | `error-code-standards` | Error Code Standards |
+| `estimation-standards` | Estimation Standards |
+| `execution-history` | Execution History Repository Standards |
+| `failure-source-taxonomy` | Failure Source Taxonomy Standard |
+| `feature-flag-standards` | Feature Flag Management Standards |
+| `feature-manifest-standard` | Feature Manifest Standard |
+| `flaky-test-management` | Flaky Test Management Standards |
+| `flow-based-testing` | This document defines a systematic methodology for |
 | `forward-derivation-standards` | This standard defines the principles and workflows |
+| `frontend-design-standards` | This standard defines a machine-readable frontend  |
+| `full-coverage-testing` | Full Coverage Testing Standards |
 | `git-workflow` | This standard defines Git branching strategies and |
 | `git-worktree` | Define a lifecycle for using Git worktrees to isol |
+| `governance-layer` | A governance layer provides a shared anchor for al |
+| `health-check-standards` | Health Check Standards |
+| `immutability-first` | Immutability-First Architecture Standard |
+| `knowledge-transfer-standards` | Knowledge Transfer Standards |
+| `llm-output-validation` | LLM 輸出驗證標準 |
 | `logging-standards` | Logging Standards |
+| `mock-boundary` | This document defines rules for what can and canno |
 | `model-selection` | Define a cost-effective strategy for selecting AI  |
+| `mutation-testing` | Mutation testing evaluates test suite effectivenes |
+| `no-cicd-deployment` | No-CI/CD Deployment Strategy |
+| `observability-standards` | Observability Standards |
+| `packaging-standards` | This standard defines a Recipe-based packaging fra |
 | `performance-standards` | This standard defines comprehensive guidelines for |
 | `pipeline-integration-standards` | Pipeline Integration Standards |
+| `pipeline-security-gates` | Pipeline Security Gates（CI Pipeline 安全檢查點） |
+| `policy-as-code-testing` | Policy as Code 測試標準 |
+| `postmortem-standards` | Postmortem Standards (Blameless Post-Incident Review) |
+| `privacy-standards` | Privacy Standards |
 | `project-context-memory` | This standard defines a structured system for capt |
 | `project-structure` | This standard defines conventions for project dire |
+| `prompt-regression` | Prompt Regression Standards |
+| `property-based-testing` | Property-Based Testing Standards |
+| `recovery-recipe-registry` | Recovery Recipe Registry Standard |
 | `refactoring-standards` | This standard defines comprehensive guidelines for |
+| `release-quality-manifest` | Release Quality Manifest |
+| `release-readiness-gate` | This standard defines a **single, aggregated Relea |
+| `replay-test` | Replay Test Standards |
 | `requirement-engineering` | Requirement Engineering Standards |
+| `retrospective-standards` | Retrospectives are structured team reflections tha |
+| `retry-standards` | Retry Standards |
 | `reverse-engineering-standards` | This standard defines the principles, workflows, a |
+| `rollback-standards` | Rollback Standards（回滾標準） |
+| `runbook-standards` | Runbook Standards |
+| `sast-advanced` | This standard defines Advanced Static Application  |
+| `secure-op` | Secure-Op：AI Agent 安全操作標準 |
+| `security-decision` | Security Decision Standard |
 | `security-standards` | This standard defines comprehensive security guide |
+| `security-testing` | This document defines the security testing methodo |
+| `server-ops-security` | 伺服器操作安全標準 |
+| `skill-standard-alignment-check` | Skill-Standard Alignment Check |
+| `slo-standards` | SLO Standards (Service Level Objectives) |
+| `smoke-test` | Smoke Test Standards |
 | `spec-driven-development` | Spec-Driven Development (SDD) Standards |
+| `standard-admission-criteria` | Standard Admission Criteria |
+| `standard-lifecycle-management` | Standard Lifecycle Management |
 | `structured-task-definition` | Structured Task Definition Standards |
+| `supply-chain-attestation` | Supply Chain Attestation Standards |
+| `supply-chain-security-standards` | Supply Chain Security Standards |
 | `systematic-debugging` | Define a structured, four-phase debugging workflow |
+| `tech-debt-standards` | Tech Debt Management Standards |
 | `test-completeness-dimensions` | This document defines a systematic framework for e |
+| `test-data-standards` | Test Data Standards |
 | `test-driven-development` | Test-Driven Development (TDD) Standards |
 | `test-governance` | Test Governance Standards |
 | `testing-standards` | This standard defines actionable testing rules and |
+| `timeout-standards` | Timeout Standards |
+| `token-budget` | Token Budget Zone Standard |
+| `translation-lifecycle-standards` | Translation lifecycle standards: MISSING vs OUTDAT |
 | `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 |
@@ -190,19 +288,29 @@ status: current
 | Script | 說明 |
 |--------|-------------|
 | `add-industry-standards-metadata.mjs` | Add industry standards metadata to core/ |
+| `aggregate-effectiveness.mjs` | Aggregate Standards Effectiveness Reports |
+| `analyze-hook-stats.mjs` | Hook Statistics Analyzer (SPEC-SELFDIAG-001 REQ-7, |
+| `bump-version.mjs` | Build a platform-aware shell command for a .sh scr |
+| `bump-version.sh` | DEPRECATED: Use 'node scripts/bump-version.mjs <ve |
 | `check-ai-agent-sync.ps1` | Check Ai Agent Sync |
 | `check-ai-agent-sync.sh` | AI Agent Sync Checker |
+| `check-ai-behavior-sync.sh` | DEPRECATED: Use 'npx tsx scripts/check-ai-behavior |
 | `check-cli-docs-sync.ps1` | Check Cli Docs Sync |
 | `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-commit-spec-reference.sh` | DEPRECATED: Use 'npx tsx scripts/check-commit-spec |
 | `check-docs-integrity.ps1` | Check Docs Integrity |
 | `check-docs-integrity.sh` | Documentation Integrity Checker |
 | `check-docs-sync.ps1` | Check Docs Sync |
 | `check-docs-sync.sh` | Documentation Sync Checker |
+| `check-external-references.mjs` | External Reference Checker (SPEC-SELFDIAG-001 REQ- |
+| `check-flow-gate-report.sh` | DEPRECATED: Use 'npx tsx scripts/check-flow-gate-r |
+| `check-integration-commands-sync.sh` | DEPRECATED: Use 'npx tsx scripts/check-integration |
 | `check-orphan-specs.ps1` | Check Orphan Specs |
 | `check-orphan-specs.sh` | Orphan Spec Detection Script |
+| `check-registry-completeness.sh` | DEPRECATED: Use 'npx tsx scripts/check-registry-co |
+| `check-release-readiness-signoff.sh` | DEPRECATED: Use 'npx tsx scripts/check-release-rea |
 | `check-scope-sync.ps1` | Check Scope Sync |
 | `check-scope-sync.sh` | Scope Consistency Check Script |
 | `check-skill-next-steps-sync.ps1` | Check Skill Next Steps Sync |
@@ -219,11 +327,15 @@ status: current
 | `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 |
+| `check-workflow-compliance.sh` | DEPRECATED: Use 'npx tsx scripts/check-workflow-co |
 | `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 |
 | `generate-docs.mjs` | Generate Docs |
+| `generate-version-manifest.mjs` | Generate Version Manifest (SPEC-SELFDIAG-001 REQ-9 |
+| `install-hooks.mjs` | Install Hooks |
+| `install-hooks.sh` | DEPRECATED: Use 'node scripts/install-hooks.mjs' i |
+| `pre-commit.mjs` | Build a platform-aware shell command for a .sh scr |
 | `pre-release-check.ps1` | Pre Release Check |
 | `pre-release-check.sh` | Pre-release Check Script |
 | `pre-release.ps1` | Pre-Release Preparation Script for Universal Devel |