Research, build, and review in one reusable recipe

The recipe runs Research at ultracode effort, Codex at high effort, and Reviewer at high effort. Research documents the relevant codebase, risks, viable approaches, and recommendation before Codex implements. Reviewer then checks the implementation against the same acceptance criteria.

• Research: read-only findings and recommended approach
• Codex: focused implementation and verification
• Reviewer: correctness, regressions, edge cases, and missing tests

Define the intended user or system outcome, relevant code paths and dependencies, known constraints, exclusions, observable acceptance criteria, and the checks required before review. The later steps inherit that context instead of relying on an informal chat summary.

Review the research recommendation before treating it as the implementation plan. After the coding step, inspect the branch, diff, available checks and preview, then resolve the Reviewer's findings before a human approves the merge.