What problem does it solve?
Running measured Autoresearch loops against Slate v2 requires consistent session state, correctness routing, and dashboard discipline that generic tooling does not provide, leading to lost packets and unmeasured regressions.
Core Features & Use Cases
- Slate v2 Loop Defaults: Pins the working directory to
.tmp/slate-v2, manages autoresearch.* session files, and enforces keep/discard decisions based on Slate correctness checks.
- Operator Routing: Routes short commands like continue, status, finalize, research, gate, and perfect to the correct specialized wrapper skill such as slate-ar-perf, slate-ar-gate, or slate-patch.
- Finalization Discipline: Runs preview-only finalization by default and requires explicit user approval before creating review branches, commits, or PRs.
- Use Case: A developer iterating on Slate v2 editor behavior invokes
slate-ar continue to resume a measured loop, review kept versus discarded packets, and get the next recommended packet without re-initializing state.
Quick Start
Ask the assistant to continue the current Slate v2 Autoresearch session and report status, baseline, and the next recommended packet.