Codex as a Disciplined Teammate

Lesson 2 · Context, boundaries, verification

© 2026 Jared Cluff · Labalicious · Lesson 2

Today’s outcome

  • Write an executable AI task brief
  • Investigate an unfamiliar codebase safely
  • Review a proposed diff and its tests
  • Preserve useful context as files and playbooks
© 2026 Jared Cluff · Labalicious · Lesson 2

Treat Codex like a capable new teammate

Give it:

  • desired outcome
  • relevant files and sources
  • scope and safety boundaries
  • completion bar

Then review its work like you would any teammate’s.

© 2026 Jared Cluff · Labalicious · Lesson 2

A strong task brief

Find why staff cannot send an inquiry update. Read these paths. Do not change files. Return: request path, cited evidence, likely hypotheses, open questions, and the smallest verification command.

Specific task. Bounded authority. Reviewable result.

© 2026 Jared Cluff · Labalicious · Lesson 2

Modern Codex workflow

Explore → plan → review → apply → verify

For unfamiliar or consequential work, ask for a plan first. Use repository instructions and current source files as durable context.

© 2026 Jared Cluff · Labalicious · Lesson 2

Demo

  1. Read AGENTS.md
  2. Trace a feature through UI, server, and test
  3. Ask for an investigation plan
  4. Verify every cited path
  5. Run an approved check
© 2026 Jared Cluff · Labalicious · Lesson 2

What Codex should say

  • “Here is the evidence I found.”
  • “This is an inference.”
  • “This requirement is ambiguous.”
  • “I need approval before changing…”

It should not pretend to know missing business rules.

© 2026 Jared Cluff · Labalicious · Lesson 2

Lab: Codebase Detective

Mission: investigate, do not rush a fix.

Deliver: task brief, verified repository map, tool result, and open question.

© 2026 Jared Cluff · Labalicious · Lesson 2

Diff review questions

  • Does the change match the acceptance criterion?
  • Is its scope small and reversible?
  • Would the test fail for the actual regression?
  • Did it leak data, broaden permissions, or hide a failure?
© 2026 Jared Cluff · Labalicious · Lesson 2

Durable context beats chat memory

Keep:

  • repository instructions
  • test commands
  • architectural notes
  • approved playbooks
  • evaluation cases
© 2026 Jared Cluff · Labalicious · Lesson 2

What takes an agent further?

Context: current requirements, files and examples.

Tools: actions the client can execute.

Reusable workflow: instructions and scripts for repeated jobs.

Feedback: tests, observed state and corrections.

© 2026 Jared Cluff · Labalicious · Lesson 2

Tools, MCP, and reusable skills

MCP connects an agent to external tools and context.

A skill packages a repeatable workflow with instructions and optional scripts/resources.

Account access and permissions determine what can run.

© 2026 Jared Cluff · Labalicious · Lesson 2

Let it execute an authorized task

Ask Codex to inspect, implement, run checks, diagnose failures, and iterate within the learner copy.

Give a clear stopping condition and review the result.

Use extra reasoning or parallel work when it improves measured outcomes.

© 2026 Jared Cluff · Labalicious · Lesson 2

Exit ticket

Write a task brief asking Codex to find, not fix, a suspected regression.

© 2026 Jared Cluff · Labalicious · Lesson 2

Ask which missing element blocks a spreadsheet-to-CRM workflow. A model cannot read a file it has not been given or use an unavailable tool.

Sources: https://learn.chatgpt.com/docs/extend/mcp?surface=cli and https://learn.chatgpt.com/docs/build-skills. Inspect tools available to this cohort; do not promise a native Google/Discord connector.

Demonstrate a complete local edit/test cycle. Routine authorized local steps do not require repeated approval.