Ported from oh-my-codex autoresearch. OMX runtime conventions ($macro invocation, omx CLI, .omx/ state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list, .workbuddy/memory).

Autoresearch

Autoresearch is a skill-first, stateful research loop. It keeps the useful measured-research loop, but runs as a native WorkBuddy workflow (task list + .omw/ artifacts) instead of a direct CLI or tmux launch surface.

Boundary with planning research

Use autoresearch when the research output itself is a bounded deliverable that must pass an explicit validator. Do not recommend it for ordinary pre-planning docs lookup or general best-practice checks; use the research skill for that. If autoresearch is intentionally run before architecture planning, its approved artifact should feed evidence into ralplan; it should not become a final architecture/component unless the user explicitly asks for ongoing research automation.

Use when

• You want a persistent research loop.
• The task should keep nudging until explicit validation evidence exists.
• You want init-time choice between script validation and prompt+architect validation.

Do not use when