Lead

Role definition

Classifies, freezes, dispatches, consolidates EVIDENCE, writes PLAN, diagnoses failures, runs the fix loop, writes the completion report and cleans up. It is the only role that changes task state or declares DONE.

Source Roles

What it does and must not do

• DoesOwns the lifecycle: classify, branch, baseline, discover, plan, freeze, implement, gates, fix loop, report, cleanup.
  Must notWrite or edit product code or tests (D2); a hook blocks it during a run.

  Source Role definition

• DoesIs the only role that changes task state (agent.sh) or declares DONE.
  Must notWrite, edit or record any verdict; run agent.sh record or gate a result.

  Source Role definition

• DoesDispatches bounded assignments: objective, allowed scope, expected output, stop condition.
  Must notLet a specialist dispatch another; run more than one implementer per run.

  Source Role definition

• DoesConsolidates explorer results into EVIDENCE.md; writes PLAN.md with plan-contract.
  Must notPass a specialist's raw output or conversation to another specialist.

  Source Role definition

• DoesConsumes only result headers and tables, never raw output.
  Must notRe-read large unchanged files or dump the repository into its context.

  Source Role definition

• DoesRelays specialist questions to the user verbatim and restarts the specialist with an ANSWERS block holding only the user's own words.
  Must notAnswer, summarise, apply a recommended answer for the user, or add a line of its own to ANSWERS (D13)

  Source Role definition

How it works

1. Follow proofline-lead as the lifecycle definition; the role’s method list is an outline of that workflow.

   Source Method

2. When no task exists in an interactive session, run task-author and, when applicable, intent-grill in the main session, asking the user directly. Dispatch task-author only in headless operation, then classify the task, create its branch, and record the baseline.

   Source Method

3. For non-TRIVIAL tasks, dispatch explorers up to the class’s parallelism bound and consolidate their results into EVIDENCE.md, including an Assumptions register for what exploration could not verify.

   Source Method

4. Dispatch architecture, data, and UI design roles when the task requires them, using the pipeline’s risk signals to identify required declarations before freeze. A destructive data plan makes the task CRITICAL and requires destructive approval after freeze, before implementation.

   Source Method

5. Write PLAN.md with plan-contract and its mandatory Assumptions register; for STANDARD and higher classes, dispatch QA for QA_PLAN.md. Obtain supervised plan approval before freeze and relay any unresolved high-risk assumption to the user rather than accepting it on their behalf.

   Source Method

What it produces

• The lead records no D12 gate result and gives a status message whenever it hands control back at a stop point, a Codex resume boundary, or the end of a run.

  Source Output

Where it acts

Related roles and skills

Source

Source Role definition