Skip to content

Codex HELIX Recipe

Use this recipe when Codex is the implementation agent and HELIX supplies the planning, alignment, and handoff contract. DDx is not required.

What the runtime must provide

Codex, or the environment around it, must provide:

  • Explicit working directory and file scope.
  • Clear instructions about which artifacts govern the task.
  • A way to apply direct file edits.
  • A final response that names changed files and unresolved follow-up.
  • Optional validation commands, only when the human asks Codex to run them.

Codex works best when the handoff is narrow. Treat the prompt as the execution boundary.

Recipe 1: create the first artifact stack

Ask Codex to create only the artifact files, not implementation code.

Prompt:

In <repo>, create a minimal HELIX artifact stack for <project>. Write only these
files: <artifact paths>. Use product vision, PRD, feature spec, design note, and
implementation handoff. Keep unknowns explicit. Do not run tests. Do not edit
code. Final response: exact files changed.

Human edit pass:

  • Tighten the product facts and non-goals.
  • Replace inferred requirements with explicit decisions.
  • Add real constraints such as compliance, deployment, data ownership, or supported platforms.
  • Remove implementation details that are not justified by upstream artifacts.

Recipe 2: run the first alignment pass

Prompt:

Run a HELIX alignment review for <artifact paths>. Findings first. For each
finding, cite the downstream artifact, the governing upstream artifact, and the
specific correction needed. Do not edit files until I approve. Do not inspect or
modify unrelated areas.

After approving corrections:

Apply the approved alignment edits only to <artifact paths>. Keep the authority
order intact. Do not touch implementation files, generated references, tracker
state, or site navigation.

Recipe 3: create the first implementation handoff

Prompt:

Create a HELIX implementation handoff for <feature>. Use the aligned artifacts
as authority. Include allowed write scope, files to avoid, acceptance criteria,
validation expectations, and final-response requirements. Do not implement.

Implementation prompt:

You are implementing this HELIX handoff in <repo>. Own only this write scope:
<paths>. Avoid these paths: <paths>. Read each required file at most once before
editing. Do not run tests unless explicitly asked. Do not revert or overwrite
other workers' changes. Final response: summary and exact files changed.

This prompt shape makes the runtime responsibilities explicit: Codex receives authority, scope, validation policy, and evidence requirements from the human instead of from a DDx queue.