How PMs Use the Codex App

Why It Matters

By enabling non‑technical leaders to diagnose and fix code issues, Codex shortens feedback loops and raises overall engineering efficiency.

Key Takeaways

• PM leverages Codex to understand code without writing it.
• AI skills fetch build logs, eliminating manual debugging steps.
• Codex identifies unnecessary UI elements, streamlining product decisions.
• Automated token installation via Codex resolves PR test failures quickly.
• Iterative skill updates make Codex increasingly effective across codebases.

Summary

The video follows a product manager who integrates the Codex app into daily workflows to bridge the gap between non‑coding responsibilities and the technical codebase. By asking Codex to explain unfamiliar UI elements and to perform routine tasks, the PM stays informed without writing code themselves.

When a confusing button appeared, the PM consulted the team, confirmed it was unnecessary, and used Codex to delete it. Later a pull‑request failed a test; the PM opened the Codex skills tab, ran the “build kite fetch logs” command, learned a missing token was required, and instructed Codex to install the token and fix the failure. The PM also updated two underlying skills during the process.

Key moments include pinging the team about the button, leveraging the “build kite” skill to retrieve logs, asking Codex to set the token, and iteratively improving the assistant’s capabilities while resolving the PR issue. These actions demonstrate a hands‑on, AI‑augmented approach to code review and debugging.

The experience shows how AI assistants like Codex can empower product managers to act on code‑level feedback, reduce manual debugging effort, and continuously refine the tool’s skill set, ultimately accelerating development cycles and enhancing overall code quality.

Original Description

Alexander Embiricos (a Product Manager on the Codex team) shows how he uses Codex skills to make a small product change, diagnose a Buildkite failure, and improve the skills so the next PR goes faster.

Takeaways:

- Skills are a shortcut for repeated workflows like Buildkite logs.

- When a skill fails, fix the root cause and update the skill.

- The real win is compounding: the codebase gets easier over time.

This is the loop: ship the fix, then teach the workflow.

Chapters:

00:00 PM context: careful before tagging engineers

00:16 A confusing button and a quick team check

00:32 Delete the button, then hit a PR failure

00:46 Use the Buildkite skill instead of digging through logs

01:09 Install the Buildkite token

01:20 Update the skill so it works next time

01:53 Inductive loop: feedback - fix - improve the skill

02:06 Compounding payoff: Codex gets better over time