dhpk-adaptive-dev-workflowlisted

# Adaptive Dev Workflow ## Overview 先做 workflow 分流，再決定是否需要 profile、scope、work-item、gate 等前置資產。 主檔只保留決策核心；分支細節由條件式 reference 提供。 ## When NOT to Use - `CLAUDE.md` Execution Policy 定義的 small change：直接 patch + the designated code-reviewer agent - Root-cause 調查已在進行：改用 `dhpk-root-cause-investigation` - 純架構或 module boundary 討論：改用 `dhpk-module-design` - 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，不重跑前置。 5. Feature and Bug work stay on their selected branch through implementation; shared test, freshness, review, and handoff rules live in the execution-policy delivery-loop reference。 6. Follow `rules/execution-policy.md` §Orchestration decision policy: unresolved non-trivial choices require the read-only reasoner contract before a writer; OpenSpec applies with two or more unchecked tasks require a planner, while one clear task records `planner=skipped`. ## Wayfinder checkpoint When the destination is unclear and work spans sessions or agents, load [workflow-analysis](references/workflow-analysis.md) and record its bounded decision-map fields before implementation; clear one-session work skips it. ## Fast-worker in