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

package/bundled/skills/ac-coverage-assistant/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: ac-coverage
+scope: universal
+description: "[UDS] Analyze AC-to-test traceability and coverage"
+allowed-tools: Read, Grep, Glob
+argument-hint: "[spec file path | 規格檔案路徑]"
+---
+
+# AC Coverage Assistant | AC 覆蓋率助手
+
+Analyze Acceptance Criteria (AC) to test traceability and generate coverage reports.
+
+分析驗收條件（AC）與測試之間的追蹤關係，並產生覆蓋率報告。
+
+## What This Does vs `/coverage` | 與 `/coverage` 的區別
+
+| Aspect | `/coverage` | `/ac-coverage` |
+|--------|-------------|----------------|
+| **Scope** | Code-level (line/branch/function) | Requirement-level (AC-to-test) |
+| **Input** | Source code + test runner | SPEC file + test annotations |
+| **Question** | "How much code is tested?" | "Which AC have tests?" |
+| **Output** | Coverage percentages | Traceability matrix + gap report |
+
+## Workflow | 工作流程
+
+1. **Parse SPEC** — Extract AC definitions (AC-1, AC-2, ...) from the specification file
+2. **Scan Tests** — Search test files for `@AC` and `@SPEC` annotations using standard linking conventions
+3. **Build Matrix** — Map each AC to its test references (file, test name, line)
+4. **Classify Status** — Mark each AC as ✅ covered, ⚠️ partial, or ❌ uncovered
+5. **Calculate Coverage** — Apply formula: `Coverage % = (covered + partial × 0.5) / total × 100`
+6. **Generate Report** — Output standardized Markdown report
+
+## Linking Convention | 標註慣例
+
+Tests MUST reference their source AC using standard annotations:
+
+```typescript
+// TypeScript/JavaScript
+describe('AC-1: User login with valid credentials', () => {
+  // @AC AC-1
+  // @SPEC SPEC-001
+  it('should redirect to dashboard on successful login', () => { ... });
+});
+```
+
+```python
+# Python
+class TestAC1_UserLogin:
+    """AC-1: User login with valid credentials
+    @AC AC-1
+    @SPEC SPEC-001
+    """
+    def test_redirect_to_dashboard(self): ...
+```
+
+```gherkin
+# BDD Feature
+@SPEC-001 @AC-1
+Scenario: User login with valid credentials
+```
+
+## Coverage Thresholds | 覆蓋率門檻
+
+| Threshold | Default Value | Enforcement |
+|-----------|---------------|-------------|
+| **Check-in** | 80% | Required for feature branch merge |
+| **Release** | 100% | Required for production release |
+| **Warning** | 60% | Triggers coverage warning |
+
+Thresholds are configurable via `--threshold` parameter or project configuration.
+
+## Report Format | 報告格式
+
+The generated report follows the standard format from `core/acceptance-criteria-traceability.md`:
+
+```markdown
+# AC Coverage Report
+
+**Specification**: SPEC-001 — Feature Name
+**Generated**: 2026-03-18
+**Coverage**: 75% (6/8 AC)
+
+## Summary
+
+| Status | Count | Percentage |
+|--------|-------|------------|
+| ✅ Covered | 5 | 62.5% |
+| ⚠️ Partial | 2 | 25.0% |
+| ❌ Uncovered | 1 | 12.5% |
+
+## Traceability Matrix
+
+| AC-ID | Description | Status | Test Reference |
+|-------|-------------|--------|----------------|
+| AC-1 | Login with valid credentials | ✅ | auth.test.ts:15 |
+| AC-2 | Reject invalid credentials | ✅ | auth.test.ts:32 |
+| ...   | ...                        | ... | ... |
+
+## Gaps
+- **AC-8**: Social login — Blocked by OAuth sandbox
+
+## Action Items
+1. [ ] AC-8: Set up OAuth sandbox (ETA: TBD)
+```
+
+## Next Steps Guidance | 下一步引導
+
+After `/ac-coverage` completes, the AI assistant should suggest:
+
+> **AC 覆蓋率分析完成。建議下一步 / AC coverage analysis complete. Suggested next steps:**
+> - 覆蓋率達標 → 執行 `/checkin` 品質關卡 — Coverage meets threshold → Run `/checkin` quality gates
+> - 有未覆蓋 AC → 執行 `/derive-tdd` 補齊測試 — Uncovered AC found → Run `/derive-tdd` to add tests
+> - 有部分覆蓋 AC → 檢查缺少的邊界情況 — Partial AC → Review missing edge cases
+
+## Reference | 參考
+
+- Core standard: [acceptance-criteria-traceability.md](../../core/acceptance-criteria-traceability.md)
+- SPEC: [SPEC-AC-COVERAGE.md](../../docs/specs/skills/SPEC-AC-COVERAGE.md)
+- Related: [test-coverage-assistant](../test-coverage-assistant/SKILL.md) (code-level coverage)
+- Related: [checkin-assistant](../checkin-assistant/SKILL.md) (quality gates)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/ac-coverage`](../commands/ac-coverage.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/ac-coverage`](../commands/ac-coverage.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/ai-collaboration-standards/SKILL.md

@@ -16,6 +16,16 @@ description: |
 
 ---
 
+## AI Skills Hierarchy | AI 技能層級
+
+This skill is part of a three-layer AI collaboration system:
+
+| Layer | Skill | Question it Answers | 回答的問題 |
+|-------|-------|-------------------|-----------|
+| **Behavior** (Immediate) | `/ai-collaboration` (this) | "How should AI respond accurately?" | 「AI 如何準確回應？」 |
+| **Configuration** (Session) | `/ai-instruction-standards` | "What to write in CLAUDE.md?" | 「CLAUDE.md 該寫什麼？」 |
+| **Architecture** (Long-term) | `/ai-friendly-architecture` | "How to structure code for AI?" | 「如何讓專案對 AI 友善？」 |
+
 ## Purpose
 
 This skill ensures AI assistants provide accurate, evidence-based responses without hallucination.

package/bundled/skills/ai-friendly-architecture/SKILL.md

@@ -18,6 +18,16 @@ description: |
 
 > **Core Standard**: This skill implements [AI-Friendly Architecture](../../core/ai-friendly-architecture.md). For comprehensive methodology documentation, refer to the core standard.
 
+## AI Skills Hierarchy | AI 技能層級
+
+This skill is part of a three-layer AI collaboration system:
+
+| Layer | Skill | Question it Answers | 回答的問題 |
+|-------|-------|-------------------|-----------|
+| **Behavior** (Immediate) | `/ai-collaboration` | "How should AI respond accurately?" | 「AI 如何準確回應？」 |
+| **Configuration** (Session) | `/ai-instruction-standards` | "What to write in CLAUDE.md?" | 「CLAUDE.md 該寫什麼？」 |
+| **Architecture** (Long-term) | `/ai-friendly-architecture` (this) | "How to structure code for AI?" | 「如何讓專案對 AI 友善？」 |
+
 ## Purpose
 
 This skill helps design project architecture that maximizes AI collaboration effectiveness through explicit patterns, layered documentation, and semantic boundaries.

package/bundled/skills/ai-instruction-standards/SKILL.md

@@ -18,6 +18,16 @@ description: |
 
 > **Core Standard**: This skill implements [AI Instruction File Standards](../../core/ai-instruction-standards.md). For comprehensive methodology documentation, refer to the core standard.
 
+## AI Skills Hierarchy | AI 技能層級
+
+This skill is part of a three-layer AI collaboration system:
+
+| Layer | Skill | Question it Answers | 回答的問題 |
+|-------|-------|-------------------|-----------|
+| **Behavior** (Immediate) | `/ai-collaboration` | "How should AI respond accurately?" | 「AI 如何準確回應？」 |
+| **Configuration** (Session) | `/ai-instruction-standards` (this) | "What to write in CLAUDE.md?" | 「CLAUDE.md 該寫什麼？」 |
+| **Architecture** (Long-term) | `/ai-friendly-architecture` | "How to structure code for AI?" | 「如何讓專案對 AI 友善？」 |
+
 ## Purpose
 
 This skill helps create and maintain AI instruction files with proper separation between universal standards and project-specific configurations.

package/bundled/skills/api-design-assistant/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: api-design
+scope: universal
+description: |
+  Guide API design following REST, GraphQL, and gRPC best practices.
+  Use when: designing APIs, reviewing endpoints, API versioning decisions.
+  Keywords: API, REST, GraphQL, gRPC, endpoint, versioning, 介面設計.
+allowed-tools: Read, Grep, Glob
+argument-hint: "[API endpoint or module | API 端點或模組]"
+---
+
+# API Design Assistant | API 設計助手
+
+Guide API design following REST, GraphQL, and gRPC best practices.
+
+引導 API 設計，遵循 REST、GraphQL 和 gRPC 最佳實踐。
+
+## Quick Reference — REST Conventions | 快速參考
+
+### HTTP Methods | HTTP 方法
+
+| Method | Purpose | Idempotent | 用途 |
+|--------|---------|------------|------|
+| GET | Read resource | Yes | 讀取資源 |
+| POST | Create resource | No | 建立資源 |
+| PUT | Replace resource | Yes | 替換資源 |
+| PATCH | Partial update | No | 部分更新 |
+| DELETE | Remove resource | Yes | 刪除資源 |
+
+### Status Codes | 狀態碼
+
+| Code | Meaning | 說明 |
+|------|---------|------|
+| 200 | OK | 成功 |
+| 201 | Created | 已建立 |
+| 204 | No Content | 無內容（刪除成功） |
+| 400 | Bad Request | 請求格式錯誤 |
+| 401 | Unauthorized | 未認證 |
+| 403 | Forbidden | 無權限 |
+| 404 | Not Found | 資源不存在 |
+| 409 | Conflict | 資源衝突 |
+| 422 | Unprocessable Entity | 驗證失敗 |
+| 429 | Too Many Requests | 請求過多（限流） |
+| 500 | Internal Server Error | 伺服器內部錯誤 |
+
+### URL Naming | URL 命名規則
+
+| Pattern | Example | 說明 |
+|---------|---------|------|
+| Collection | `/users` | 資源集合 |
+| Singleton | `/users/{id}` | 單一資源 |
+| Sub-resource | `/users/{id}/orders` | 子資源 |
+| Action | `/users/{id}/activate` | 動作（僅限 POST） |
+
+## Design Workflow | 設計工作流程
+
+```
+DEFINE ──► DESIGN ──► VALIDATE ──► DOCUMENT
+```
+
+### 1. Define — Identify Requirements | 定義需求
+Clarify consumers, use cases, data models, and non-functional requirements.
+
+釐清使用者、使用情境、資料模型和非功能性需求。
+
+### 2. Design — Structure Endpoints | 設計端點
+Apply RESTful conventions, define request/response schemas, plan versioning.
+
+套用 RESTful 慣例、定義請求/回應 Schema、規劃版本策略。
+
+### 3. Validate — Review Consistency | 驗證一致性
+Check naming consistency, error format uniformity, pagination patterns.
+
+檢查命名一致性、錯誤格式統一、分頁模式。
+
+### 4. Document — Generate Specs | 產生文件
+Produce OpenAPI/Swagger specs or GraphQL schema documentation.
+
+產出 OpenAPI/Swagger 規格或 GraphQL Schema 文件。
+
+## Versioning Strategy | 版本策略
+
+| Strategy | Example | Pros | 優點 |
+|----------|---------|------|------|
+| URL Path | `/v1/users` | Simple, explicit | 簡單、明確 |
+| Header | `Accept: application/vnd.api+json;v=1` | Clean URLs | URL 乾淨 |
+| Query | `/users?version=1` | Easy to test | 容易測試 |
+
+## Usage | 使用方式
+
+```
+/api-design              - Interactive API design guide | 互動式 API 設計引導
+/api-design /users       - Review specific endpoint design | 審查特定端點設計
+/api-design --graphql    - GraphQL schema design guide | GraphQL Schema 設計引導
+```
+
+## Next Steps Guidance | 下一步引導
+
+After `/api-design` completes, the AI assistant should suggest:
+
+> **API 設計完成。建議下一步 / API design complete. Suggested next steps:**
+> - 執行 `/sdd` 建立正式規格文件 — Create formal specification
+> - 執行 `/testing` 規劃 API 測試策略 — Plan API testing strategy
+> - 執行 `/docs` 產生 API 文件 — Generate API documentation
+> - 審查安全性 → 執行 `/security` — Review security → Run `/security`
+
+## Reference | 參考
+
+- Core standard: [api-design-standards.md](../../core/api-design-standards.md)
+
+## Version History | 版本歷史
+
+| Version | Date | Changes | 變更說明 |
+|---------|------|---------|----------|
+| 1.0.0 | 2026-03-23 | Initial release | 初始版本 |
+
+## License | 授權
+
+CC BY 4.0 — Documentation content

package/bundled/skills/atdd-assistant/SKILL.md

@@ -81,3 +81,10 @@ After `/atdd` completes, the AI assistant should suggest:
 
 - Detailed guide: [guide.md](./guide.md)
 - Core standard: [acceptance-test-driven-development.md](../../core/acceptance-test-driven-development.md)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/atdd`](../commands/atdd.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/atdd`](../commands/atdd.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/bdd-assistant/SKILL.md

@@ -77,3 +77,10 @@ After `/bdd` completes, the AI assistant should suggest:
 
 - Detailed guide: [guide.md](./guide.md)
 - Core standard: [behavior-driven-development.md](../../core/behavior-driven-development.md)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/bdd`](../commands/bdd.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/bdd`](../commands/bdd.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/brainstorm-assistant/SKILL.md

@@ -123,3 +123,10 @@ After `/brainstorm` completes, the AI assistant should suggest:
 ## Reference | 參考
 
 - Detailed guide: [guide.md](./guide.md)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/brainstorm`](../commands/brainstorm.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/brainstorm`](../commands/brainstorm.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/checkin-assistant/SKILL.md

@@ -60,3 +60,10 @@ After `/checkin` completes, the AI assistant should suggest:
 
 - Detailed guide: [guide.md](./guide.md)
 - Core standard: [checkin-standards.md](../../core/checkin-standards.md)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/checkin`](../commands/checkin.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/checkin`](../commands/checkin.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/ci-cd-assistant/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: ci-cd
+scope: universal
+description: |
+  Guide CI/CD pipeline design, configuration, and optimization.
+  Use when: setting up pipelines, optimizing build times, configuring deployment stages.
+  Keywords: CI/CD, pipeline, GitHub Actions, deployment, build, 持續整合, 持續部署.
+allowed-tools: Read, Grep, Glob
+argument-hint: "[pipeline config or stage | Pipeline 配置或階段]"
+---
+
+# CI/CD Pipeline Assistant | CI/CD 管線助手
+
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/ci-cd-assistant/SKILL.md)
+
+Guide CI/CD pipeline design following industry best practices and DORA metrics.
+
+引導 CI/CD 管線設計，遵循業界最佳實踐與 DORA 指標。
+
+## Pipeline Stage Reference | 管線階段參考
+
+```
+BUILD ──► TEST ──► ANALYZE ──► DEPLOY ──► VERIFY
+建置       測試      分析         部署       驗證
+```
+
+| Stage | Purpose | Key Activities | 關鍵活動 |
+|-------|---------|----------------|----------|
+| **Build** | Compile & package | Dependency install, compilation, artifact creation | 安裝相依、編譯、產出成品 |
+| **Test** | Quality verification | Unit, integration, E2E tests | 單元、整合、端對端測試 |
+| **Analyze** | Code quality | Lint, security scan, coverage report | 程式碼檢查、安全掃描、覆蓋率 |
+| **Deploy** | Release to environment | Staging → Production rollout | 預備環境 → 正式環境部署 |
+| **Verify** | Post-deploy validation | Smoke tests, health checks, monitoring | 冒煙測試、健康檢查、監控 |
+
+## DORA Metrics Quick Reference | DORA 指標快速參考
+
+| Metric | Elite | High | Medium | Low |
+|--------|-------|------|--------|-----|
+| **Deployment Frequency** 部署頻率 | On-demand (multiple/day) | Weekly–Monthly | Monthly–Biannual | > 6 months |
+| **Lead Time for Changes** 變更前置時間 | < 1 hour | 1 day–1 week | 1–6 months | > 6 months |
+| **MTTR** 平均恢復時間 | < 1 hour | < 1 day | 1 day–1 week | > 6 months |
+| **Change Failure Rate** 變更失敗率 | 0–15% | 16–30% | 16–30% | > 30% |
+
+## Best Practices Checklist | 最佳實踐檢查清單
+
+- [ ] **Fail fast** — Run fastest checks first (lint → unit → integration → E2E)
+- [ ] **Cache dependencies** — Cache `node_modules`, `.m2`, pip cache between runs
+- [ ] **Parallel jobs** — Split test suites across parallel runners
+- [ ] **Immutable artifacts** — Build once, deploy the same artifact to all environments
+- [ ] **Environment parity** — Keep staging identical to production
+- [ ] **Secrets management** — Never hardcode secrets; use vault/environment variables
+- [ ] **Branch protection** — Require CI pass before merge
+- [ ] **Rollback strategy** — Automate rollback on deploy failure
+
+快速失敗、快取相依、平行作業、不可變成品、環境一致、密鑰管理、分支保護、回滾策略。
+
+## Platform-Specific Tips | 平台專屬提示
+
+| Platform | Cache | Parallelism | Secrets | 備註 |
+|----------|-------|-------------|---------|------|
+| **GitHub Actions** | `actions/cache` | `matrix` strategy | `secrets.*` context | 使用 reusable workflows |
+| **GitLab CI** | `cache:` keyword | `parallel:` keyword | CI/CD Variables | 使用 `include:` 模組化 |
+| **Jenkins** | Stash/unstash | `parallel {}` block | Credentials plugin | 使用 shared libraries |
+
+## Usage | 使用方式
+
+```bash
+/ci-cd                     # Show full pipeline guidance | 顯示完整管線指引
+/ci-cd github-actions      # GitHub Actions specific tips | GitHub Actions 專屬提示
+/ci-cd --optimize          # Pipeline optimization advice | 管線優化建議
+/ci-cd build               # Build stage best practices | 建置階段最佳實踐
+```
+
+## Next Steps Guidance | 下一步引導
+
+After `/ci-cd` completes, the AI assistant should suggest:
+
+> **管線指引已提供。建議下一步 / Pipeline guidance provided. Suggested next steps:**
+> - 部署配置 → 執行 `/deploy` 設定部署策略 — Configure deployment strategy
+> - 安全掃描 → 執行 `/security` 檢查管線安全 — Check pipeline security
+> - 測試設計 → 執行 `/testing` 設計測試策略 — Design test strategy
+> - 提交規範 → 執行 `/commit` 建立規範化提交 — Create conventional commit
+
+## Reference | 參考
+
+- Core standard: [pipeline-integration-standards.md](../../core/pipeline-integration-standards.md)
+- Core standard: [deployment-standards.md](../../core/deployment-standards.md)
+
+## Version History | 版本歷史
+
+| Version | Date | Changes | 變更說明 |
+|---------|------|---------|----------|
+| 1.0.0 | 2026-03-24 | Initial release | 初始版本 |
+
+## License | 授權
+
+CC BY 4.0 — Documentation content

package/bundled/skills/code-review-assistant/SKILL.md

@@ -61,3 +61,10 @@ After `/review` completes, the AI assistant should suggest:
 
 - Detailed guide: [guide.md](./guide.md)
 - Core standard: [code-review-checklist.md](../../core/code-review-checklist.md)
+
+
+## AI Agent Behavior | AI 代理行為
+
+> 完整的 AI 行為定義請參閱對應的命令文件：[`/review`](../commands/review.md#ai-agent-behavior--ai-代理行為)
+>
+> For complete AI agent behavior definition, see the corresponding command file: [`/review`](../commands/review.md#ai-agent-behavior--ai-代理行為)

package/bundled/skills/commands/README.md

@@ -41,6 +41,26 @@ Commands for development workflow automation.
 | [`/sdd-retro`](./sdd-retro.md) | Create retroactive specs for untracked commits | 為未追蹤 commits 建立追溯 spec |
 | [`/docs`](./docs.md) | Create/update documentation | 建立/更新文件 |
 | [`/coverage`](./coverage.md) | Analyze test coverage | 分析測試覆蓋率 |
+| [`/ac-coverage`](./ac-coverage.md) | Generate AC traceability matrix and coverage report | AC 追蹤矩陣與覆蓋率報告 |
+| [`/refactor`](./refactor.md) | Guide refactoring decisions and strategy selection | 重構決策與策略選擇 |
+| [`/pr`](./pr.md) | Guide PR creation, review and merge | PR 建立、審查與合併 |
+| [`/checkin`](./checkin.md) | Pre-commit quality gates verification | 提交前品質閘門驗證 |
+| [`/incident`](./incident.md) | Guide incident response and post-mortem | 事故回應與事後檢討 |
+| [`/metrics`](./metrics.md) | Track development metrics and project health | 追蹤開發指標與專案健康 |
+| [`/migrate`](./migrate.md) | Guide code migration and framework upgrades | 程式碼遷移與框架升級 |
+| [`/audit`](./audit.md) | UDS health check and feedback system | UDS 健康檢查與回饋 |
+| [`/docgen`](./docgen.md) | Generate usage documentation from project sources | 從專案原始碼產生使用文件 |
+| [`/discover`](./discover.md) | Assess project health, architecture, and risks | 評估專案健康度、架構與風險 |
+| [`/api-design`](./api-design.md) | Guide API design (REST, GraphQL, gRPC) | API 設計引導 |
+| [`/ci-cd`](./ci-cd.md) | Guide CI/CD pipeline design and optimization | CI/CD 管線設計與優化 |
+| [`/database`](./database.md) | Guide database design and migration | 資料庫設計與遷移 |
+| [`/security`](./security.md) | Guide security review (OWASP) | 安全審查（OWASP） |
+| [`/scan`](./scan.md) | Automated security scanning | 自動化安全掃描 |
+| [`/durable`](./durable.md) | Guide workflow failure recovery | 工作流程故障恢復 |
+| [`/dev-workflow`](./dev-workflow.md) | Map development phases to UDS commands | 開發階段對應 UDS 指令 |
+| [`/guide`](./guide.md) | Access UDS guides and references | 存取 UDS 指南與參考 |
+| [`/reverse`](./reverse.md) | Reverse engineer code to Specs, BDD, or TDD | 反向工程成規格、BDD 或 TDD |
+| [`/derive`](./derive.md) | Derive BDD/TDD/ATDD from specifications | 從規格推演 BDD/TDD/ATDD |
 | [`/reverse-sdd`](./reverse-sdd.md) | Reverse engineer code to SDD spec | 反向工程成 SDD 規格 |
 | [`/reverse-bdd`](./reverse-bdd.md) | Transform SDD AC to BDD scenarios | SDD AC 轉換為 BDD 場景 |
 | [`/reverse-tdd`](./reverse-tdd.md) | Analyze BDD-TDD coverage | BDD-TDD 覆蓋率分析 |
@@ -60,6 +80,56 @@ Commands for development methodology workflows.
 | [`/bdd`](./bdd.md) | Behavior-Driven Development workflow | BDD 開發流程 |
 | [`/atdd`](./atdd.md) | Acceptance Test-Driven Development workflow | ATDD 驗收流程 |
 
+## Command → Skill / Standard Mapping | 指令→技能/標準對照表
+
+| Command | Skill | Core Standard | Category |
+|---------|-------|---------------|----------|
+| `/init` | — | — | Standards Management |
+| `/update` | — | — | Standards Management |
+| `/check` | — | — | Standards Management |
+| `/config` | — | — | Standards Management |
+| `/commit` | commit-standards | `commit-message-guide.md` | Development Workflow |
+| `/review` | code-review | `code-review-checklist.md` | Development Workflow |
+| `/checkin` | — | `checkin-standards.md` | Development Workflow |
+| `/release` | release-standards | `versioning.md` | Development Workflow |
+| `/changelog` | — | `changelog-standards.md` | Development Workflow |
+| `/requirement` | — | `requirement-engineering.md` | Development Workflow |
+| `/sdd` | spec-driven-development | `spec-driven-development.md` | Development Workflow |
+| `/sdd-retro` | — | `spec-driven-development.md` | Development Workflow |
+| `/brainstorm` | — | — | Development Workflow |
+| `/docs` | documentation | `documentation-writing-standards.md` | Development Workflow |
+| `/docgen` | — | `documentation-writing-standards.md` | Development Workflow |
+| `/coverage` | testing-guide | `testing-standards.md` | Development Workflow |
+| `/ac-coverage` | — | `acceptance-criteria-traceability.md` | Development Workflow |
+| `/refactor` | refactoring | `refactoring-standards.md` | Development Workflow |
+| `/discover` | — | — | Development Workflow |
+| `/dev-workflow` | — | — | Development Workflow |
+| `/guide` | — | — | Development Workflow |
+| `/api-design` | api-design-assistant | `api-design-standards.md` | Development Workflow |
+| `/ci-cd` | ci-cd-assistant | — | Development Workflow |
+| `/database` | database-assistant | `database-standards.md` | Development Workflow |
+| `/incident` | incident-response-assistant | — | Development Workflow |
+| `/metrics` | metrics-dashboard-assistant | — | Development Workflow |
+| `/migrate` | migration-assistant | — | Development Workflow |
+| `/pr` | pr-automation-assistant | — | Development Workflow |
+| `/security` | security-assistant | `security-standards.md` | Development Workflow |
+| `/scan` | security-scan-assistant | — | Development Workflow |
+| `/audit` | audit-assistant | — | Development Workflow |
+| `/durable` | durable-execution-assistant | — | Development Workflow |
+| `/derive` | — | `forward-derivation-standards.md` | Methodology |
+| `/derive-bdd` | — | `behavior-driven-development.md` | Methodology |
+| `/derive-tdd` | — | `test-driven-development.md` | Methodology |
+| `/derive-atdd` | — | `acceptance-test-driven-development.md` | Methodology |
+| `/derive-all` | — | — | Methodology |
+| `/reverse` | — | `reverse-engineering-standards.md` | Methodology |
+| `/reverse-sdd` | — | `reverse-engineering-standards.md` | Methodology |
+| `/reverse-bdd` | — | `reverse-engineering-standards.md` | Methodology |
+| `/reverse-tdd` | — | `reverse-engineering-standards.md` | Methodology |
+| `/methodology` | — | — | Methodology |
+| `/tdd` | — | `test-driven-development.md` | Methodology |
+| `/bdd` | — | `behavior-driven-development.md` | Methodology |
+| `/atdd` | — | `acceptance-test-driven-development.md` | Methodology |
+
 ## Commands vs Skills | 命令與技能
 
 | Aspect | Commands | Skills |