council.md

You are the chair of a 3-model code review council. Your job: synthesize findings from three reviewers into an implementable fix program for Codex.

Context: We have six markdown files produced by three different models:

• a-review.md, a-fixes.md
• b-review.md, b-fixes.md
• c-review.md, c-fixes.md

Task:

1. Read all six files. Build a unified issue list.
2. Deduplicate + cluster issues into “Major Things” (epics). Rule of thumb: one epic if it is cross-cutting, risky, architectural, or likely touches >3 files. Otherwise group small items.
3. For each issue, assign:

• Severity (P0/P1/P2)
• Confidence (high/med/low) based on evidence and cross-model agreement
• Effort (S/M/L)
• A short acceptance test (how we know it’s fixed)

4. Resolve conflicts:

• If models disagree, call it out explicitly.
• Prefer evidence-backed claims; quote or reference the exact bullet/section from the source markdowns.

Deliverables (STRICT):

Output a single “Codex master prompt” that tells Codex to:

• create/ensure AGENTS.md and PLANS.md exist (if missing) with an ExecPlan workflow
• write one ExecPlan per epic into EXECPLAN-<EPIC_SLUG>.md following the PLANS.md skeleton
• then execute those ExecPlans sequentially, updating Progress/Decision Log as it goes
• keep changes safe: branch, small commits, run tests, avoid breaking public APIs unless explicitly required
• stop only when all acceptance criteria are met or a blocker is proven

ExecPlan requirements (follow exactly):

• Must be self-contained and novice-guiding.
• Must include the required sections: Purpose/Big Picture, Progress, Surprises & Discoveries, Decision Log, Outcomes & Retrospective, Context and Orientation, Plan of Work, Concrete Steps, Validation and Acceptance, Idempotence and Recovery, Artifacts and Notes, Interfaces and Dependencies.
• Use prose-first.
• Checklists only in Progress.
• Include concrete commands (with working directory) for build/test/lint and brief expected outputs.

Formatting constraints:

• First output: “CODEX_MASTER_PROMPT” (a single code block).
• Then output: “EXECPLANS” with one code block per plan, labeled with the target filepath on the first line.

Assumptions:

• Repo uses git.
• We want high-signal fixes over style churn.
• Prefer adding tests when fixing bugs/regressions.

Now proceed.