universal-dev-standards 5.6.0 → 5.7.0

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

@@ -6,12 +6,10 @@ allowed-tools: Read, Grep, Glob, Bash(git diff:*), Bash(git status:*), Bash(npm
 disable-model-invocation: true
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
-  Checkin workflow orchestration (gate execution sequence, abort logic) extracted to:
-  - DevAP flow: dev-autopilot/.devap/flows/checkin.flow.yaml
-  - DevAP CLI:  devap checkin (packages/cli/src/commands/checkin.ts)
-  - Flow spec:  dev-autopilot/standards/flow/checkin-gate-sequence.ai.yaml
-  This Skill retains: quality gate definitions, checklist items, never-commit rules.
-  Use `devap checkin` for enforced execution; this Skill for activity reference.
+  Checkin workflow orchestration (gate execution sequence, abort logic) relocated to adoption layer
+  (XSPEC-095, 2026-04-28). This Skill retains: quality gate definitions, checklist items,
+  never-commit rules.
+  For enforced execution, use your adoption layer's toolchain.
 -->
 
 # Check-in Assistant | 簽入助手

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

@@ -7,11 +7,10 @@ argument-hint: "[file path or branch | 檔案路徑或分支名稱]"
 disable-model-invocation: true
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
-  Code review workflow orchestration (4-step sequence, outcome gating) extracted to:
-  - DevAP flow: dev-autopilot/.devap/flows/review.flow.yaml
-  - DevAP CLI:  devap review (packages/cli/src/commands/review.ts)
-  This Skill retains: 8 review category definitions, BLOCKING/IMPORTANT/SUGGESTION/QUESTION/NOTE prefix semantics.
-  Use `devap review` for enforced execution; this Skill for category and prefix reference.
+  Code review workflow orchestration (4-step sequence, outcome gating) relocated to adoption layer
+  (XSPEC-095, 2026-04-28). This Skill retains: 8 review category definitions,
+  BLOCKING/IMPORTANT/SUGGESTION/QUESTION/NOTE prefix semantics.
+  For enforced execution, use your adoption layer's toolchain.
 -->
 
 # Code Review Assistant | 程式碼審查助手

package/bundled/skills/commands/observability.md

@@ -9,3 +9,45 @@ argument-hint: "[--checklist | --maturity | --alerting | service name | 服務
 See [SKILL.md](../observability-assistant/SKILL.md) for full documentation.
 
 詳見 [SKILL.md](../observability-assistant/SKILL.md)。
+
+## AI Agent Behavior | AI 代理行為
+
+> Follows [AI Command Behavior Standards](../../core/ai-command-behavior.md)
+
+### Entry Router | 進入路由
+
+| Input | AI Action |
+|-------|-----------|
+| `/observability` | 詢問目標服務，進行整體可觀測性評估 |
+| `/observability --checklist` | 直接執行可觀測性檢查清單 |
+| `/observability --maturity` | 執行成熟度評估並給出改善建議 |
+| `/observability --alerting` | 進入告警規則設計與審查流程 |
+| `/observability <service>` | 針對指定服務進行可觀測性分析 |
+
+### Interaction Script | 互動腳本
+
+1. 確認目標服務與現有可觀測性工具（Prometheus、Grafana、Datadog 等）
+2. 依選定模式執行評估或設計流程
+3. 展示現況分析與缺口報告
+
+**Decision: 可觀測性缺口**
+- IF 缺少 Metrics → 建議關鍵指標清單（RED/USE method）
+- IF 缺少 Tracing → 建議分散式追蹤導入步驟
+- IF 缺少 Logging → 建議結構化日誌規範
+- IF 告警規則不完整 → 建議補齊 SLO-based alerting
+
+🛑 **STOP**: 缺口分析完成後等待使用者確認優先補齊項目
+
+### Stop Points | 停止點
+
+| Stop Point | 等待內容 |
+|-----------|---------|
+| 現況評估報告後 | 使用者確認分析正確性 |
+| 改善建議展示後 | 使用者決定優先實施項目 |
+
+### Error Handling | 錯誤處理
+
+| Error Condition | AI Action |
+|-----------------|-----------|
+| 無法識別監控工具 | 詢問工具名稱或改以通用建議進行 |
+| 服務不存在或名稱不明 | 請使用者確認服務名稱或列出已知服務 |

package/bundled/skills/commands/runbook.md

@@ -9,3 +9,47 @@ argument-hint: "[create | drill | coverage] [alert name | 告警名稱]"
 See [SKILL.md](../runbook-assistant/SKILL.md) for full documentation.
 
 詳見 [SKILL.md](../runbook-assistant/SKILL.md)。
+
+## AI Agent Behavior | AI 代理行為
+
+> Follows [AI Command Behavior Standards](../../core/ai-command-behavior.md)
+
+### Entry Router | 進入路由
+
+| Input | AI Action |
+|-------|-----------|
+| `/runbook` | 詢問目標告警或服務，進入 runbook 導覽選單 |
+| `/runbook create` | 啟動 runbook 建立流程 |
+| `/runbook create <alert>` | 針對指定告警直接建立 runbook |
+| `/runbook drill` | 啟動 runbook 演練模擬流程 |
+| `/runbook coverage` | 產生 runbook 覆蓋率報告 |
+
+### Interaction Script | 互動腳本
+
+1. 確認操作模式（建立 / 演練 / 覆蓋率）
+2. 依模式執行對應流程，收集必要資訊
+3. 輸出 runbook 草稿或報告
+
+**Decision: 建立模式**
+- IF 告警名稱已提供 → 直接填入模板並產生草稿
+- IF 告警名稱未提供 → 詢問告警名稱、嚴重程度、負責團隊
+
+**Decision: 演練模式**
+- 逐步模擬告警觸發情境，確認執行步驟可行性
+- IF 步驟有疑義 → 停止並請使用者確認或修正
+
+🛑 **STOP**: runbook 草稿產生後等待使用者審查與修正
+
+### Stop Points | 停止點
+
+| Stop Point | 等待內容 |
+|-----------|---------|
+| 草稿產生後 | 使用者審查並確認內容正確 |
+| 演練每個關鍵步驟後 | 使用者確認步驟可執行 |
+
+### Error Handling | 錯誤處理
+
+| Error Condition | AI Action |
+|-----------------|-----------|
+| 告警名稱不明確 | 請使用者提供告警名稱或描述觸發條件 |
+| 無現有 runbook 可演練 | 提示先執行 `create` 建立 runbook |

package/bundled/skills/commands/slo.md

@@ -9,3 +9,48 @@ argument-hint: "[create | review | budget] [service name | 服務名稱]"
 See [SKILL.md](../slo-assistant/SKILL.md) for full documentation.
 
 詳見 [SKILL.md](../slo-assistant/SKILL.md)。
+
+## AI Agent Behavior | AI 代理行為
+
+> Follows [AI Command Behavior Standards](../../core/ai-command-behavior.md)
+
+### Entry Router | 進入路由
+
+| Input | AI Action |
+|-------|-----------|
+| `/slo` | 詢問目標服務，進入 SLO 設計導覽 |
+| `/slo create` | 啟動新 SLO 建立流程 |
+| `/slo create <service>` | 針對指定服務直接啟動 SLO 建立 |
+| `/slo review` | 審查現有 SLO 設定合理性 |
+| `/slo budget` | 查看 Error Budget 消耗狀況與建議 |
+
+### Interaction Script | 互動腳本
+
+1. 確認操作模式（建立 / 審查 / Error Budget）
+2. 依模式引導使用者完成 SLI 選擇、目標設定或現況分析
+3. 輸出 SLO 定義草稿或 Error Budget 報告
+
+**Decision: 建立模式**
+- 引導選擇 SLI 類型（Availability / Latency / Quality）
+- 詢問目標值（如 99.9%）與測量窗口（rolling 28d）
+- IF 目標值過高（>99.99%）→ 警告工程成本，建議先設較保守目標
+
+**Decision: Error Budget 模式**
+- IF budget 剩餘 < 10% → 建議暫停非必要發布
+- IF budget 已燒盡 → 提示凍結發布，優先處理可靠性
+
+🛑 **STOP**: SLO 草稿完成後等待使用者確認目標值與告警閾值
+
+### Stop Points | 停止點
+
+| Stop Point | 等待內容 |
+|-----------|---------|
+| SLI 選擇完成後 | 使用者確認選定的可靠性指標 |
+| SLO 草稿產生後 | 使用者審查目標值與告警設定 |
+
+### Error Handling | 錯誤處理
+
+| Error Condition | AI Action |
+|-----------------|-----------|
+| 服務無監控資料 | 建議先導入基礎 metrics，再設定 SLO |
+| 目標值格式錯誤 | 提示正確格式（如 `99.9%` 或 `0.999`） |

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

@@ -199,5 +199,5 @@ describe.skipIf(!BASE_URL)("Platform Admin Journey — T-001 → T-010", () => {
 ## 參考
 
 - 標準：[user-journey-testing.ai.yaml](../../.standards/user-journey-testing.ai.yaml)
-- 相關 XSPEC：XSPEC-128（UDS 標準定義）、XSPEC-129（VibeOps 實作範例）
+- 相關 XSPEC：XSPEC-128（UDS 標準定義）
 - 相關 Skill：`/e2e`（AC 層測試）、`/atdd`（驗收條件定義）

package/bundled/skills/orchestrate/SKILL.md

@@ -164,4 +164,4 @@ After completing the task, run: {task.verify_command}
 | 版本 | 日期 | 變更 |
 |------|------|------|
 | 2.0.0 | 2026-04-28 | 升格為 UDS 正式 Skill；Step 1 改為 Claude-native 解析（移除 plan-resolver-cli.js 依賴）；新增 Quality Gate / Fix Loop 章節（XSPEC-097 Phase 3） |
-| 1.0.0 | 2026-04-09 | 初始發布（DevAP packages/cli/skills/） |
+| 1.0.0 | 2026-04-09 | 初始發布（從上游遷移） |

package/bundled/skills/plan/SKILL.md

@@ -231,4 +231,4 @@ Claude 對 plan.json 執行以下驗證（無需外部引擎）：
 | 版本 | 日期 | 變更 |
 |------|------|------|
 | 2.0.0 | 2026-04-28 | 升格為 UDS 正式 Skill；移除 [DEVAP] 標記；Step 9 改為 Claude-native 驗證（XSPEC-097 Phase 3） |
-| 1.0.0 | 2026-04-09 | 初始發布（DevAP packages/cli/skills/） |
+| 1.0.0 | 2026-04-09 | 初始發布（從上游遷移） |

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

@@ -10,11 +10,10 @@ argument-hint: "[branch name or PR number | 分支名稱或 PR 編號]"
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
   PR lifecycle orchestration (5-step: CREATE→REVIEW→APPROVE→MERGE→CLEANUP,
-  size gate >400 lines block, CI gate, squash/merge strategy, gh CLI integration) extracted to:
-  - DevAP flow: dev-autopilot/.devap/flows/pr.flow.yaml
-  - DevAP CLI:  devap pr (packages/cli/src/commands/pr.ts)
-  This Skill retains: PR description template, merge strategy decision matrix, auto-review trigger rules.
-  Use `devap pr` for enforced lifecycle; this Skill for template and rule reference.
+  size gate >400 lines block, CI gate, squash/merge strategy, gh CLI integration) relocated to
+  adoption layer (XSPEC-095, 2026-04-28). This Skill retains: PR description template,
+  merge strategy decision matrix, auto-review trigger rules.
+  For enforced lifecycle execution, use your adoption layer's toolchain.
 -->
 
 # PR Automation Assistant | PR 自動化助手

package/bundled/skills/push/SKILL.md

@@ -238,7 +238,7 @@ After `/push` completes, the AI assistant should suggest:
 
 | Version | Date | Changes |
 |---------|------|---------|
-| 2.0.0 | 2026-04-28 | Restore workflow execution steps (DevAP decomposition XSPEC-097); remove deprecation notice |
+| 2.0.0 | 2026-04-28 | Restore workflow execution steps (XSPEC-097 採用層解耦); remove deprecation notice |
 | 1.0.0 | 2026-04-23 | Initial release — XSPEC-081 Phase 1 |
 
 ---

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

@@ -6,11 +6,10 @@ allowed-tools: Read, Write, Grep, Glob, Bash(git:*)
 argument-hint: "[spec name or feature | 規格名稱或功能]"
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
-  SDD lifecycle orchestration (7-phase state machine, phase transitions, gate checks) extracted to:
-  - DevAP flow: dev-autopilot/.devap/flows/sdd.flow.yaml
-  - DevAP CLI:  devap sdd (packages/cli/src/commands/sdd.ts) with --phase jump support
-  This Skill retains: spec format definition, state descriptions, delta operations, decision tree.
-  Use `devap sdd` for enforced lifecycle; this Skill for spec structure reference.
+  SDD lifecycle orchestration (7-phase state machine, phase transitions, gate checks) relocated to
+  adoption layer (XSPEC-095, 2026-04-28). This Skill retains: spec format definition, state
+  descriptions, delta operations, decision tree.
+  For enforced lifecycle execution, use your adoption layer's toolchain.
 -->
 
 # Spec-Driven Development Assistant | 規格驅動開發助手

package/bundled/skills/sweep/SKILL.md

@@ -34,7 +34,7 @@ Optionally auto-fix safe patterns (console.log, debugger statements).
 ```bash
 /sweep                        # Scan current directory, report findings
 /sweep --fix                  # Scan and auto-fix fixable patterns
-/sweep --report               # Scan and save report to .devap/sweep-report.json
+/sweep --report               # Scan and save report to .uds/sweep-report.json
 /sweep --path src/            # Scan specific directory
 /sweep --exclude "**/*.test.ts"  # Exclude patterns (glob)
 ```
@@ -78,7 +78,7 @@ Use Edit tool to apply changes file by file.
 Report: "Fixed N findings in M files."
 
 ### Step 6: Save Report (if --report)
-Write findings to `.devap/sweep-report.json`:
+Write findings to `.uds/sweep-report.json`:
 ```json
 {
   "timestamp": "<ISO8601>",
@@ -136,7 +136,7 @@ After `/sweep` completes, suggest:
 
 | Version | Date | Changes |
 |---------|------|---------|
-| 1.0.0 | 2026-04-28 | Initial release — XSPEC-097 Phase 1 (from DevAP sweep module) |
+| 1.0.0 | 2026-04-28 | Initial release — XSPEC-097 Phase 1 (從上游遷移) |
 
 ---
 

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

@@ -6,11 +6,10 @@ allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*), Bash(npx vitest:*)
 argument-hint: "[feature or file | 功能或檔案]"
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
-  TDD flow orchestration (RED→GREEN→REFACTOR cycle, test execution gates) extracted to:
-  - DevAP flow: dev-autopilot/.devap/flows/tdd.flow.yaml
-  - DevAP CLI:  devap tdd (packages/cli/src/commands/tdd.ts)
-  This Skill retains: TDD principles, FIRST rules, AAA format, language examples, workflow guide.
-  Use `devap tdd` for enforced interactive cycle; this Skill for practice reference.
+  TDD flow orchestration (RED→GREEN→REFACTOR cycle, test execution gates) relocated to adoption
+  layer (XSPEC-095, 2026-04-28). This Skill retains: TDD principles, FIRST rules, AAA format,
+  language examples, workflow guide.
+  For enforced interactive cycle, use your adoption layer's toolchain.
 -->
 
 # TDD Assistant | TDD 助手

package/package.json

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

package/src/commands/flow.js

@@ -3,13 +3,15 @@
  *
  * CLI 命令：管理自訂 SDLC 流程（create/list/validate/diff/export/import）。
  *
- * @deprecated XSPEC-095 (2026-04-28): This command is superseded by `devap flow`.
- *   The list/validate/diff operations have been extracted to DevAP:
- *   - CLI command: dev-autopilot/packages/cli/src/commands/flow-mgmt.ts
+ * @deprecated XSPEC-095 (2026-04-28): Runtime relocated to adoption layer.
+ *   The list/validate/diff operations are adoption-layer responsibility:
+ *   adoption layers must implement equivalent flow management commands
+ *   in their own toolchain.
  *
- *   棄用理由：UDS 專注於活動定義，DevAP 承擔流程編排（XSPEC-086 / DEC-049）。
+ *   棄用理由：UDS 專注於活動定義；流程編排由採用層承擔（XSPEC-086 /
+ *   DEC-049 — orchestration runtime moved to adoption layer 2026-04-28）。
  *   UDS 5.x 仍維持本命令可用（向後相容），UDS 6.0.0 將移除。
- *   建議遷移：`uds flow list/validate/diff` → `devap flow list/validate/diff`
+ *   建議遷移：實作於採用層工具鏈。
  */
 
 import { existsSync, readdirSync, readFileSync, writeFileSync, mkdirSync } from 'fs';

package/src/commands/start.js

@@ -3,14 +3,15 @@
  *
  * 啟動一個具名任務（Mission）並設定任務意圖。
  *
- * @deprecated XSPEC-095 (2026-04-28): This command is superseded by `devap mission`.
- *   The orchestration logic has been extracted to DevAP:
- *   - Core module: dev-autopilot/packages/core/src/mission/
- *   - CLI command: dev-autopilot/packages/cli/src/commands/mission.ts
+ * @deprecated XSPEC-095 (2026-04-28): Runtime relocated to adoption layer.
+ *   The orchestration logic is adoption-layer responsibility:
+ *   adoption layers must implement equivalent mission start commands
+ *   in their own toolchain.
  *
- *   棄用理由：UDS 專注於活動定義，DevAP 承擔流程編排（XSPEC-086 / DEC-049）。
+ *   棄用理由：UDS 專注於活動定義；流程編排由採用層承擔（XSPEC-086 /
+ *   DEC-049 — orchestration runtime moved to adoption layer 2026-04-28）。
  *   UDS 5.x 仍維持本命令可用（向後相容），UDS 6.0.0 將移除。
- *   建議遷移：`uds start ...` → `devap mission start <type> "<intent>"`
+ *   建議遷移：實作於採用層工具鏈。
  */
 import chalk from 'chalk';
 import { select, input, confirm as inquirerConfirm } from '@inquirer/prompts';

package/src/commands/sweep.js

@@ -6,14 +6,15 @@
  *
  * @module commands/sweep
  * @see docs/specs/system/vibe-coding-integration.md (AC-2)
- * @deprecated XSPEC-095 (2026-04-28): This command is superseded by `devap sweep`.
- *   The orchestration logic has been extracted to DevAP:
- *   - Core module: dev-autopilot/packages/core/src/sweep/
- *   - CLI command: dev-autopilot/packages/cli/src/commands/sweep.ts
+ * @deprecated XSPEC-095 (2026-04-28): Runtime relocated to adoption layer.
+ *   The orchestration logic is adoption-layer responsibility:
+ *   adoption layers must implement equivalent sweep commands in their
+ *   own toolchain.
  *
- *   棄用理由：UDS 專注於活動定義，DevAP 承擔流程編排（XSPEC-086 / DEC-049）。
+ *   棄用理由：UDS 專注於活動定義；流程編排由採用層承擔（XSPEC-086 /
+ *   DEC-049 — orchestration runtime moved to adoption layer 2026-04-28）。
  *   UDS 5.x 仍維持本命令可用（向後相容），UDS 6.0.0 將移除。
- *   建議遷移：`uds sweep ...` → `devap sweep [--fix] [--report]`
+ *   建議遷移：實作於採用層工具鏈。
  */
 
 import chalk from 'chalk';

package/src/commands/workflow.js

@@ -4,14 +4,15 @@
  * CLI commands for listing and installing UDS workflows.
  *
  * @version 1.0.0
- * @deprecated XSPEC-095 (2026-04-28): This command is superseded by `devap workflow`.
- *   The orchestration logic has been extracted to DevAP:
- *   - Core module: dev-autopilot/packages/core/src/workflow-state/ + core/src/flow/
- *   - CLI command: dev-autopilot/packages/cli/src/commands/workflow.ts
+ * @deprecated XSPEC-095 (2026-04-28): Runtime relocated to adoption layer.
+ *   The orchestration logic is adoption-layer responsibility:
+ *   adoption layers must implement equivalent workflow commands in
+ *   their own toolchain.
  *
- *   棄用理由：UDS 專注於活動定義，DevAP 承擔流程編排（XSPEC-086 / DEC-049）。
+ *   棄用理由：UDS 專注於活動定義；流程編排由採用層承擔（XSPEC-086 /
+ *   DEC-049 — orchestration runtime moved to adoption layer 2026-04-28）。
  *   UDS 5.x 仍維持本命令可用（向後相容），UDS 6.0.0 將移除。
- *   建議遷移：`uds workflow ...` → `devap workflow list/execute/status`
+ *   建議遷移：實作於採用層工具鏈。
  */
 
 import chalk from 'chalk';

package/src/core/agent-communication-protocol.js

@@ -11,6 +11,12 @@ export const UNIFIED_STATUSES = [
   'needs_context', 'skipped', 'timeout', 'unknown',
 ];
 
+// Reference status mappings. `uds` is UDS's own native status set;
+// the other two entries are illustrative example mappings showing how
+// adoption-layer runtimes can plug their own status vocabularies into
+// the unified status code set. Adoption layers should add their own
+// keys (or call mapStatus with their own project name) — these example
+// keys are not endorsements of any specific downstream product.
 const STATUS_MAP = {
   uds: {
     DONE: 'success',
@@ -18,7 +24,7 @@ const STATUS_MAP = {
     NEEDS_CONTEXT: 'needs_context',
     BLOCKED: 'blocked',
   },
-  devap: {
+  adapter_example_a: {
     success: 'success',
     failed: 'failed',
     skipped: 'skipped',
@@ -27,7 +33,7 @@ const STATUS_MAP = {
     needs_context: 'needs_context',
     blocked: 'blocked',
   },
-  vibeops: {
+  adapter_example_b: {
     success: 'success',
     partial: 'success_partial',
     failure: 'failed',
@@ -38,7 +44,8 @@ const STATUS_MAP = {
  * Map a project-specific status to unified status code.
  * Unknown statuses map to 'unknown' with a warning.
  * @param {string} status - Project-specific status code
- * @param {string} project - Source project ('uds' | 'devap' | 'vibeops')
+ * @param {string} project - Source project (e.g. 'uds', 'adapter_example_a',
+ *   'adapter_example_b', or any custom adoption-layer project key)
  * @returns {{ unified: string, warning?: { original: string, project: string } }}
  */
 export function mapStatus(status, project) {