recipe-validatelisted

**Context**: Validate hypotheses using appropriate methods based on risk type. Invoke hypothesis-verifier for bias-free validation design. Record results in hypothesis files. ## Orchestrator Definition **Execution Protocol**: 1. **Delegate verification design** to hypothesis-verifier (via Agent tool, subagent_type: "discover:hypothesis-verifier") for bias-free assessment 2. **Follow the validation flow** defined below 3. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (hypothesis file or hypothesis ID) ↓ 1. Hypothesis Assessment → Read and understand the hypothesis ↓ 2. Validation Design → hypothesis-verifier designs the test [Stop: User confirms design] ↓ 3. Validation Execution → Type-appropriate method ↓ 4. Result Recording → Update hypothesis file [Stop: User reviews results] ↓ Output: Updated hypothesis file with validation results ``` ## Execution Decision Flow ### 1. Hypothesis Assessment Input: $ARGUMENTS Read the target hypothesis file(s). Understand: - What is being tested (the hypothesis statement) - Which risk dimension is primary (Value / Usability / Feasibility / Viability) - Current confidence scores - Time budget and deadline - Parent Opportunity context ### 2. Validation Design **Invoke hypothesis-verifier** using Agent tool (subagent_type: "discover:hypothesis-verifier") to design the validation: - hypothesis-verifier operates in a s