What problem does it solve?
Autoresearch solves the problem of getting reliable, step-by-step improvement for one mission without losing control over evaluation quality or run duration.
Core Features & Use Cases
- Stateful single-mission improvement loop: Runs one mission at a time, repeatedly applying experiment cycles until an explicit stop condition is met.
- Strict evaluator contract & durable artifacts: Requires evaluator output as JSON including a boolean
pass (and optional numeric score), and persists iteration-by-iteration logs and decisions under .omc/autoresearch/<mission-slug>/.
- Bounded runtime with predictable stopping: Stops primarily on
max-runtime, while also supporting explicit terminal conditions and cancellation, so runs don’t drift indefinitely.
- Use Case: When you have a prepared mission and evaluator from
/deep-interview --autoresearch, use this skill to continuously refine outputs based on pass/fail evaluation and keep a human-readable decision log.
Quick Start
In your Claude Code session, run /deep-interview --autoresearch first, then activate autoresearch with your mission so it begins iterating and writing evaluation JSON plus markdown decision logs.