Auto Research

Turns an ambiguous research or engineering task into a confirmed plan, maintains durable state in ./auto_research, advances work through explicit checkpoints, and validates progress against agreed success criteria.

Core Rules

• Treat /autoresearch <TaskDescription> as the workflow trigger, not as a shell command.
• Do not rely only on conversation memory for critical facts.
• Persist goals, plans, findings, decisions, validation status, blockers, and handoff notes under ./auto_research.
• Reread persistent state before every major step.
• Ask the user to confirm unclear goals, scope changes, architectural decisions, destructive actions, and git commits.
• Continue iterating until the Definition of Done is satisfied, the task is blocked, or the user stops the workflow.
• Use git commits only at meaningful checkpoints and only after explicit user authorization unless the session contract pre-approves checkpoint commits.

State Files