doe-plan

⚙️ Configuration

This public edition is an MCP-recommended skill. By default, use PatSnap MCP for patent and literature retrieval before entering the DOE pipeline.

Complete PatSnap MCP Setup first.

Recommended tool access:

- patsnap_search - patsnap_fetch

If the user already provides search_input.json, fetch_manifest.json, evidence_catalog.json, or other readable evidence files, continue with the current pipeline. If there is neither MCP access nor evidence input, stop at setup guidance.

🔒 Constraints

Validate outputs by stage:

evidence_catalog.json

- gates.status should be ready

factor_hypotheses.json

- summary.status should be ready - enough design_ready_factors should exist

doe_design.json

- must contain design_type, selection_rationale, runs[], and analysis_plan[]

run_sheet.csv

- must contain run_order, run_id, replicate, and per-factor _actual / _coded columns

doe_plan.md

- its title and section structure must match the six-section contract in references/output-contract.md

If any stage fails validation, do not cover the gap by pushing ahead to later stages.