dhpk-execution-policylisted

# DHPK Execution Policy Default: execute directly, plan sparingly. Every code change ends with `→ [dr*] → code-reviewer`. `dr*` = database-reviewer (SQL) / security-reviewer (auth/crypto/money). Agent names above are the plugin defaults; projects override via `userConfig.review_agents`. ## Task modes | Task | Flow | |------|------| | Small change | inspect → patch | | Small bug (known cause) | inspect → tdd-guide RED → patch → tdd-guide verify | | Medium change | inspect → brief plan → tdd-guide → patch | | Bug (unknown cause) | bug-investigation skill → tdd-guide → patch | | New feature | tdd-guide → patch | | Architecture change | architect → tdd-guide → patch | `[OpenSpec?]` defaults to inline brief plan; use `/opsx:new` only when the user explicitly requests a spec-driven change. ## Skill priority order 1. `/opsx:*` when explicitly invoked 2. `bug-investigation` — triggers: investigate / trace / why / root cause 3. `tdd-guide` — feature/bugfix needing tests (pre-edit) 4. `architect` — cross-module design 5. `/code-review` — user-invoked; triggers `code-reviewer` on pending sentinel 6. Project-local skills win over same-name plugin skills; skip workflow skills for small direct edits. ## Mandatory post-edit steps ### Hook-enforced (sentinel-driven) The `post-edit-remind` hook writes sentinels per matching reviewer slot: | Sentinel | Agent (default name) | |---|---| | `.pending-review` | `code-reviewer` (always last) | | `.pending-db-review` | `database-reviewer`