universal-dev-standards 6.6.0 → 6.7.0

package/bundled/skills/error-code-guide/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Design consistent error codes following the PREFIX_CATEGORY_NUMBER format.
   Use when: defining error codes, creating error handling, designing APIs.
+  Not for: log format and levels — use /logging-guide; handling errors that already reached production — use /incident.
   Keywords: error code, error handling, error format, API errors.
 ---
 

package/bundled/skills/git-workflow-guide/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide Git branching strategies, branch naming, and merge operations.
   Use when: creating branches, merging, pull requests, Git workflow questions.
+  Not for: composing the commit message — use /commit; the safety checks around pushing — use /push.
   Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow.
 ---
 

package/bundled/skills/incident-response-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide incident response, root cause analysis, and post-mortem documentation.
   Use when: production incident, outage response, post-mortem writing, RCA.
+  Not for: designing retries and checkpoints before failure — use /durable; setting alert thresholds and Error Budget policy — use /slo.
   Keywords: incident, outage, post-mortem, RCA, root cause.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[incident description or severity | 事故描述或嚴重程度]"

package/bundled/skills/journey-test-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: journey-test-assistant
 scope: partial
-description: "[UDS] Generate coherent user journey test plans (TESTPLAN) and E2E skeletons from project description."
+description: |
+  [UDS] Generate coherent user-journey test plans (TESTPLAN) and journey E2E skeletons from a project description.
+  Use when: a new project needs a test journey from day one, testing state carried across multiple stories, building persona-driven journey plans.
+  Not for: isolated per-AC E2E skeletons — use /e2e; measuring achieved code coverage — use /coverage.
+  Keywords: user journey, TESTPLAN, journey test, persona, cross-story state, 使用者旅程, 旅程測試, 測試計畫.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[project description | --analyze | --archetype A1|A2|A3]"
 status: stable

package/bundled/skills/knowledge-graph/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: knowledge-graph
 scope: partial
-description: "[UDS] Trace spec/decision/code impact chains via a knowledge graph (engine or Markdown fallback)"
+description: |
+  [UDS] Trace impact chains across specs, decisions, and code via a knowledge graph, with a Markdown fallback when no engine is present.
+  Use when: asking what a spec or decision affects, finding which code implements an artifact, tracing dependencies between specs, ADRs, and modules.
+  Not for: plain text search with no spec or decision anchor — use Grep; authoring the spec itself — use /sdd.
+  Keywords: knowledge graph, impact chain, traceability, spec impact, decision graph, 知識圖, 影響鏈, 規格追蹤.
 allowed-tools: Read, Glob, Grep, Bash(curl:*)
 argument-hint: "[artifact id, e.g. XSPEC-205 | 產物 id]"
 ---

package/bundled/skills/logging-guide/SKILL.md

@@ -5,6 +5,7 @@ anchor_standard: logging-standards
 description: |
   Implement structured logging with proper log levels and sensitive data handling.
   Use when: adding logging, debugging, setting up observability.
+  Not for: metrics, traces, and alerting design — use /observability; error code taxonomy — use /error-code-guide.
   Keywords: logging, log level, structured logging, observability.
 ---
 

package/bundled/skills/metrics-dashboard-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: metrics
 scope: universal
-description: "[UDS] Track development metrics, code quality indicators, and project health"
+description: |
+  [UDS] Track development metrics, code quality indicators, and technical debt over time.
+  Use when: assessing ongoing project health, classifying and trending technical debt, reporting code quality to a team.
+  Not for: first-time assessment of an unfamiliar codebase — use /discover; test coverage specifically — use /coverage or /ac-coverage.
+  Keywords: metrics, code quality, technical debt, project health, debt trend, 開發指標, 技術債, 專案健康度.
 allowed-tools: Read, Grep, Glob, Bash(npm:*, git:log)
 argument-hint: "[metric type or module | 指標類型或模組]"
 ---

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

@@ -1,7 +1,11 @@
 ---
 name: migrate
 scope: universal
-description: "[UDS] Guide code migration, framework upgrades, and technology modernization"
+description: |
+  [UDS] Guide systematic code migration, framework upgrades, and technology modernization.
+  Use when: planning a framework or major-version upgrade, assessing migration risk, capturing contract-test fixtures before an API migration.
+  Not for: in-place improvement that keeps the same framework — use /refactor; database schema design — use /database.
+  Keywords: migration, framework upgrade, modernization, breaking change, dependency upgrade, 遷移, 升級, 技術現代化.
 allowed-tools: Read, Grep, Glob, Bash(npm:*, git:*)
 argument-hint: "[migration target or framework | 遷移目標或框架]"
 ---

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

@@ -5,6 +5,7 @@ anchor_standard: observability-standards
 description: |
   Guide observability setup, metrics design, and alerting configuration.
   Use when: new service instrumentation, SLO definition, alert design, maturity assessment.
+  Not for: setting numeric targets and Error Budget policy — use /slo; log format and levels — use /logging-guide.
   Keywords: observability, metrics, traces, golden signals, alerting, SLO.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[service name or observability topic | 服務名稱或可觀測性主題]"

package/bundled/skills/orchestrate/SKILL.md

@@ -5,6 +5,7 @@ scope: universal
 description: |
   Orchestrate multi-task execution plans using Claude's native Agent tool (DAG-based, no external engine).
   Use when: executing a plan.json file with parallel/sequential task dependencies.
+  Not for: producing the plan in the first place — use /plan; single tasks with no dependencies between them.
   Keywords: orchestrate, plan, execute, DAG, task plan.
 argument-hint: "<plan.json> [--dry-run]"
 ---

package/bundled/skills/plan/SKILL.md

@@ -5,6 +5,7 @@ scope: universal
 description: |
   Generate plan.json from Spec documents, OpenSpec changes, or free-text requirements.
   Use when: converting specifications into executable task plans for /orchestrate.
+  Not for: executing the resulting plan — use /orchestrate; deciding whether the idea is worth doing — use /brainstorm.
   Keywords: plan, spec, task plan, plan.json, DAG.
 argument-hint: "[spec-file.md | openspec-dir/ | \"requirement text\" | (interactive)]"
 ---

package/bundled/skills/pr-automation-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide pull request creation, review automation, and merge strategies.
   Use when: creating PRs, automating reviews, configuring merge policies.
+  Not for: the substance of the review itself — use /code-review; branch naming and merge strategy — use /git-workflow-guide.
   Keywords: pull request, PR, merge, review, GitHub, GitLab.
 allowed-tools: Read, Grep, Glob, Bash(git:*, gh:*)
 argument-hint: "[branch name or PR number | 分支名稱或 PR 編號]"

package/bundled/skills/project-discovery/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: discover
 scope: universal
-description: "[UDS] Assess project health, architecture, and risks before adding features"
+description: |
+  [UDS] Assess project health, architecture, and risks before adding features to an existing codebase.
+  Use when: onboarding to an unfamiliar or legacy project, sizing risk before starting a feature, building a risk register.
+  Not for: ongoing metric tracking on a codebase you already know — use /metrics; recovering specs from code — use /reverse.
+  Keywords: discovery, project assessment, legacy onboarding, risk register, technical debt, 現況評估, 專案盤點, 風險登記簿.
 allowed-tools: Read, Grep, Glob, Bash(npm test:*), Bash(npm audit:*), Bash(npm outdated:*)
 argument-hint: "[feature area | 功能範圍]"
 disable-model-invocation: true

package/bundled/skills/project-structure-guide/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide for organizing project directories following language-specific best practices.
   Use when: creating projects, reorganizing structure, adding modules, setting up builds, deciding file placement.
+  Not for: structuring specifically for AI navigation — use /ai-friendly-architecture; restructuring existing code in place — use /refactor.
   Keywords: project, structure, directory, layout, gitignore, scaffold, file placement, utils, helpers, shared, where to put.
 ---
 

package/bundled/skills/push/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   AI-assisted safety layer for git push operations with quality gates and collaboration guardrails.
   Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches.
+  Not for: composing the commit — use /commit; branch and merge strategy decisions — use /git-workflow-guide.
   Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation.
 allowed-tools: Read, Bash(git:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Bash(bun:*)
 argument-hint: "[--force] [--target <branch>] [--skip-gates] [--no-pr]"

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

@@ -1,7 +1,11 @@
 ---
 name: refactor
 scope: universal
-description: "[UDS] Guide refactoring decisions and strategy selection"
+description: |
+  [UDS] Guide refactoring decisions and strategy selection, including the refactor-versus-rewrite call.
+  Use when: code has become hard to change, choosing between tactical and architectural refactoring, working safely inside legacy code.
+  Not for: moving to a different framework or major version — use /migrate; clearing debug artifacts and dead code — use /sweep.
+  Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債.
 allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*), Bash(npx:*)
 argument-hint: "[file or module | 檔案或模組]"
 ---

package/bundled/skills/release-standards/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: release
 scope: universal
-description: "[UDS] Guide release process and changelogs"
+description: |
+  [UDS] Guide the release process — semantic versioning, release modes, and the start/finish/promote/deploy sequence.
+  Use when: cutting a release, deciding a semantic version bump, promoting a release candidate to stable, recording a deployment.
+  Not for: writing the changelog entries themselves — use /changelog; the deployment mechanics — use /deploy.
+  Keywords: release, semantic versioning, version bump, release candidate, promote, 發布, 語意化版本, 發版流程.
 allowed-tools: Read, Write, Grep, Bash(git:*), Bash(npm version:*)
 argument-hint: "[version]"
 prerequisites: ["release-check"]

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

@@ -1,7 +1,11 @@
 ---
 name: requirement
 scope: universal
-description: "[UDS] Write user stories and requirements following INVEST criteria"
+description: |
+  [UDS] Write user stories and requirements that satisfy the INVEST criteria.
+  Use when: turning a feature idea into a user story, defining testable acceptance criteria, checking a backlog item for quality.
+  Not for: full specification documents with design and delta operations — use /sdd; deciding whether the idea is right at all — use /brainstorm.
+  Keywords: requirement, user story, INVEST, acceptance criteria, backlog refinement, 需求, 使用者故事, 驗收條件.
 allowed-tools: Read, Write, Grep
 argument-hint: "[feature description | 功能描述]"
 ---

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

@@ -4,6 +4,7 @@ scope: universal
 description: |
   [UDS] Guide structured team retrospectives for Sprint and Release cycles.
   Use when: sprint end, release post-mortem, iteration review, process improvement.
+  Not for: post-mortems for a production incident — use /incident; tracking metric trends between retros — use /metrics.
   Keywords: retrospective, retro, sprint review, lessons learned, action items.
 allowed-tools: Read, Write, Glob, Grep
 argument-hint: "[sprint | release | actions | --technique starfish]"

package/bundled/skills/reverse-engineer/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: reverse
 scope: partial
-description: "[UDS] System archeology - reverse engineer code across Logic, Data, and Runtime dimensions"
+description: |
+  [UDS] System archeology — reverse engineer an existing system across the Logic, Data, and Runtime dimensions.
+  Use when: documenting an undocumented system, recovering specifications from existing code, mapping an unknown data model or runtime topology.
+  Not for: assessing health and risk before a feature — use /discover; deriving tests forward from an approved spec — use /spec-derive.
+  Keywords: reverse engineering, system archeology, legacy code, spec extraction, data model, runtime, 反向工程, 系統考古, 規格提取.
 allowed-tools: Read, Grep, Glob, Bash(pg_dump:*), Bash(mysql:*), Bash(sqlite3:*), Bash(npm run:*), Bash(cat:*), Bash(docker:*)
 argument-hint: "[spec|data|runtime|bdd|tdd] <input>"
 disable-model-invocation: true

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

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide runbook creation, maintenance, and drill exercises.
   Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates.
+  Not for: responding to an incident already in progress — use /incident; the deployment procedure itself — use /deploy.
   Keywords: runbook, operations, drill, on-call, procedure.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[create|drill|coverage] [alert name or type | 告警名稱或類型]"

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

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide security review and vulnerability assessment following OWASP standards.
   Use when: security audit, vulnerability check, secure coding review, threat modeling.
+  Not for: automated dependency, CVE, and secret scanning — use /scan; handling a breach in progress — use /incident.
   Keywords: security, OWASP, vulnerability, authentication, authorization.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[module or file to audit | 要審計的模組或檔案]"

package/bundled/skills/security-scan-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide automated security scanning, dependency auditing, and secret detection.
   Use when: dependency audit, CVE scanning, secret detection, license compliance.
+  Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep.
   Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.
 allowed-tools: Read, Grep, Glob, Bash(npm:audit, npx:*)
 argument-hint: "[scan type or target | 掃描類型或目標]"

package/bundled/skills/skill-builder/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: skill-builder
 scope: universal
-description: "[UDS] Identify repeated processes and build Skills with the right development depth"
+description: |
+  [UDS] Turn a repeated manual process into a properly scoped Skill, with the right amount of process along the way.
+  Use when: the same multi-step sequence has been done manually three or more times, formalising an ad-hoc Skill, deciding where a Skill belongs.
+  Not for: recording historical facts or project state — that belongs in memory, not a Skill; one-off tasks that will not recur.
+  Keywords: skill, skill builder, process knowledge, repeated process, automation, 技能建立, 流程知識, 自動化.
 allowed-tools: Read, Glob, Grep, Write, Edit, Bash
 argument-hint: "[process description | 流程描述]"
 ---

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

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide SLI selection, SLO setting, and Error Budget management.
   Use when: defining service quality targets, setting up SLO-based alerting, Error Budget policy.
+  Not for: instrumentation and metric collection — use /observability; responding to an active breach of the target — use /incident.
   Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[create|review|budget] [service name | 服務名稱]"

package/bundled/skills/spec-derivation/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: spec-derive
 scope: partial
-description: "[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications"
+description: |
+  [UDS] Derive BDD scenarios, TDD skeletons, integration and E2E tests, and ATDD tables from an approved specification.
+  Use when: a spec has been approved and needs test artifacts, generating tagged test skeletons from acceptance criteria, producing contract stubs from a spec.
+  Not for: recovering a spec from existing code — use /reverse; writing or reviewing the spec itself — use /sdd.
+  Keywords: forward derivation, spec to test, BDD scenario, TDD skeleton, ATDD table, 正向推演, 規格衍生, 測試生成.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[all|bdd|tdd|it|e2e|atdd] <spec-file>"
 prerequisites: ["spec-approved"]

package/bundled/skills/spec-driven-dev/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: sdd
 scope: universal
-description: "[UDS] Create or review specification documents for Spec-Driven Development"
+description: |
+  [UDS] Create and review specification documents before writing code — spec format, states, and delta operations.
+  Use when: a change needs a written spec first, reviewing a spec for completeness, amending an existing spec with delta sections.
+  Not for: executing a gated SDD lifecycle — that moved to the adoption layer (XSPEC-095); lightweight micro-specs for rapid iteration — use the uds spec command.
+  Keywords: SDD, spec, specification, design document, delta operation, spec review, 規格驅動開發, 規格文件, 變更操作.
 allowed-tools: Read, Write, Grep, Glob, Bash(git:*)
 argument-hint: "[spec name or feature | 規格名稱或功能]"
 ---

package/bundled/skills/sweep/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Scan codebase for debug artifacts and code quality issues; optionally auto-fix safe patterns.
   Use when: before committing, during PR review, or periodic codebase cleanup.
+  Not for: structural code improvement — use /refactor; security-specific scanning — use /scan.
   Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality.
 allowed-tools: Read, Grep, Glob, Bash(find:*), Edit, Write
 argument-hint: "[--fix] [--report] [--path <dir>] [--exclude <pattern>]"

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

@@ -1,7 +1,11 @@
 ---
 name: tdd
 scope: partial
-description: "[UDS] Guide through Test-Driven Development workflow"
+description: |
+  [UDS] Reference for Test-Driven Development: the Red-Green-Refactor cycle, FIRST principles, and Arrange-Act-Assert structure.
+  Use when: writing a failing test before implementation, structuring a test with Arrange-Act-Assert, checking tests against FIRST.
+  Not for: driving the RED/GREEN cycle interactively — that moved to the adoption layer (XSPEC-095); measuring how much code the tests cover — use /coverage.
+  Keywords: TDD, test first, Red Green Refactor, FIRST, Arrange Act Assert, unit test, 測試驅動開發, 紅綠重構, 單元測試.
 allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*), Bash(npx vitest:*)
 argument-hint: "[feature or file | 功能或檔案]"
 status: reference

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

@@ -1,7 +1,11 @@
 ---
 name: coverage
 scope: partial
-description: "[UDS] Analyze test coverage and provide recommendations"
+description: |
+  [UDS] Analyze code-level test coverage across the eight-dimension framework and recommend which gaps to close.
+  Use when: coverage percentages look healthy but defects still ship, judging test completeness beyond line percentage, setting coverage targets.
+  Not for: requirement-level AC-to-test traceability — use /ac-coverage; writing the missing tests — use /tdd or /spec-derive.
+  Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 測試覆蓋率, 八維度, 測試完整性.
 allowed-tools: Read, Grep, Glob, Bash(npm test:*)
 argument-hint: "[file or module | 檔案或模組]"
 ---

package/bundled/skills/testing-guide/SKILL.md

@@ -5,6 +5,7 @@ description: |
   Testing pyramid and test writing standards for UT/IT/ST/E2E.
   Supports ISTQB and Industry Pyramid frameworks.
   Use when: writing tests, discussing test coverage, test strategy, or test naming.
+  Not for: driving a Red-Green-Refactor cycle — use /tdd; measuring achieved coverage — use /coverage.
   Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT.
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "universal-dev-standards",
-  "version": "6.6.0",
+  "version": "6.7.0",
   "description": "CLI tool for adopting Universal Development Standards",
   "keywords": [
     "documentation",

package/standards-registry.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "version": "6.6.0",
+  "version": "6.7.0",
   "lastUpdated": "2026-05-13",
   "description": "Standards registry for universal-dev-standards with integrated skills and AI-optimized formats",
   "formats": {
@@ -58,14 +58,14 @@
     "standards": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
-      "version": "6.6.0"
+      "version": "6.7.0"
     },
     "skills": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
       "localPath": "skills",
       "rawUrl": "https://raw.githubusercontent.com/AsiaOstrich/universal-dev-standards/main/skills",
-      "version": "6.6.0",
+      "version": "6.7.0",
       "note": "Skills are now included in the main repository under skills/"
     }
   },
@@ -2260,7 +2260,7 @@
       "id": "license-compliance",
       "name": "License Compliance Standards",
       "nameZh": "授權合規標準",
-      "version": "6.6.0",
+      "version": "6.7.0",
       "source": {
         "human": "core/license-compliance.md",
         "ai": "ai/standards/license-compliance.ai.yaml"
@@ -2272,7 +2272,7 @@
       "id": "verification-oracle",
       "name": "Verification Oracle Standards",
       "nameZh": "驗證 Oracle 標準",
-      "version": "6.6.0",
+      "version": "6.7.0",
       "source": {
         "human": "core/verification-oracle.md",
         "ai": "ai/standards/verification-oracle.ai.yaml"
@@ -2284,7 +2284,7 @@
       "id": "model-provenance",
       "name": "Model Provenance Policy Standards",
       "nameZh": "模型來源政策標準",
-      "version": "6.6.0",
+      "version": "6.7.0",
       "source": {
         "human": "core/model-provenance.md",
         "ai": "ai/standards/model-provenance.ai.yaml"
@@ -2296,7 +2296,7 @@
       "id": "resource-cost-boundary",
       "name": "Resource / Cost Boundary Declaration Standards",
       "nameZh": "資源／成本邊界宣告標準",
-      "version": "6.6.0",
+      "version": "6.7.0",
       "source": {
         "human": "core/resource-cost-boundary.md",
         "ai": "ai/standards/resource-cost-boundary.ai.yaml"