Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill spec-driven-dev명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
[UDS] 以 Claude 原生 Agent tool 编排多任务执行计划（DAG-based，无外部引擎）。 Use when: executing a plan.json file with parallel/sequential task dependencies. Keywords: orchestrate, plan, execute, DAG, task plan, 编排, 执行计划, 并行.
[UDS] 从 Spec 文档、OpenSpec 变更或自由文本需求生成 plan.json。 Use when: converting specifications into executable task plans for /orchestrate. Keywords: plan, spec, task plan, 计划, 规格, 任务, plan.json, DAG.
[UDS] AI 辅助 git push 安全层：质量门禁 + 协作护栏。 Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches. Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保护分支, 质量门禁.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | spec-driven-dev |
| source | ../../../../skills/spec-driven-dev/SKILL.md |
| source_version | 1.2.0 |
| translation_version | 1.2.0 |
| last_synced | "2026-06-02T00:00:00.000Z" |
| source_hash | 195f50bcbfb7 |
| status | current |
| description | [UDS] 在撰寫程式碼前，建立、審查和管理規格文件 |
在撰寫程式碼前，建立、審查和管理規格文件。
語言: English | 繁體中文
/sdd vs uds spec | 何時使用| 情境 | /sdd | uds spec |
|---|---|---|
| 具審查循環的正式功能開發 | ✅ | ❌ |
| 完整規格生命週期（Draft → Archived） | ✅ | ❌ |
| 快速原型 / Vibe coding | ❌ | ✅ |
| 小型漸進式變更 | ❌ | ✅ |
| 需要利害關係人簽核 | ✅ | ❌ |
| 從自然語言意圖產生微規格（micro-spec） | ❌ | ✅ |
/sdd= 正式開發的完整規格生命週期uds spec= 快速迭代的輕量微規格
specs/、docs/specs/ 或專案規格目錄SPEC-NNN 或 kebab-case 變更 IDNew request? | 新需求？
├─ Bug fix restoring spec behavior? → Fix directly | 直接修復
├─ Typo/format/comment? → Fix directly | 直接修復
├─ Dependency update (non-breaking)? → Fix directly | 直接修復
├─ New feature/capability? → Create proposal | 建立提案
├─ Breaking change? → Create proposal | 建立提案
├─ Architecture change? → Create proposal | 建立提案
├─ Agent/role definition (spans multiple features)? → Use spec-type: agent | 使用 Agent SPEC template
└─ Unclear? → Create proposal (safer) | 建立提案（較安全）
DISCUSS ──► CREATE ──► REVIEW ──► APPROVE ──► IMPLEMENT ──► VERIFY ──► ARCHIVE
在撰寫規格前，捕捉灰色地帶、建立治理原則、解決模糊之處。
定義需求、技術設計、驗收條件與測試計畫。
與利害關係人一同檢查完整性、一致性與可行性。
在開始實作前取得利害關係人簽核。
依照核准的規格進行開發，參照需求與 AC。
確保實作符合規格、所有測試通過、AC 已滿足。
將完成的規格歸檔，並附上 commit／PR 連結。
| 狀態 | 說明（英） | 說明 |
|---|---|---|
| Draft | Work in progress | 草稿中 |
| Review | Under review | 審查中 |
| Approved | Ready for implementation | 已核准 |
| Implemented | Code complete | 已實作 |
| Archived | Completed or deprecated | 已歸檔 |
# [SPEC-ID] Feature: [Name]
## Overview
Brief description of the proposed change.
## Motivation
Why is this change needed? What problem does it solve?
## Requirements
### Requirement: [Name]
The system SHALL [behavior description].
#### Scenario: [Success case]
- **GIVEN** [initial context]
- **WHEN** [action performed]
- **THEN** [expected result]
## Acceptance Criteria
- AC-1: Given [context], when [action], then [result]
## Technical Design
[Architecture, API changes, database changes]
## Test Plan
- [ ] Unit tests for [component]
- [ ] Integration tests for [flow]
spec-type: agent）# [SPEC-ID] Agent: [Role Name]
<!-- spec-type: agent -->
<!-- agent-id auto-referenced by feature SPECs -->
## Role Definition
- **Role**: [Agent Name]
- **Responsibility**: [One sentence]
- **Autonomy Level**: L[1-5] (per DEC-065)
## Capability Scope
**Owns:**
- [Capability 1]
- [Capability 2]
**Does NOT own:**
- [Explicit exclusion]
## Interface Contract
### Input
| Message Type | Required Fields | Optional Fields |
|---|---|---|
| [Type] | [fields] | [fields] |
### Output
| Artifact Type | Success Condition | Failure Condition |
|---|---|---|
| [Type] | [condition] | [condition] |
## Agent Interactions
- **Upstream**: [Who calls this agent]
- **Downstream**: [Who this agent calls]
- **Parallel**: [Agents working alongside]
## Related Feature SPECs
- [SPEC-NNN] — [This agent's role in that spec]
#### Scenario:（h4 標題）修改現有規格時，使用 delta 區段：
| 操作 | 說明（英） | 說明 |
|---|---|---|
## ADDED Requirements | New capabilities | 新增功能 |
## MODIFIED Requirements | Changed behavior | 修改行為 |
## REMOVED Requirements | Deprecated features | 移除功能 |
## RENAMED Requirements | Name changes | 重新命名 |
/sdd - Interactive spec creation wizard | 互動式規格建立精靈
/sdd auth-flow - Create spec for specific feature | 為特定功能建立規格
/sdd review - Review existing specs | 審查現有規格
/sdd --sync-check - Check sync status | 檢查同步狀態
/sdd 完成後，AI 助手應建議：
規格文件已建立。建議下一步 / Specification document created. Suggested next steps:
- 執行
/derive從規格推導測試工件 ⭐ Recommended / 推薦 — Derive test artifacts from spec- 執行
/derive bdd僅推導 BDD 場景 — Derive BDD scenarios only- 執行
/derive tdd僅推導 TDD 骨架 — Derive TDD skeletons only- 審查 AC 完整性，確保所有驗收條件可測試 — Review AC completeness
- 檢查 UDS 規範覆蓋率 → 執行
/audit --patterns— Check UDS standard coverage → Run/audit --patterns
完整的 AI 行為定義請參閱對應的命令文件：
/sddFor complete AI agent behavior definition, see the corresponding command file:
/sdd