用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill dev-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 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 | dev-workflow |
| scope | universal |
| description | [UDS] Guide for mapping software development phases to UDS commands and features |
| allowed-tools | Read, Grep, Glob |
| argument-hint | [phase name | scenario | 階段名稱 | 場景] |
Language: English | 繁體中文
Map your current software development phase to the right UDS commands and skills. Get instant guidance on which tools to use at each stage of development.
將你目前的軟體開發階段對應到正確的 UDS 指令與技能。即時了解在開發的每個階段應該使用哪些工具。
Related: To choose or switch between development methodologies (SDD, BDD, TDD), use
/methodologyinstead.相關：如需選擇或切換開發方法論（SDD、BDD、TDD），請改用
/methodology。
I. Planning ──► II. Testing Design ──► III. Implementation ──► IV. Quality Gates
需求設計 測試驅動開發 程式碼開發 品質保證
V. Release ──► VI. Documentation ──► VII. Standards ──► VIII. Advanced
版本提交 文件與架構 工具與標準 進階分析
| Phase | UDS Commands | Purpose | 用途 |
|---|---|---|---|
| I. Planning & Design | /brainstorm /requirement /sdd /reverse | Requirements, specs, reverse engineering | 需求、規格、逆向工程 |
| II. Test-Driven Development | /bdd /atdd /tdd /coverage /derive | Design tests before code | 先寫測試再寫程式 |
| III. Implementation | /refactor /reverse | Write and improve code | 撰寫與改善程式碼 |
| IV. Quality Gates | /checkin /code-review | Pre-commit and code review | 提交前檢查與程式碼審查 |
| V. Release & Commit | /commit /changelog /release | Version, commit, publish | 版本、提交、發布 |
| VI. Documentation | /docs /docgen /struct | Docs and project structure | 文件與專案結構 |
| VII. Tools & Standards | /discover /testing /guide /git | Reference guides | 參考指南 |
| VIII. Advanced Analysis | /methodology | Cross-methodology workflows | 跨方法論工作流程 |
Recommended flow for building a new feature from scratch:
從零開始建立新功能的推薦流程：
/brainstorm → /requirement → /sdd → /derive → /tdd → /checkin → /commit
| Step | Command | What to Do | 做什麼 |
|---|---|---|---|
| 1 | /brainstorm | Explore ideas and approaches | 探索想法與方法 |
| 2 | /requirement | Write user stories (INVEST criteria) | 撰寫使用者故事 |
| 3 | /sdd | Create specification document | 建立規格文件 |
| 4 | /derive | Generate test skeletons from spec | 從規格產生測試骨架 |
| 5 | /tdd | Implement with Red-Green-Refactor | 用紅綠重構循環實作 |
| 6 | /checkin | Verify quality gates | 驗證品質關卡 |
| 7 | /commit | Create conventional commit | 建立規範化提交 |
Recommended flow for fixing bugs in existing code:
修復既有程式碼錯誤的推薦流程：
/discover → /reverse → /tdd → /checkin → /commit
| Step | Command | What to Do | 做什麼 |
|---|---|---|---|
| 1 | /discover | Assess affected area health | 評估受影響區域健康度 |
| 2 | /reverse | Understand existing code structure | 理解現有程式碼結構 |
| 3 | /tdd | Write failing test, then fix | 先寫失敗測試，再修復 |
| 4 | /checkin | Verify quality gates | 驗證品質關卡 |
| 5 | /commit | Create conventional commit | 建立規範化提交 |
Recommended flow for code refactoring:
程式碼重構的推薦流程：
/discover → /reverse → /coverage → /refactor → /checkin → /commit
| Step | Command | What to Do | 做什麼 |
|---|---|---|---|
| 1 | /discover | Assess project health and risks | 評估專案健康度與風險 |
| 2 | /reverse | Document current behavior | 記錄目前行為 |
| 3 | /coverage | Ensure test safety net exists | 確保測試安全網存在 |
| 4 | /refactor | Apply refactoring strategies | 套用重構策略 |
| 5 | /checkin | Verify quality gates | 驗證品質關卡 |
| 6 | /commit | Create conventional commit | 建立規範化提交 |
/dev-workflow # Show full phase overview
/dev-workflow planning # Get Phase I guidance
/dev-workflow testing # Get Phase II guidance
/dev-workflow new-feature # Get new feature workflow
/dev-workflow bug-fix # Get bug fix workflow
/dev-workflow refactoring # Get refactoring workflow
| Argument | Description | 說明 |
|---|---|---|
planning | Phase I: Planning & Design | 需求與設計 |
testing | Phase II: Test-Driven Development | 測試驅動開發 |
implementation | Phase III: Implementation | 程式碼開發 |
quality | Phase IV: Quality Gates | 品質保證 |
release | Phase V: Release & Commit | 版本與提交 |
docs | Phase VI: Documentation | 文件與架構 |
standards | Phase VII: Tools & Standards | 工具與標準 |
advanced | Phase VIII: Advanced Analysis | 進階系統分析 |
new-feature | Scenario: New feature workflow | 場景：新功能開發 |
bug-fix | Scenario: Bug fix workflow | 場景：修復錯誤 |
refactoring | Scenario: Refactoring workflow | 場景：重構 |
When invoked:
The skill reads from workflow-phases.md for detailed phase information.
呼叫時：
After /dev-workflow completes, the AI assistant should suggest based on user's situation:
工作流程已顯示。建議下一步 / Workflow displayed. Suggested next steps:
- 新功能開發 → 執行
/brainstorm探索想法 — New feature → Run/brainstormto explore ideas- 修復錯誤 → 執行
/discover評估受影響區域 — Bug fix → Run/discoverto assess affected area- 重構程式碼 → 執行
/discover評估健康度 — Refactoring → Run/discoverto assess health- 遺留系統 → 執行
/reverse進行系統考古 — Legacy system → Run/reversefor system archeology
| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2026-03-04 | Initial: 8 development phases, 3 scenarios, phase-based navigation |
This skill is released under CC BY 4.0.
Source: universal-dev-standards