name: claude-hook-validation description: > Validation phase for hook automation rule development. Use when planning, designing, building, testing, validating, or refining a hook automation rule as it moves through a full delivery lifecycle. Triggers include drafting the hook spec, locking contracts, wiring runtime placement, scoring quality, running live scenarios, or choosing the right re-entry point after a failure.

Hook Validation

Score quality, discoverability, safety, and portability before the rule is considered release-ready.

Intent Router

Load reference files on demand only when the corresponding topic is active:

• references/quality-rubric.md — Load when scoring safety, observability, and portability

Quick Start

[ ] Capture the current hook spec
[ ] Complete the required outputs for this phase
[ ] Record evidence for the gate
[ ] Hand off the evidence to the next phase

Phase Workflow

Start from the current hook spec and tighten only the decisions owned by this phase. Work forward until the gate is satisfied, then hand the evidence to the next phase in the family. Keep the workflow description portable even when the runtime wiring is specific to one environment.

Example Evidence

| Criterion | Score | Notes |
|---|---|---|
| Discoverability | PASS | |
| Safety | PASS | |
| Observability | PASS | |
| Portability | PASS | |

Gate

Require H04 Safety to PASS before approving the hook automation rule.

Safety Notes

A rule that fails safety or portability validation must loop back before any live rollout.

Resource Index