dhpk-execution-checklistlisted

# Execution checklist Use this gate at the wrap-up boundary for substantive edits or a pending commit. It has three stages: Per-reply, Conditional, and Task-end. Record skips and blockers in the wrap-up reply; a quiet hook does not prove that a reviewer ran. > Source: the project's execution policy — project > `.claude/rules/execution-policy.md` if present, else > `${CLAUDE_PLUGIN_ROOT}/rules/execution-policy.md`. This skill carries the > long-form checklist so the policy rule itself stays index-sized. ## When NOT to Use - Trivial typo-only edits with no triggered safety surface. - Pure research / planning turns with no Edit/Write and no pending commit. ## Usage - **Load it at wrap-up** — after the final Edit/Write, before emitting the Conclusion, or before `smart-commit` when the change is already staged. - **Honour the reviewer dispatch model** — triage false positives, dispatch every surviving configured reviewer slot in one parallel batch, and record any triage-drop or self-accountable skip. ## Per-reply (check after a substantive Edit/Write or before a pending commit) Four boxes must clear: 1. **TDD pre-run** — Bug fix / feature that touches business logic: did `tdd-guide` (or the configured first agent in `review_agents`) run in the RED phase, writing the failing test first? Skip for pure docs / harness / hook edits. 2. **Final gate ran** — After the Edit/Write, every matching configured reviewer slot (the 7-slot default is defined by `review_