← ClaudeAtlas

dhpk-execution-policylisted

Execution-policy router for dhpk software-engineering work. Use when choosing a task flow or OpenSpec route at kickoff, checking post-edit reviewer obligations, recovering from an anti-loop stop, or shaping a blocked/completion reply. Not for: substantial-change classification (use dhpk-adaptive-dev-workflow), an investigation already underway (use dhpk-root-cause-investigation), pure code tracing, or mid-workflow execution. Output: one next route plus the required gates and completion shape.
hmj1026/dhpk · ★ 2 · AI & Automation · score 71
Install: claude install-skill hmj1026/dhpk
# DHPK Execution Policy Read `${CLAUDE_PLUGIN_ROOT}/rules/execution-policy-kernel.md` first. It is the always-visible safety, authorization, dirty-worktree, route-boundary, and completion contract. Then load only the reference required by the selected branch; the canonical policy is the single source of truth and this skill is a route index rather than an unconditional second read: - classification or OpenSpec routing → `${CLAUDE_PLUGIN_ROOT}/rules/execution-policy.md` §Change classification & OpenSpec routing; - feature or bug delivery loop → `./references/delivery-loop-gate.md`; - implementation dispatch → `./references/implementation-dispatch.md`; - reviewer or sentinel closure → `./references/review-gate-mechanics.md`; - retry or anti-loop → `./references/anti-loop.md`; - explicit policy audit or an uncovered rule → the project policy, then the plugin fallback `${CLAUDE_PLUGIN_ROOT}/rules/execution-policy.md`. This skill supplies routing and load-on-demand pointers; it does not copy normative tables or require the full policy for every invocation. The implementation posture is **decide → dispatch → verify** when orchestration dispatch is enabled. Inline work is the policy's small, unambiguous exception, not a reason to bypass its worker or review gates. ## When NOT to Use - A substantial change needs workflow classification, required artifacts, or readiness gates → use `dhpk-adaptive-dev-workflow`. - A root-cause investigation is already underway → use `dhpk-root