universal-dev-standards 5.8.0 → 5.11.0

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

@@ -1,15 +1,7 @@
----
-source: ../../../docs/FEATURE-REFERENCE.md
-source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-04-22
-status: current
----
-
 # UDS 功能参考手册
 
 > Universal Development Standards - 完整功能文档
-> Auto-generated | Last updated: 2026-03-24
+> Auto-generated | Last updated: 2026-05-14
 
 **Language**: [English](../../../docs/FEATURE-REFERENCE.md) | [繁體中文](../../zh-TW/docs/FEATURE-REFERENCE.md) | 简体中文
 
@@ -18,14 +10,14 @@ status: current
 ## 目录
 
 1. [CLI 指令](#cli-commands) (9)
-2. [斜线命令](#slash-commands) (45)
-3. [技能](#skills) (40)
+2. [斜线命令](#slash-commands) (49)
+3. [技能](#skills) (54)
 4. [代理](#agents) (5)
 5. [工作流程](#workflows) (5)
-6. [核心规范](#core-standards) (48)
-7. [脚本](#scripts) (41)
+6. [核心规范](#core-standards) (125)
+7. [脚本](#scripts) (55)
 
-**Total Features: 182**
+**Total Features: 302**
 
 ---
 
@@ -60,8 +52,11 @@ status: current
 | `--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 |
+| `--with-hooks` | Install enforcement hooks (commit-msg, security, logging) |
+| `--content-layout` | Content layout (flat, layered) [default: flat] |
 | `-y, --yes` | Use defaults, skip interactive prompts |
 | `-E, --experimental` | Enable experimental features (methodology) |
+| `--force` | Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071) |
 
 ### `uds configure`
 
@@ -93,6 +88,7 @@ status: current
 | `--ci` | CI mode: disable interactive prompts and set exit code on issues |
 | `--migrate` | Migrate legacy manifest to hash-based tracking |
 | `--offline` | Skip npm registry check for CLI updates |
+| `--force` | Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071) |
 
 ### `uds update`
 
@@ -159,15 +155,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 |
@@ -177,9 +177,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 |
@@ -188,8 +195,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 |
 
@@ -199,10 +210,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 Records (ADR). |
 | `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. |
+| `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/, 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 健康檢查與回饋系統" |
@@ -213,29 +225,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 Commits standard" |
+| `contract-test-assistant` | [UDS] Guide contract testing strategy for APIs and microservices. |
 | `database-assistant` | Guide database design, migration, and query optimization. |
+| `deploy-assistant` | Guide reliable deployments without CI/CD platforms (GitHub Actions / GitLab CI). |
+| `dev-methodology` | "[UDS] Manage development methodology workflow" |
 | `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" |
+| `e2e-assistant` | "[UDS] Generate E2E test skeletons from BDD scenarios" |
 | `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. |
+| `journey-test-assistant` | "[UDS] 從專案描述生成連貫使用者旅程測試計畫（TESTPLAN）與 E2E 骨架" |
 | `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" |
+| `observability-assistant` | Guide observability setup, metrics design, and alerting configuration. |
+| `orchestrate` | Orchestrate multi-task execution plans using Claude's native Agent tool (DAG-based, no external engine). |
+| `plan` | Generate plan.json from Spec documents, OpenSpec changes, or free-text requirements. |
 | `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. |
+| `push` | AI-assisted safety layer for git push operations with quality gates and collaboration guardrails. |
 | `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" |
+| `retrospective-assistant` | [UDS] Guide structured team retrospectives for Sprint and Release cycles. |
 | `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logic, Data, and Runtime dimensions" |
+| `runbook-assistant` | Guide runbook creation, maintenance, and drill exercises. |
 | `security-assistant` | Guide security review and vulnerability assessment following OWASP standards. |
 | `security-scan-assistant` | Guide automated security scanning, dependency auditing, and secret detection. |
+| `skill-builder` | "[UDS] Identify repeated processes and build Skills with the right development depth" |
+| `slo-assistant` | Guide SLI selection, SLO setting, and Error Budget management. |
+| `spec-derivation` | "[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications" |
 | `spec-driven-dev` | "[UDS] Create or review specification documents for Spec-Driven Development" |
+| `sweep` | Scan codebase for debug artifacts and code quality issues; optionally auto-fix safe patterns. |
 | `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. |
@@ -273,46 +298,123 @@ status: current
 | `acceptance-criteria-traceability` | - |  |
 | `acceptance-test-driven-development` | 1.1.0 |  |
 | `accessibility-standards` | 1.0.0 | This standard defines comprehensive guidelines for creating accessible software  |
+| `adr-standards` | 1.0.0 | Architecture Decision Records capture the context, options, and rationale behind |
+| `adversarial-test` | - |  |
+| `agent-behavior-discipline` | 1.0.0 | This standard defines four behavioral disciplines for AI agents that elevate per |
+| `agent-communication-protocol` | 1.0.0 | Define a unified communication protocol for AI agents across the AsiaOstrich pro |
 | `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-command-behavior` | 1.0.0 | This standard defines a structure for specifying AI Agent runtime behavior in co |
 | `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 |
+| `ai-response-navigation` | 1.0.0 | This standard defines navigation behavior for AI responses: every substantive AI |
+| `alerting-standards` | 1.0.0 |  |
+| `anti-hallucination` | 1.5.1 | This standard defines strict guidelines for AI assistants to prevent hallucinati |
+| `anti-sycophancy-prompting` | 1.0.0 | This standard defines techniques and rules for designing prompts that elicit gen |
 | `api-design-standards` | 1.0.0 | This standard defines comprehensive guidelines for designing, building, and main |
 | `behavior-driven-development` | 1.1.0 |  |
+| `behavior-snapshot` | - |  |
 | `branch-completion` | 1.0.0 | Define a standardized workflow for completing development branches, including pr |
+| `browser-compatibility-standards` | 1.0.0 | This standard defines supported browser and device matrices, testing automation  |
+| `capability-declaration` | - |  |
+| `cd-deployment-strategies` | - |  |
 | `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.5.0 | This standard defines quality gates that MUST be passed before committing code t |
+| `chaos-engineering-standards` | 1.0.0 |  |
+| `chaos-injection-tests` | - |  |
+| `checkin-standards` | 1.6.0 | This standard defines quality gates that MUST be passed before committing code t |
+| `circuit-breaker` | - |  |
 | `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 |
+| `container-security` | - |  |
+| `containerization-standards` | 1.0.0 |  |
 | `context-aware-loading` | 1.0.0 | This standard defines a protocol for AI tools to selectively load development st |
+| `contract-testing-standards` | 1.0.0 | Contract testing verifies that a provider (API server) and its consumers (client |
+| `cost-budget-test` | - |  |
+| `cross-flow-regression` | 1.0.0 | This standard defines cross-flow regression testing — verifying that changes to  |
+| `data-migration-testing` | - |  |
 | `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 |
+| `deprecation-standards` | 1.0.0 |  |
+| `design-document-standards` | 1.0.0 |  |
 | `developer-memory` | 1.0.0 | This standard defines a structured system for capturing, retrieving, and surfaci |
+| `disaster-recovery-drill` | - |  |
+| `documentation-lifecycle` | 1.0.0 | This standard defines **when** to update documentation, **when** to check it, an |
 | `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 |
+| `dual-phase-output` | - |  |
+| `environment-standards` | 1.0.0 |  |
 | `error-code-standards` | 1.2.0 |  |
+| `estimation-standards` | 1.0.0 |  |
+| `execution-history` | 1.0.0 |  |
+| `failure-source-taxonomy` | - |  |
+| `feature-flag-standards` | 1.0.0 |  |
+| `feature-manifest-standard` | - |  |
+| `flaky-test-management` | - |  |
+| `flow-based-testing` | 1.3.0 | This document defines a systematic methodology for testing multi-step processes. |
 | `forward-derivation-standards` | 1.2.0 | This standard defines the principles and workflows for Forward Derivation—automa |
+| `frontend-design-standards` | 1.0.0 | This standard defines a machine-readable frontend design specification format (D |
+| `full-coverage-testing` | - |  |
 | `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 |
+| `governance-layer` | 1.0.0 | A governance layer provides a shared anchor for all agents and roles in a projec |
+| `health-check-standards` | - |  |
+| `immutability-first` | - |  |
+| `knowledge-transfer-standards` | 1.0.0 |  |
+| `llm-output-validation` | - |  |
 | `logging-standards` | 1.2.0 |  |
+| `mock-boundary` | 1.0.0 | This document defines rules for what can and cannot be mocked in tests. Its goal |
 | `model-selection` | 1.0.0 | Define a cost-effective strategy for selecting AI model tiers based on task comp |
+| `mutation-testing` | 1.0.0 | Mutation testing evaluates test suite effectiveness by injecting artificial bugs |
+| `no-cicd-deployment` | - |  |
+| `observability-standards` | 1.0.0 |  |
+| `packaging-standards` | 1.0.0 | This standard defines a Recipe-based packaging framework that enables user proje |
 | `performance-standards` | 1.1.0 | This standard defines comprehensive guidelines for software performance engineer |
 | `pipeline-integration-standards` | - |  |
+| `pipeline-security-gates` | - |  |
+| `policy-as-code-testing` | - |  |
+| `postmortem-standards` | 1.0.0 |  |
+| `privacy-standards` | 1.0.0 |  |
 | `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 |
+| `prompt-regression` | - |  |
+| `property-based-testing` | - |  |
+| `recovery-recipe-registry` | - |  |
 | `refactoring-standards` | 2.1.0 | This standard defines comprehensive guidelines for code refactoring, covering ev |
+| `release-quality-manifest` | - |  |
+| `release-readiness-gate` | 1.0.0 | This standard defines a **single, aggregated Release Readiness Gate** that unifi |
+| `replay-test` | - |  |
 | `requirement-engineering` | 1.0.0 |  |
+| `retrospective-standards` | 1.0.0 | Retrospectives are structured team reflections that identify what worked well, w |
+| `retry-standards` | - |  |
 | `reverse-engineering-standards` | 1.0.0 | This standard defines the principles, workflows, and best practices for reverse  |
+| `rollback-standards` | - |  |
+| `runbook-standards` | 1.0.0 |  |
+| `sast-advanced` | 1.0.0 | This standard defines Advanced Static Application Security Testing (SAST) practi |
+| `secure-op` | - |  |
+| `security-decision` | - |  |
 | `security-standards` | 1.1.0 | This standard defines comprehensive security guidelines for software development |
-| `spec-driven-development` | 2.1.0 |  |
+| `security-testing` | 1.0.0 | This document defines the security testing methodology for software projects. It |
+| `server-ops-security` | - |  |
+| `skill-standard-alignment-check` | - |  |
+| `slo-standards` | 1.0.0 |  |
+| `smoke-test` | - |  |
+| `spec-driven-development` | 2.2.0 |  |
+| `standard-admission-criteria` | - |  |
+| `standard-lifecycle-management` | - |  |
 | `structured-task-definition` | 1.0.0 |  |
+| `supply-chain-attestation` | - |  |
+| `supply-chain-security-standards` | 1.0.0 |  |
 | `systematic-debugging` | 1.0.0 | Define a structured, four-phase debugging workflow that prevents the common anti |
+| `tech-debt-standards` | 1.0.0 |  |
 | `test-completeness-dimensions` | 1.1.0 | This document defines a systematic framework for evaluating test completeness. I |
+| `test-data-standards` | 1.0.0 |  |
 | `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 |
+| `test-governance` | 1.1.0 |  |
+| `testing-standards` | 3.2.0 | This standard defines actionable testing rules and conventions for AI agents and |
+| `timeout-standards` | - |  |
+| `token-budget` | - |  |
+| `translation-lifecycle-standards` | 1.0.0 | Translation lifecycle standards: MISSING vs OUTDATED distinction, semver-aware s |
 | `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 |
@@ -326,19 +428,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, AC-11) |
+| `bump-version.mjs` | Build a platform-aware shell command for a .sh script. |
+| `bump-version.sh` | DEPRECATED: Use 'node scripts/bump-version.mjs <version>' instead (cross-platform). |
 | `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-sync.ts' instead (cross-platform). |
 | `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 ONLY (non-blocking) |
+| `check-commit-spec-reference.sh` | DEPRECATED: Use 'npx tsx scripts/check-commit-spec-reference.ts' instead (cross-platform). |
 | `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-5, AC-7) |
+| `check-flow-gate-report.sh` | DEPRECATED: Use 'npx tsx scripts/check-flow-gate-report.ts' instead (cross-platform). |
+| `check-integration-commands-sync.sh` | DEPRECATED: Use 'npx tsx scripts/check-integration-commands-sync.ts' instead (cross-platform). |
 | `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-completeness.ts' instead (cross-platform). |
+| `check-release-readiness-signoff.sh` | DEPRECATED: Use 'npx tsx scripts/check-release-readiness-signoff.ts' instead (cross-platform). |
 | `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 |
@@ -355,11 +467,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-blocking) |
+| `check-workflow-compliance.sh` | DEPRECATED: Use 'npx tsx scripts/check-workflow-compliance.ts' instead (cross-platform). |
 | `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, AC-14) |
+| `install-hooks.mjs` | Install Hooks |
+| `install-hooks.sh` | DEPRECATED: Use 'node scripts/install-hooks.mjs' instead (cross-platform). |
+| `pre-commit.mjs` | Build a platform-aware shell command for a .sh script. |
 | `pre-release-check.ps1` | Pre Release Check |
 | `pre-release-check.sh` | Pre-release Check Script |
 | `pre-release.ps1` | Pre-Release Preparation Script for Universal Development Standards |

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

@@ -38,3 +38,46 @@ CAPTURE ──► ANALYZE ──► DECIDE ──► RECORD ──► LINK
 
 - 核心规范：[adr-standards.md](../../../../core/adr-standards.md)
 - 详细指南：[guide.md](./guide.md)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/adr` completes, the AI assistant should suggest:
+
+> **ADR created. Suggested next steps:**
+> - Execute `/sdd` to create a spec if the decision requires implementation
+> - Execute `/commit` to commit the ADR file
+> - Update related SPECs to reference this ADR
+> - Share with team for review if status is `Proposed`
+
+> **ADR 已建立。建議下一步：**
+> - 執行 `/sdd` 建立規格（若決策需要實作）
+> - 執行 `/commit` 提交 ADR 檔案
+> - 更新相關規格以引用此 ADR
+> - 若狀態為 `Proposed`，分享給團隊審查
+
+## AI Agent Behavior | AI 代理行為
+
+When the user invokes `/adr`, the AI assistant MUST:
+
+1. **Check existing ADRs** — Search `docs/adr/` to determine next ADR number
+2. **Guide interactively** — Ask about context, drivers, and options step by step
+3. **Generate the file** — Write ADR to `docs/adr/ADR-NNN-title.md`
+4. **Suggest links** — Identify related SPECs or ADRs to cross-reference
+5. **Offer next steps** — Show the Next Steps Guidance above
+
+When the user invokes `/adr list`:
+1. Scan `docs/adr/` directory
+2. Parse status from each ADR file
+3. Display as a table: Number, Title, Status, Date
+
+When the user invokes `/adr supersede [ADR-NNN]`:
+1. Read the existing ADR
+2. Guide creation of a new ADR
+3. Update old ADR status to `Superseded by ADR-NNN`
+4. Add `Supersedes ADR-NNN` to new ADR
+
+## Reference | 參考
+
+- Core Standard: [adr-standards.md](../../core/adr-standards.md)
+- Detailed Guide: [guide.md](./guide.md)

package/bundled/locales/zh-CN/skills/ai-collaboration-standards/SKILL.md

@@ -173,3 +173,38 @@ This project uses **English** certainty tags.
 此技能依据 [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 `/ai-collaboration` completes, the AI assistant should suggest:
+
+> **AI 協作行為規範已掌握。建議下一步 / AI collaboration behavior standards understood. Suggested next steps:**
+> - 執行 `/ai-instructions` 建立或更新 CLAUDE.md 等 AI 指令檔案 ⭐ **Recommended / 推薦** — 將協作標準寫入專案配置 / Write collaboration standards into project configuration
+> - 執行 `/ai-friendly-architecture` 設計 AI 友善架構 — 從長期架構層面優化 AI 協作 / Optimize AI collaboration at the architecture level
+> - 執行 `/review` 運用確定性標籤進行程式碼審查 — 實踐基於證據的分析 / Practice evidence-based analysis
+
+---
+
+## Related Standards
+
+- [Anti-Hallucination Standards](../../core/anti-hallucination.md)
+- [Code Review Checklist](../../core/code-review-checklist.md)
+- [Testing Standards](../../core/testing-standards.md)
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.1.0 | 2026-01-25 | Added: Unified Tag System with Certainty and Derivation tag categories |
+| 1.0.0 | 2025-12-24 | Added: 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-CN/skills/ai-friendly-architecture/SKILL.md

@@ -219,3 +219,38 @@ documentation:
 本技能以 [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 `/ai-friendly-architecture` completes, the AI assistant should suggest:
+
+> **AI 友善架構指南已掌握。建議下一步 / AI-friendly architecture guide understood. Suggested next steps:**
+> - 執行 `/sdd` 將 AI 友善架構設計納入正式規格 ⭐ **Recommended / 推薦** — 確保架構決策有規格追蹤 / Ensure architecture decisions are tracked in specs
+> - 建立 `.ai-context.yaml` 和 `QUICK-REF.md` — 立即實作 AI 友善結構 / Implement AI-friendly structure immediately
+> - 執行 `/ai-instructions` 更新 CLAUDE.md 以反映架構配置 — 讓 AI 指令檔案與架構保持同步 / Keep AI instruction files in sync with architecture
+
+---
+
+## Related Standards
+
+- [AI-Friendly Architecture](../../core/ai-friendly-architecture.md) - Core architecture standard
+- [Project Structure](../../core/project-structure.md) - Directory organization
+- [Documentation Structure](../../core/documentation-structure.md) - Documentation layering
+- [Anti-Hallucination](../../core/anti-hallucination.md) - AI accuracy standards
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.0.0 | 2026-01-25 | 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/ai-instruction-standards/SKILL.md

@@ -212,3 +212,38 @@ project/
 本技能以 [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 `/ai-instructions` completes, suggest:
+
+> - Create or update project's `CLAUDE.md` / `AGENTS.md` ⭐ **Recommended** — Apply standards immediately
+> - Run `/ai-friendly-architecture` to optimize AI collaboration at the architecture level
+> - Run `/ai-collaboration` to review AI behavior guidelines
+
+---
+
+## Related Standards
+
+- [AI Instruction File Standards](../../core/ai-instruction-standards.md) - Core standard
+- [Documentation Writing Standards](../../core/documentation-writing-standards.md) - Writing guidelines
+- [Anti-Hallucination Guidelines](../../core/anti-hallucination.md) - AI accuracy rules
+- [AI-Friendly Architecture](../../core/ai-friendly-architecture.md) - Context optimization
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 2.0.0 | 2026-04-28 | Add Gemini CLI, OpenAI Codex CLI; update Cursor (MDC format, deprecated .cursorrules); update OpenCode (AGENTS.md primary); update Copilot (multiple file types); update Windsurf (Workflows); add AGENTS.md cross-tool standard section |
+| 1.0.0 | 2026-01-25 | 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/contract-test-assistant/SKILL.md

@@ -29,3 +29,27 @@ description: |
 
 - 详细指南：[contract-testing.md](../../../../options/testing/contract-testing.md)
 - 技能指南：[guide.md](./guide.md)
+
+
+## Next Steps Guidance | 下一步引導
+
+After `/contract-test` completes:
+
+> **合約測試引導完成。建議下一步：**
+> - 執行 `/ci-cd` 將合約驗證加入 CI 管線
+> - 執行 `/api-design` 完善 API 設計
+> - 執行 `/testing` 整合到整體測試策略
+
+## Reference | 參考
+
+- Detailed guide: [contract-testing.md](../../options/testing/contract-testing.md)
+- Related: [api-design-assistant](../api-design-assistant/SKILL.md)
+
+## AI Agent Behavior | AI 代理行為
+
+When `/contract-test` is invoked:
+1. **Assess** — Ask about architecture (monolith, microservices, number of APIs)
+2. **Recommend** — Suggest strategy based on architecture
+3. **Guide** — Walk through setup for chosen strategy
+4. **Generate** — Create example contract test files
+5. **Verify** — If `verify` subcommand, scan for contracts and report coverage

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

@@ -418,3 +418,40 @@ MIT
 本 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 `/docs-guide` completes, the AI assistant should suggest:
+
+> **文件結構與需求已釐清。建議下一步 / Documentation structure and requirements clarified. Suggested next steps:**
+> - 執行 `/docs` 根據指南直接產生專案文件 ⭐ **Recommended / 推薦** — 立即將文件指南化為行動 / Turn documentation guidelines into action immediately
+> - 執行 `/changelog` 建立或更新 CHANGELOG.md — 確保變更歷史完整 / Ensure change history is complete
+> - 執行 `/sdd` 將文件需求納入規格驅動開發 — 確保文件與功能同步 / Ensure docs stay in sync with features
+
+---
+
+## Related Standards
+
+- [Documentation Writing Standards](../../core/documentation-writing-standards.md) - Content requirements
+- [Documentation Structure](../../core/documentation-structure.md) - File organization
+- [Changelog Standards](../../core/changelog-standards.md) - CHANGELOG format
+- [Changelog Guide Skill](../changelog-guide/SKILL.md) - CHANGELOG skill
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 2.1.0 | 2026-03-17 | Added: Diátaxis classification, LLM discovery, quality metrics, enhanced ADR template, translation-friendly writing |
+| 2.0.0 | 2026-01-12 | Added: Project type matrix, document templates, documentation pyramid |
+| 1.0.0 | 2025-12-24 | 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/error-code-guide/SKILL.md

@@ -267,3 +267,36 @@ export const ErrorCodes = {
 此技能採用 [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 `/errors` completes, the AI assistant should suggest:
+
+> **錯誤碼設計已完成。建議下一步 / Error code design completed. Suggested next steps:**
+> - 執行 `/sdd` 將錯誤碼設計納入正式規格 ⭐ **Recommended / 推薦** — 確保錯誤碼在規格中有完整定義 / Ensure error codes are fully defined in specs
+> - 執行 `/logging` 設定結構化日誌以配合錯誤碼 — 讓錯誤碼與日誌系統整合 / Integrate error codes with logging system
+> - 執行 `/tdd` 為錯誤處理邏輯撰寫測試 — 確保每個錯誤碼都有對應的測試 / Ensure each error code has corresponding tests
+
+---
+
+## Related Standards
+
+- [Error Code Standards](../../core/error-code-standards.md)
+- [Logging Standards](../../core/logging-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/git-workflow-guide/SKILL.md

@@ -216,3 +216,37 @@ git push origin feature/my-feature
 本技能採用 [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 `/git-flow` completes, the AI assistant should suggest:
+
+> **Git 工作流程已設定。建議下一步 / Git workflow configured. Suggested next steps:**
+> - 執行 `git checkout -b feature/<描述>` 建立功能分支開始開發 ⭐ **Recommended / 推薦** — 立即套用所選的分支策略 / Apply the chosen branching strategy immediately
+> - 執行 `/commit` 學習提交訊息規範 — 確保提交訊息格式一致 / Ensure consistent commit message format
+> - 執行 `/checkin` 了解簽入品質門檻 — 在提交前確保程式碼品質 / Ensure code quality before commits
+
+---
+
+## Related Standards
+
+- [Git Workflow](../../core/git-workflow.md) - Core Git workflow standard
+- [Commit Message Guide](../../core/commit-message-guide.md) - Commit message conventions
+- [Checkin Standards](../../core/checkin-standards.md) - Pre-commit quality gates
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.0.0 | 2025-12-24 | Added: 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)