adaptive-dev-workflowlisted

Workflow router for substantial changes. Use when: a feature, bugfix, refactor, security, perf, or OpenSpec change needs classifying into Feature Delivery, Bug Investigation & Fix, or Lightweight Maintenance before heavy context loads. Not for tiny edits, investigation already underway, code review, or apply-ready OpenSpec tasks. Output: workflow classification + required artifacts + gate checklist.
hmj1026/dhpk · ★ 2 · AI & Automation · score 71

Install: claude install-skill hmj1026/dhpk

# Adaptive Dev Workflow ## Overview 先做 workflow 分流，再決定是否需要 profile、scope、work-item、gate 等前置資產。主檔只保留決策核心；分支細節由條件式 reference 提供。 ## When NOT to Use - `CLAUDE.md` Execution Policy 定義的 small change：直接 patch + `dhpk:code-reviewer` - root-cause 調查已在進行：改用 `bug-investigation` - 純架構或 module boundary 討論：改用 `software-architecture` - OpenSpec change 已 apply-ready：切去 `/opsx:apply` - 已進入 TDD 實作階段：改用 `tdd-guide` agent - 只做 code review：改用專用 review skill ## Core Principles 1. 先選 workflow type，再載入 heavy context。 2. 以 repo 權威規範（例如 `CLAUDE.md`、`AGENTS.md`）為 SSOT；本技能只補 workflow 缺口。 3. `Lightweight Maintenance` 只做 targeted verification；`Feature Delivery` / `Bug Investigation & Fix` 才建立 heavy artifacts。 4. 缺件時回報 blocker；apply-ready 時直接 hand off，不重跑前置。 ## Fast-worker invocation context When `/dhpk:do` supplies `WORKER_OVERRIDE`, preserve that exact invocation-only value through hand-off to `dhpk:bug-fix` / `dhpk:feature-dev`. Before the first mechanical dispatch, consume it with the shared selector at `scripts/fast-worker-selector.js` using `--backend "$WORKER_OVERRIDE"`. `unset` means omit the explicit backend argument and let the selector apply userConfig/default precedence; never infer it from cleaned task text. ## Codex mode (opt-in) 預設是 codex-free：不呼叫 `mcp__codex__*`，也不需要 Codex CLI/MCP。只有傳入 `--codex` 才載入 [references/codex-mode.md](references/codex-mode.md) 取得 phase mapping、fallback 與下游 `--codex` 規則。 ## Workflow Decision ### Feature Delivery 新能力、行為變更、跨模組契約調整，或需要完整前置治理的變更。 ### Bug