How to write an agent definition for this project. Use when the user asks to write, add, create, or redesign an agent — even if they don't say 'agent file' explicitly. Also use when deciding how an agent prompt should be structured, what sections it needs, or how to split responsibilities between agents and orchestrator skills. Trigger on: 'write an agent', 'create an agent', 'design the agent', 'update the agent', 'agent prompt for X'.
Exit rubric for the Experimental Setup Module. Load when the Main Agent needs to determine whether EXPERIMENT_SETUP.md is complete enough to hand off to Phase 1 (Method Design). Returns PASS or NEEDS-REWORK with specific failing criteria listed. Evaluates structural completeness and verification quality only — not whether the chosen baselines are the 'right' ones (that judgment belongs to the Architect).
Main Agent orchestration skill for the Experimental Setup Module — the pre-Phase-1 step that audits which datasets, metrics, baselines, LLMs, and reusable code are actually available for the idea. Load when Loop 2 has passed and EXPERIMENT_SETUP.md has not yet been produced, or when the previous audit flagged thin coverage and the Main Agent needs to drive a supplementary scout search and re-audit. Drives the auditor → exit-check → optional supplement cycle and hands off to Phase 1 (Method Design).
Exit rubric for Loop 1 (ideation refinement). Load when the Main Agent needs to determine whether the current IDEA.md is sufficiently developed to proceed to Loop 2 stress testing. Returns PASS or FAIL with specific failing criteria listed. Evaluates development completeness only — not idea quality, novelty, or validity. Those are Loop 2's job.
Main Agent orchestration skill for Loop 1 (ideation refinement). Load when entering or re-entering the idea refinement loop — whether starting fresh with a new idea, responding to user intervention during ideation, or rolling back from Loop 2 after the Tester returned attack points. Drives the Scout → Refiner → exit-check cycle and controls loop termination.
Exit rubric for Loop 2 (stress testing). Load when the Main Agent needs to determine whether the current idea has survived adversarial scrutiny sufficiently to proceed to the Experimental Setup Module. Evaluates the latest Tester report against four criteria. Returns PASS or FAIL with specific failing criteria listed. Evaluates resilience to attack only — not development completeness (that was Loop 1's job).
Main Agent orchestration skill for Loop 2 (stress testing). Load when Loop 1 has passed and the idea is ready for adversarial evaluation, or when re-entering Loop 2 after a Loop 1 retreat fixed the Tester's attack points. Drives the Tester → exit-check → retreat-or-proceed cycle. Controls loop termination and user notification.
Exit rubric for Phase 1 (Method Design). Load after the Architect ↔ Confirmer loop has converged (Confirmer Verdict = ALL CLEAR) and the Main Agent needs to determine whether the confirmed spec is complete enough to hand off to Phase 2 (Small-Scale Verification). Returns PASS or NEEDS-REWORK with specific failing criteria listed. Evaluates structural completeness and dual-anchor alignment only — semantic judgments (clarity, quality) are the Confirmer's responsibility upstream.