recipe-define

Context: Transform validated hypotheses into a reviewed PRD that preserves product evidence, exposes remaining risk, and can be consumed by downstream implementation workflows.

Orchestrator Definition

Execution Protocol:

1. Required specialist execution: Invoking this recipe is the user's explicit instruction and authorization to execute every named specialist whose condition applies. Execute each applicable Agent call with its declared subagent_type when its prerequisites are met and continue from its returned result; equivalent orchestrator work does not complete that step
2. Exact specialist handoff: The complete Agent prompt consists of all and only the applicable canonical field: value entries declared by the specialist's Input Contract. Copy each value unchanged from its authoritative source; serialize path fields as path strings so the specialist reads referenced artifacts directly
3. Complete finding coverage: Record one evidence-backed disposition for every reviewer issue before correction or progression
4. Follow the definition flow below and stop at the final user approval gate

Workflow

Assess readiness → draft the PRD → obtain independent review → resolve each finding → request final user approval.

Execution Decision Flow

1. Readiness Assessment

Input: $ARGUMENTS

Read the relevant Opportunity and hypothesis files. For each hypothesis included in the PRD:

1. Check confidence evidence using prd-standards references/user-story-guide.md
2. Assess cost × risk × reversibility
3. Determine validated enough or needs more validation
4. Keep proceed, further validation, scope reduction, and explicit residual risk as valid results; choose further validation only when its evidence can change readiness or scope

Use product-principles references/mvp-definition.md to determine the smallest included capability set, explicit exclusions, and observable proof. A ranking aid is optional and applies only when credible candidates remain tied after direct boundary analysis.