elaborate

§ 01 · purpose

Purpose

Turns one phase's contract-level "what to change" into the *actual code to apply* (paste-ready blocks grounded in the current tree), without redesigning the phase or touching any sibling's files. Dispatched once per phase in parallel after synthesize; the stitch-elaborations program (0 LLM calls) splices the results back, and the code gate grades the spliced plan.

§ 02 · when to use

When to use it

• Dispatched once per phase by the build pipeline's elaborate fanout, after the plan clears its gate.
• A phase's Changes name files and symbols but not yet the code implement should apply.
• Not standalone. The per-phase docs only matter once the splice folds them back into the plan.
• Prefer implement directly when the plan's phases already embed elaborated code. Re-elaborating a code-bearing plan adds nothing.

§ 03 · inputs

Inputs

plan + phase name

A missing path or unparseable Phase N is a dispatch error, not a failing phase. All other phases belong to sibling lanes.

§ 04 · outputs

Outputs

§ 05 · key steps

Key steps

1. 01 Read the whole plan, own one phase Why: The ## Synthesis Notes carry the reconciled cross-phase seams. Sibling phases' interfaces must be referenced by the shape synthesize already fixed. Skimming them is required precisely so their code is never rewritten here.
2. 02 Ground every change in the current tree Why: The plan may have been written against a slightly older state. The emitted code anchors to the signatures, imports, and style that are actually there now, so implement can apply it without guessing.
3. 03 Emit concrete, paste-ready code blocks per file Why: Prose hand-waving ("handle appropriately", "etc.") is exactly what the code gate's actionability dimension fails. Each block is the full function or the exact edit.
4. 04 Carry the phase's Success Criteria intact Why: The criteria are the contract validate runs later. A check may be tightened where the code makes it more concrete, but dropping or weakening one breaks downstream verification.
5. 05 Preserve the verbatim phase heading Why: The heading is the splice anchor. The stitch-elaborations program swaps the plan's section by exact phase number and title, so a renamed heading breaks the deterministic fold.
6. 06 Resolve ambiguity yourself, on the record Why: N lanes run concurrently, so the skill is non-interactive. A genuine blocker gets the most defensible call, recorded under ## Notes / Deferred, and the grade panel catches a bad one.

§ 06 · related skills

Related skills