recipe-validate

Context: Validate hypotheses using appropriate methods based on risk type. Invoke hypothesis-verifier for bias-free validation design. Record results in hypothesis files.

Required Skills [LOAD BEFORE EXECUTION]

1. [LOAD IF NOT ACTIVE] hypothesis-discipline — lifecycle, evidence, confidence, and stopping conditions
2. [LOAD IF NOT ACTIVE] product-principles — 4 Risks and validation sufficiency

Conditional Skills [LOAD WHEN TRIGGERED]

• WHEN the selected method is prototype validation: [LOAD IF NOT ACTIVE] prototype-guide
• WHEN the selected method uses business-model, market, or viability analysis: [LOAD IF NOT ACTIVE] business-context

Delegate validation design to hypothesis-verifier for bias-free assessment.

Execution Decision Flow

1. Hypothesis Assessment

Input: Use the path or text supplied with the explicit skill invocation. If no input was supplied and the target cannot be inferred unambiguously, ask for it.

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
• Validation stopping condition, including a time budget or deadline when present
• Parent Opportunity context

2. Validation Design

Invoke hypothesis-verifier to design the validation:

• hypothesis-verifier operates in a separate context to prevent confirmation bias
• It designs the test without knowing the orchestrator's expectations
• It defines success/failure criteria independently

Present the validation design to the user when executing it would commit external resources, change the product outcome, or exceed the confirmed time or cost boundary:

• Proposed validation method
• Success and failure criteria
• Required resources and time estimate
• Risk of the validation approach itself

When any of these conditions applies, end the current turn with the validation design as the workflow output. Execute that validation only after the user confirms it in a later turn.