How PMs use the Codex app

AI 总结

• 用 skills 作为重复工作流的快捷方式（如查看 Buildkite 日志）
• 从删除困惑按钮发起改动，到遇到 PR 构建失败的完整演示流程
• 通过 Buildkite skill 代替手动翻日志，并配置所需 token
• 当 skill 失败时追溯根因、修复并更新 skill 以便下次可用
• 强调“发版修复→教授工作流→技能改进”的反馈闭环与长期复利

内容摘录

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