build-loop-auto-research

Use when the user wants to analyze prior Codex archived sessions to infer request, authorization, verification, and handoff patterns and use those patterns to improve future build workflows.

Autonomous metric-driven optimization loop. Constrained scope + mechanical metric + git commit/revert + fast iteration. Use for build optimization, test coverage, prompt tuning, doc quality, or runtime performance.

Use for significant multi-step research-and-planning work that benefits from a phase-based loop, orchestration, parallel subagents, validation, iteration, and context continuity.

Use when resuming work in a project that may already have a build-loop-auto-research context snapshot or registry fallback trailhead.

Use when work is about to span sessions, risk compaction, or switch contexts and you want a bookmark-style local snapshot of the current project state.

Use before repeating an investigation, debugging loop, or multi-iteration fix so Codex can check modular lessons learned and decide whether a known fix or likely match already exists.

Use when the user has a rough request, draft plan, or prompt that needs to be tightened into a clearer, simpler, more verifiable build brief.

Use when a user wants a research-backed build packet, a concise build investigation, a history-pattern analysis, or a brief/prompt optimization pass.

Use when the user wants a research packet plus a decision-complete implementation plan for a product, feature, algorithm, prompt, bugfix, or refactor, but does not need the full explicit phase-by-phase build loop narration.