universal-dev-standards 5.15.1 → 5.16.0

package/bundled/locales/zh-CN/skills/runbook-assistant/guide.md

@@ -0,0 +1,216 @@
+---
+source: ../../../../skills/runbook-assistant/guide.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-06-02
+source_hash: 79012dab91fb
+status: current
+scope: universal
+description: |
+  指导 runbook 的创建、组织与验证。
+  使用时机：编写 runbook、审查运维流程、规划演练、评估覆盖率。
+  关键词：runbook、运维、incident、on-call、演练、SOP、运维手册、演练。
+---
+
+# Runbook Assistant
+
+> **语言**：English | [繁體中文](../../locales/zh-TW/skills/runbook-assistant/SKILL.md)
+
+**版本**：1.0.0
+**最后更新**：2026-04-01
+**适用范围**：Claude Code Skills
+
+---
+
+## 目的
+
+本 skill 帮助团队编写、组织和验证用于运维流程和 incident 响应的 runbook。它涵盖 5 种 runbook 类型、标准的 7 节模板、编写质量原则、演练流程以及覆盖率报告。
+
+---
+
+## 快速参考（YAML 压缩版）
+
+```yaml
+# === 5 RUNBOOK TYPES 五种类型 ===
+types:
+  alert_response:
+    purpose: "Diagnose and fix a specific alert / 诊断并修复特定告警"
+    example: "api-latency-high.md"
+    trigger: "Alert fires"
+  standard_operation:
+    purpose: "Routine operational procedures / 例行运维流程"
+    example: "database-backup-restore.md"
+    trigger: "Scheduled or on-demand"
+  emergency_procedure:
+    purpose: "Major incident rapid response / 重大事件快速响应"
+    example: "full-service-outage.md"
+    trigger: "SEV-1 incident"
+  change_procedure:
+    purpose: "Planned change execution steps / 计划变更执行步骤"
+    example: "database-migration.md"
+    trigger: "Change window"
+  troubleshooting_guide:
+    purpose: "General problem investigation / 一般问题排查"
+    example: "memory-leak.md"
+    trigger: "Ad-hoc investigation"
+
+# === STANDARD TEMPLATE 标准模板 (7 Sections) ===
+template_sections:
+  1_overview:
+    fields: ["Alert Name", "Severity (P1-P4)", "Related Services", "Last Updated", "Owner", "Last Drilled"]
+  2_symptoms:
+    content: "Observable behaviors — what users see, how system behaves / 可观察的异常行为"
+  3_impact_assessment:
+    fields: ["Affected users scope", "Business impact (revenue, reputation)", "Upstream/downstream cascading"]
+  4_diagnostic_steps:
+    format: "Numbered steps with copy-paste commands and expected output / 编号步骤+可复制命令+预期输出"
+    branching: "If [condition A] → Scenario A; If [condition B] → Scenario B"
+  5_fix_steps:
+    format: "Per-scenario fix with verification command after each step / 每场景修复+每步骤验证"
+    include: ["Specific commands", "Verification check", "Estimated time"]
+  6_escalation:
+    fields: ["Contact person/team", "Channel (Slack/phone)", "Backup contact", "Time threshold"]
+  7_post_actions:
+    checklist: ["Update runbook", "Create postmortem if P1/P2", "Notify stakeholders", "Record MTTD/MTTR"]
+
+optional_sections: ["Prerequisites", "Rollback Steps", "Related Runbooks", "Changelog"]
+
+# === WRITING QUALITY 编写质量 (6 Principles) ===
+six_principles:
+  reproducible:
+    rule: "Steps specific enough to copy-paste and execute / 步骤具体到可直接复制执行"
+    good: "kubectl rollout restart deployment/payment-service -n production"
+    bad: "Restart the payment service"
+  unambiguous:
+    rule: "Each step has exactly one interpretation / 每个步骤只有一种解读"
+    good: "Restart the payment-service Pod in the production namespace"
+    bad: "Restart the service"
+  decision_points:
+    rule: "Branch conditions are explicit with clear criteria / 分支条件明确有具体判断标准"
+    good: "If CPU > 90%, execute Plan A; otherwise Plan B"
+    bad: "If the server seems overloaded..."
+  rollback:
+    rule: "Failed fix steps have a fallback plan / 失败的修复步骤有回退方案"
+  verification:
+    rule: "Each fix step has success confirmation / 每个修复步骤有成功验证"
+    good: "Run curl health-check and verify HTTP 200"
+    bad: "Check that it's working"
+  time_bounded:
+    rule: "Expected completion time is stated / 标明预期完成时间"
+    good: "This step typically takes 2-5 minutes"
+
+anti_patterns:
+  - {bad: "Contact the team", fix: "Name specific people and channels / 指名具体人员和频道"}
+  - {bad: "Check the logs", fix: "Provide exact log query / 提供精确的日志查询"}
+  - {bad: "If needed, scale up", fix: "Define threshold and target / 定义阈值和目标"}
+  - {bad: "Outdated commands", fix: "Regular review cycle / 定期审查周期"}
+
+# === DRILL PROCESS 演练机制 ===
+drill:
+  schedule:
+    highest: {condition: "P1 alert runbooks", frequency: "Monthly / 每月"}
+    high: {condition: "P2 alert runbooks", frequency: "Quarterly / 每季"}
+    medium: {condition: "Emergency procedures", frequency: "Quarterly / 每季"}
+    low: {condition: "Other runbooks", frequency: "Bi-annually / 每半年"}
+  recording:
+    fields: ["Date", "Participants", "Result (Pass/Partial/Fail)", "Estimated vs Actual time", "Issues found", "Updates required"]
+  failure_handling:
+    1: "Immediately flag runbook as needing update / 立即标记需更新"
+    2: "Create action item with owner and deadline / 建立待办事项"
+    3: "Re-drill after update / 更新后重新演练"
+    4: "Not valid until re-drill passes / 重新演练通过前视为无效"
+
+# === REVIEW CYCLES 审查周期 ===
+review_cycles:
+  alert_response: "Quarterly (3 months) / 每季"
+  emergency_procedure: "Monthly / 每月"
+  standard_operation: "Bi-annually (6 months) / 每半年"
+  change_procedure: "After each use / 每次使用后"
+  troubleshooting_guide: "Bi-annually (6 months) / 每半年"
+
+staleness: "Runbook is stale when Last Updated exceeds review cycle or not drilled within drill cycle / 超过审查周期或演练周期即为过时"
+
+# === COVERAGE REPORT 覆盖率报告 ===
+coverage:
+  target:
+    P1_P2: "100% alerts must have runbooks / P1/P2 告警必须 100% 有手册"
+    P3_P4: "> 80% alerts should have runbooks / P3/P4 告警应 > 80% 有手册"
+  report_format:
+    columns: ["Alert Level", "Total Alerts", "With Runbook", "Coverage", "Target"]
+  action: "List alerts without runbooks for creation / 列出无手册的告警待建立"
+
+# === DIRECTORY STRUCTURE 目录结构 ===
+organization:
+  root: "docs/runbooks/"
+  subdirs: ["alerts/", "operations/", "emergency/", "changes/", "troubleshooting/"]
+  naming: "kebab-case, describe the PROBLEM not the solution / 描述问题而非解法"
+  index: "README.md with runbook table (name, severity, services, date)"
+```
+
+---
+
+## 与相关技能整合 / Integration with Related Skills
+
+| Skill | 整合点 | 说明 |
+|-------|-------------------|-------------|
+| `/observability --alerting` | 告警与 Runbook 关联 | 每条告警规则都应包含 `runbook_url` 注解 |
+| `/incident` | 事后检讨到 Runbook 流程 | 事后检讨后：更新现有 runbook 或为新的故障模式创建新 runbook |
+| `/slo` | 燃尽率告警 | SLO 燃尽率告警应链接到对应的 runbook |
+
+### 告警关联手册 / Alert-to-Runbook Linking
+
+```yaml
+# In alert rule definition
+annotations:
+  runbook_url: "https://wiki.example.com/runbooks/alerts/api-latency-high"
+```
+
+### 事后检讨到手册流程 / Postmortem-to-Runbook Flow
+
+- incident 揭露了 runbook 的缺漏 → 更新该 runbook
+- incident 是全新的故障模式 → 创建新的 runbook
+- 将事后检讨链接到 runbook 的变更日志
+
+---
+
+## 配置检测
+
+### 检测顺序
+
+1. 检查 `CONTRIBUTING.md` 中的 "Disabled Skills" 章节
+2. 检查 `CONTRIBUTING.md` 中的 "Runbook Standards" 章节
+3. 若未找到，**默认采用标准 runbook 实践**
+
+---
+
+## 详细指南
+
+完整标准请参见：
+- [Runbook Standards](../../core/runbook-standards.md)
+
+---
+
+## 相关标准
+
+- [Runbook Standards](../../core/runbook-standards.md) - 核心标准
+- [Alerting Standards](../../core/alerting-standards.md) - 告警设计与 runbook 关联
+- [Postmortem Standards](../../core/postmortem-standards.md) - incident 后审查
+- [Observability Standards](../../core/observability-standards.md) - 监控与仪表盘
+- [Observability Assistant](../observability-assistant/SKILL.md) - 监控设置
+- [SLO Assistant](../slo-assistant/SKILL.md) - 基于 SLO 的告警
+
+---
+
+## 版本历史
+
+| 版本 | 日期 | 变更 |
+|---------|------|---------|
+| 1.0.0 | 2026-04-01 | 首次发布 |
+
+---
+
+## 许可证
+
+本 skill 以 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 许可发布。
+
+**来源**：[universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/locales/zh-CN/skills/skill-builder/SKILL.md

@@ -0,0 +1,149 @@
+---
+name: skill-builder
+source: ../../../../skills/skill-builder/SKILL.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-06-02
+source_hash: 5d91e5974c44
+status: current
+scope: universal
+description: |
+  [UDS] 识别重复流程并以正确的开发深度构建 Skill
+allowed-tools: Read, Glob, Grep, Write, Edit, Bash
+argument-hint: "[process description | 流程描述]"
+---
+
+# 流程转 Skill 助手
+
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/process-automation/SKILL.md)
+
+引导你从「我一直在手动做这件事」走到「拥有一个正确构建的 Skill」，并在这一过程中保持适量的流程治理。
+
+## 何时使用
+
+- 你已经用同样的多步骤流程手动执行 ≥ 3 次
+- 同事第 3 次问你「我们是怎么做 X 的？」
+- 你临时建了一个 Skill，现在想把它正式化
+
+## 核心原则
+
+> Skill 记录的是**流程知识**。Memory 记录的是历史事实。
+> 当你注意到自己重复执行相同的步骤时，那就是一个 Skill 候选。
+
+## 决策树
+
+```
+New Skill needed?
+├── Modifying existing Skill?
+│     → Delta path: append ## MODIFIED / ## ADDED to existing SKILL.md
+│                   update version field → done
+│
+├── Answer these 4 questions (any "yes" → Complex):
+│     1. More than 7 steps?
+│     2. Branching logic between steps (if/else)?
+│     3. Requires knowledge from 3+ separate standards/decisions?
+│     4. Output directly affects sub-project source code?
+│
+├── All "no" → Simple path
+│     → Fill Skill Brief (templates/SKILL-BRIEF-TEMPLATE.md)
+│     → Create SKILL.md directly (no XSPEC needed)
+│
+└── Any "yes" → Complex path
+      → Create XSPEC first → run /sdd
+      → Return here after XSPEC Approved
+
+Deprecating a Skill?
+  → Add to SKILL.md frontmatter:
+      status: deprecated
+      deprecated_at: YYYY-MM-DD
+      deprecated_reason: "..."
+      superseded_by: "/new-skill"   (if applicable)
+  → Mark archived in SKILL-CANDIDATES.md
+```
+
+## 摆放位置决策
+
+在创建 SKILL.md 前，先决定它应该放在哪里：
+
+| 条件 | 摆放位置 |
+|-----------|-----------|
+| 步骤引用项目特定路径（如 TECH-RADAR.md、DEC-*.md） | 项目：`{project}/.claude/skills/` |
+| 步骤为通用流程（无项目特定路径） | UDS：`skills/{name}/` + zh-TW locale |
+
+## 工作流程
+
+### Step 1 — 描述流程
+
+捕捉重复的步骤序列：
+- 哪些步骤？按什么顺序？
+- 目前手动执行过几次？
+- 触及哪些工具或文件？
+
+### Step 2 — 更新 SKILL-CANDIDATES.md
+
+打开你项目的 `SKILL-CANDIDATES.md`（首次请从 `templates/SKILL-CANDIDATES.md` 复制）：
+- 尚未记录 → 新增一行，填入当前次数
+- 已记录 → 增加次数
+- 次数达到 3 → 标记 trigger ✅，继续执行
+
+### Step 3 — 选择路径（Simple / Complex / Delta）
+
+回答这 4 个判断问题。确定：Simple、Complex 或 Delta。
+
+### Step 4a — Simple：填写 Skill Brief
+
+使用 `templates/SKILL-BRIEF-TEMPLATE.md`：
+- 触发情境（何时会用到？）
+- 核心步骤（3 ~ 7 个，有顺序）
+- 验收条件（2 ~ 3 条）
+- 范围外（明确边界）
+
+### Step 4b — Complex：创建 XSPEC
+
+执行 `/sdd` 创建 XSPEC。XSPEC Approved 之后回到 Step 5。
+
+### Step 4c — Delta：识别变更范围
+
+识别现有 SKILL.md 中哪些区段需要变更。
+在文件末尾加入 `## MODIFIED Requirements` 或 `## ADDED Requirements`。
+
+### Step 5 — 创建 / 更新 SKILL.md
+
+依据 Brief 或 XSPEC 生成 SKILL.md：
+- 确认 frontmatter：`name`、`scope`、`description`、`allowed-tools`
+- UDS 通用 Skill：同步创建 zh-TW locale 版本
+- 项目 Skill：放在 `{project}/.claude/skills/{name}/SKILL.md`
+
+### Step 6 — 更新 SKILL-CANDIDATES.md
+
+将候选行标记为：trigger ✅、Skill 列填写完成。
+
+### Step 7 — Commit
+
+```
+feat(skills): Add /{skill-name} skill. 新增 /{skill-name} Skill。
+
+{English description, 1-2 lines}
+
+{Chinese description, 1-2 lines}
+
+Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
+```
+
+## 输出检查清单
+
+完成所有步骤后，请确认：
+
+- [ ] `SKILL-CANDIDATES.md` 已更新（trigger ✅、Skill 名称已填）
+- [ ] `SKILL.md` 已创建并具备完整 frontmatter（`name` / `scope` / `description` / `allowed-tools`）
+- [ ] Simple 路径：Skill Brief 已引用或保留
+- [ ] Complex 路径：XSPEC ID 已记录在 SKILL.md header comment 中
+- [ ] UDS skill：已创建 zh-TW locale 文件
+- [ ] 棄用（Deprecated）：frontmatter 含 `status: deprecated`
+- [ ] git commit 已完成
+
+## 参考
+
+- Skill Brief 模板：[templates/SKILL-BRIEF-TEMPLATE.md](../../templates/SKILL-BRIEF-TEMPLATE.md)
+- 候选追踪：[templates/SKILL-CANDIDATES.md](../../templates/SKILL-CANDIDATES.md)（请复制到你的项目）
+- ADR 标准：[core/adr-standards.md](../../core/adr-standards.md)

package/bundled/locales/zh-CN/skills/slo-assistant/guide.md

@@ -0,0 +1,188 @@
+---
+source: ../../../../skills/slo-assistant/guide.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-06-02
+source_hash: 3c3397aec3fe
+status: current
+scope: universal
+description: |
+  指导 SLI/SLO/Error Budget 的定义与管理。
+  使用时机：定义 SLO、选取 SLI、计算 error budget、设定可靠性目标。
+  关键字：SLI、SLO、SLA、error budget、可靠性、burn rate、服务水准、错误预算。
+---
+
+# SLO Assistant
+
+> **语言**：English | [繁體中文](../../locales/zh-TW/skills/slo-assistant/SKILL.md)
+
+**版本**：1.0.0
+**最后更新**：2026-04-01
+**适用范围**：Claude Code Skills
+
+---
+
+## 目的
+
+本技能帮助团队定义、实现并管理服务水准目标（Service Level Objectives）。内容涵盖针对不同服务类型的 SLI 选取、五步骤 SLO 设定方法论、Error Budget 计算与政策，以及开箱即用的模板。
+
+---
+
+## 快速参考（YAML 压缩版）
+
+```yaml
+# === KEY CONCEPTS 核心概念 ===
+definitions:
+  SLI: "Service Level Indicator — quantitative measurement of service behavior / 服務品質的量化量測"
+  SLO: "Service Level Objective — internal target for SLI over a window / SLI 的內部目標值"
+  SLA: "Service Level Agreement — external contract with penalties / 外部合約，違反有罰則"
+  error_budget: "Allowed unreliability = 1 - SLO target / 允許的不可靠度"
+
+relationship: "SLI ── measures ──► SLO ── stricter than ──► SLA"
+rule: "SLO should be stricter than SLA to provide buffer / SLO 應比 SLA 嚴格以提供緩衝"
+
+# === SLI SELECTION GUIDE SLI 選取指南 ===
+sli_by_service_type:
+  api_services:
+    availability: "Non-5xx / Total requests"
+    latency: "Requests below duration threshold / Total"
+    quality: "Non-degraded responses / Total"
+  batch_jobs:
+    freshness: "Time since last success within threshold"
+    correctness: "Correctly processed / Total records"
+    coverage: "Completed batches / Scheduled batches"
+  frontend:
+    load_performance: "LCP<2.5s, FID<100ms, CLS<0.1 / Total pages"
+    availability: "Successful loads / Total loads"
+    interaction_delay: "Actions with response < threshold / Total"
+
+sli_quick_select:
+  api: "→ Availability + Latency + Quality"
+  batch: "→ Freshness + Correctness + Coverage"
+  frontend: "→ LCP/FID/CLS + Availability"
+
+# === 5-STEP SLO METHODOLOGY 五步驟設定法 ===
+slo_methodology:
+  step_1_select_sli: "Choose 1-3 most meaningful SLIs per service / 每個服務選 1-3 個最有意義的 SLI"
+  step_2_measurement_window:
+    rolling_28d: "Recommended; smooths weekly patterns / 推薦，平滑週間波動"
+    calendar_month: "Aligns with business reporting / 對齊業務報告週期"
+  step_3_set_target:
+    "99%": "7.3h downtime/month — internal tools / 內部工具"
+    "99.5%": "3.65h — general B2B / 一般 B2B"
+    "99.9%": "43.8min — consumer-facing / 面向消費者"
+    "99.95%": "21.9min — financial, healthcare / 金融、醫療"
+    "99.99%": "4.38min — infrastructure, payments / 基礎設施"
+    tip: "Don't set higher than you can sustain / 別設得比你能維持的更高"
+  step_4_compliance_formula: |
+    SLO Compliance = (Good Events / Total Events) x 100%
+    Define: Good Events, Total Events, Window, Target
+  step_5_document: "Record using SLO Document Template / 使用 SLO 文件範本記錄"
+
+iterative_adjustment:
+  budget_underused: "Consider tightening SLO / 考慮收緊 SLO"
+  budget_exhausted_often: "Loosen SLO or invest in reliability / 放寬或投資可靠性"
+  users_unhappy_despite_meeting: "Revisit SLI selection / 重新檢視 SLI 選取"
+  team_burnout: "SLO may be too aggressive / SLO 可能過於激進"
+
+# === ERROR BUDGET 錯誤預算 ===
+error_budget:
+  formula: "Budget = 1 - SLO Target"
+  example: "99.9% over 28d → 0.1% → 40.32 min allowed downtime"
+  quick_calc: "Budget = (1 - target) x window_minutes"
+
+burn_rate_alerting:
+  fast_burn: {threshold: "2% in 1h", action: "Page (P1)", meaning: "Budget gone in ~2 days"}
+  medium_burn: {threshold: "5% in 6h", action: "Alert (P2)", meaning: "Budget gone in ~5 days"}
+  slow_burn: {threshold: "10% in 3d", action: "Ticket (P3)", meaning: "May exhaust before month end"}
+
+budget_exhaustion_policies:
+  freeze_releases: "Halt non-reliability features until recovery / 凍結非可靠性功能發布"
+  reliability_sprint: "Dedicate sprint to reliability / 專注衝刺可靠性改善"
+  enhanced_review: "Additional production-readiness review / 加強生產就緒審查"
+  lower_slo: "Reduce target after stakeholder agreement / 經利害關係人同意後降低目標"
+  rule: "Agree on policy BEFORE budget exhaustion / 在預算耗盡前就達成政策共識"
+
+# === SLO TEMPLATES 範本庫 ===
+templates:
+  api_service:
+    availability: {sli: "Non-5xx / Total", default_slo: "99.9%"}
+    latency: {sli: "P99 < threshold / Total", default_slo: "99%"}
+    error_rate: {sli: "Non-5xx+timeout / Total", default_slo: "99.9%"}
+  batch_job:
+    freshness: {sli: "Max delay < threshold", default_slo: "99.5%"}
+    correctness: {sli: "Correct / Total", default_slo: "99.99%"}
+    completion: {sli: "Completed / Scheduled", default_slo: "99.9%"}
+  frontend:
+    load_perf: {sli: "LCP<2.5s proportion", default_slo: "90%"}
+    interaction: {sli: "FID<100ms proportion", default_slo: "95%"}
+    visual: {sli: "CLS<0.1 proportion", default_slo: "95%"}
+```
+
+---
+
+## 与相关技能的整合 / Integration with Related Skills
+
+| 技能 | 整合点 | 说明 |
+|-------|-------------------|-------------|
+| `/observability` | SLI 数据来源 | 来自三大支柱的指标用于 SLI 计算 |
+| `/incident` | SLO 影响评估 | 在事件报告中纳入已消耗与剩余的 Error Budget |
+| `/sdd` | 规格中的 SLO | 新服务规格应包含 SLO 目标章节 |
+
+### 事件回应中的 SLO / SLO in Incident Response
+
+报告事件时，请纳入：
+- **受影响的 SLI**：哪个指标受到影响
+- **已消耗的 Error Budget**：分钟数或百分比
+- **剩余预算**：当前窗口内还剩多少
+
+### 规格驱动开发中的 SLO / SLO in Spec-Driven Development
+
+使用 `/sdd` 定义新服务时，请新增一个 SLO 章节：
+- 附理由的 SLI 选取
+- 附论证的目标值
+- Error Budget 政策选择
+
+---
+
+## 配置侦测
+
+### 侦测顺序
+
+1. 检查 `CONTRIBUTING.md` 是否有 "Disabled Skills" 章节
+2. 检查 `CONTRIBUTING.md` 是否有 "SLO Standards" 章节
+3. 若未找到，**预设采用标准 SLO 实践**
+
+---
+
+## 详细准则
+
+完整标准请参阅：
+- [SLO Standards](../../core/slo-standards.md)
+
+---
+
+## 相关标准
+
+- [SLO Standards](../../core/slo-standards.md) - 核心标准
+- [Observability Standards](../../core/observability-standards.md) - 三大支柱框架
+- [Alerting Standards](../../core/alerting-standards.md) - 基于 SLO 的告警
+- [Performance Standards](../../core/performance-standards.md) - 性能目标
+- [Observability Assistant](../observability-assistant/SKILL.md) - 监控设定
+- [Runbook Assistant](../runbook-assistant/SKILL.md) - 告警回应程序
+
+---
+
+## 版本历史
+
+| 版本 | 日期 | 变更 |
+|---------|------|---------|
+| 1.0.0 | 2026-04-01 | 首次发布 |
+
+---
+
+## 授权
+
+本技能依 [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) 发布。
+
+**来源**：[universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/locales/zh-CN/skills/spec-derivation/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: spec-derive
+source: ../../../../skills/spec-derivation/SKILL.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-06-02
+source_hash: ae80ca14f9b9
+status: current
+scope: partial
+description: |
+  [UDS] 从规格衍生 BDD 场景、TDD 骨架或 ATDD 表格
+allowed-tools: Read, Write, Grep, Glob
+argument-hint: "[all|bdd|tdd|it|e2e|atdd] <spec-file>"
+prerequisites: ["spec-approved"]
+disable-model-invocation: true
+---
+
+# 正向推演
+
+> **语言**: [English](../../../../skills/spec-derivation/SKILL.md) | 简体中文
+
+从已批准的 SDD 规格生成衍生工件（BDD 场景、TDD 骨架、ATDD 表格）。
+
+## 子命令
+
+| 子命令 | 说明 | 输出 |
+|--------|------|------|
+| `all` | 完整推演管线（BDD + TDD + IT + E2E + ATDD + Contracts） | `.feature` + `.test.*` + `.it.test.*` + `.e2e.test.*` + `.md` + `.json` |
+| `bdd` | 仅生成 BDD 场景 | `.feature` |
+| `tdd` | 仅生成 TDD 骨架 | `.test.*` |
+| `it` | 生成集成测试骨架 | `.it.test.*` |
+| `e2e` | 生成 E2E 测试骨架 | `.e2e.test.*` |
+| `atdd` | 生成 ATDD 测试表格 | `.md`（Markdown 表格） |
+
+## 工作流程
+
+1. **读取 Spec** — 分析输入的 `SPEC-XXX.md` 文件
+2. **抽取 AC** — 解析所有验收条件
+3. **生成工件** — 创建 BDD / TDD / ATDD 输出
+4. **验证** — 确认 AC 与生成项目为一对一对应
+
+## 防幻觉规则
+
+| 规则 | 说明 |
+|------|------|
+| **1:1 对应** | 每个 AC 对应一个测试 / 场景 |
+| **可追溯性** | 所有工件都引用 Spec ID 与 AC ID |
+| **不发明** | 不新增规格外的场景 |
+
+## 产生工件标签
+
+| 标签 | 含义 |
+|------|------|
+| `[Source]` | 直接来自规格的内容 |
+| `[Derived]` | 从来源转换而来 |
+| `[Generated]` | AI 生成的结构 |
+| `[TODO]` | 需人工实现 |
+
+## 使用方式
+
+```
+/derive all specs/SPEC-001.md           - 完整推演管线
+/derive bdd specs/SPEC-001.md           - 仅推演 BDD 场景
+/derive tdd specs/SPEC-001.md           - 仅推演 TDD 骨架
+/derive it specs/SPEC-001.md            - 推演集成测试骨架
+/derive e2e specs/SPEC-001.md           - 推演 E2E 测试骨架
+/derive atdd specs/SPEC-001.md          - 推演 ATDD 表格
+```
+
+## 下一步引导
+
+`/derive` 完成后，AI 助手应建议：
+
+> **测试工件已生成。建议下一步：**
+> - 执行 `/tdd` 开始红绿重构循环 ⭐ **推荐**
+> - 执行 `/bdd` 细化 Gherkin 场景
+> - 检查生成的 `[TODO]` 标记并补齐实现
+
+## 参考
+
+- 详细指南：[guide.md](./guide.md)
+- 核心标准：[forward-derivation-standards.md](../../../../core/forward-derivation-standards.md)
+
+## AI 代理行为
+
+> 完整的 AI 行为定义请参阅对应的命令文件：[`/derive`](../../../../skills/commands/derive.md#ai-agent-behavior--ai-代理行为)