← ClaudeAtlas

hypothesis-simulation-reviewlisted

Simulate the hypothesis mechanism and identify failure scenarios.
panjose/Co-Scientist · ★ 4 · Code & Development · score 77
Install: claude install-skill panjose/Co-Scientist
# hypothesis-simulation-review Goal: - Simulate the hypothesis mechanism and identify failure scenarios. Inputs: - `research_plan/RESEARCH_PLAN.json` - `hypotheses/<id>/HYPOTHESIS.json` - optional prior review artifacts for calibration Outputs: - `hypotheses/<id>/REVIEW/SIMULATION_REVIEW.json` Context Loading: - Read `research_plan/RESEARCH_PLAN.json`. - Read `hypotheses/<id>/HYPOTHESIS.json`. - Use prior reviews only as hints for likely weak spots; the simulation should still be an independent walk-through of the mechanism and validation path. Execution Prompt Contract: - System Intent: - You are mentally simulating the hypothesis mechanism and proposed validation path step by step. - Required Reasoning Focus: - Break the mechanism into an ordered process. - Identify where the process could fail and why. - Distinguish inherent failures from contingent implementation issues where possible. - Prioritize likely and fundamental failure scenarios over edge cases. - Do Not Do: - Do not generate abstract critique without a concrete simulated step. - Do not flood the artifact with low-value edge cases. - Do not replace the structured review with narrative prose. - Review Quality Floor: - A `status = completed` simulation review must include concrete mechanism or validation steps and concrete failure scenarios. - Steps must name hypothesis-specific materials, mechanisms, measurements, conditions, controls, or decision points. - Do not use placeholder s