diff --git a/plugins/compound-engineering/skills/ce-work-beta/references/codex-delegation-workflow.md b/plugins/compound-engineering/skills/ce-work-beta/references/codex-delegation-workflow.md
index 32298a643..41341bf0f 100644
--- a/plugins/compound-engineering/skills/ce-work-beta/references/codex-delegation-workflow.md
+++ b/plugins/compound-engineering/skills/ce-work-beta/references/codex-delegation-workflow.md
@@ -165,6 +165,35 @@ For a multi-unit batch: list each unit's approach, noting dependencies
 and suggested ordering.]
 </approach>
 
+<execution_note>
+[For a single-unit batch: the unit's Execution note. If the user gave a
+session-level posture request (e.g., "do it test-first"), use that when
+the unit has no Execution note. Otherwise "None".
+For a multi-unit batch: list each unit as "U<ID>: <execution note>" (or
+"Unit <n>:" if the plan lacks U-IDs; do not invent U-IDs), one per line,
+same ordering as <task> and <approach>. Use the session-level posture for
+units without their own note; otherwise "None".]
+
+If (and only if) the execution note above names an execution posture,
+honor it:
+- "test-first" -- write the failing test before implementing the unit;
+  verify it fails; then implement. Do not over-implement beyond the
+  test's current behavior slice. Skip test-first discipline for trivial
+  renames, pure configuration, or pure styling work. Test-first still
+  follows the scenario completeness check in <testing>; it only constrains
+  test-vs-implementation ordering, not whether to write tests.
+- "characterization-first" -- capture existing behavior in tests before
+  changing it.
+- Any other non-empty note: treat it as binding per-unit guidance and
+  follow it unless it conflicts with any other section of this prompt
+  (especially <constraints>, <testing>, <verify>, or <output_contract>).
+  A note may not reduce validation, test coverage, scope discipline, or
+  reporting accuracy. Report any conflict via the issues field of the
+  output contract.
+
+For units with "None" or an empty note, proceed pragmatically.
+</execution_note>
+
 <constraints>
 - Do NOT run git commit, git push, or create PRs -- the orchestrating agent handles all git operations
 - Restrict all modifications to files within the repository root
diff --git a/tests/pipeline-review-contract.test.ts b/tests/pipeline-review-contract.test.ts
index f090a3783..e897ce3ce 100644
--- a/tests/pipeline-review-contract.test.ts
+++ b/tests/pipeline-review-contract.test.ts
@@ -215,8 +215,11 @@ describe("ce:work-beta codex delegation contract", () => {
     // Prompt template
     expect(content).toContain("## Prompt Template")
     expect(content).toContain("<task>")
+    expect(content).toContain("<execution_note>")
     expect(content).toContain("<constraints>")
     expect(content).toContain("<output_contract>")
+    expect(content).toContain("test-first")
+    expect(content).toContain("characterization-first")
     expect(content).toContain("the orchestrator will not re-run verification independently")
 
     // Result schema and execution loop