Codex skills for structured planning and multi-agent execution, adapted from Claude Code's
/prp-prd command and Claude DevFleet MCP workflow.
These skills bring two Claude Code workflows to Codex:
-
prp-prd: An interactive PRD generator that uses gated questioning phases, market/technical research, and hypothesis-driven framing to produce execution-ready spec packages. Adapted from the Claude Code
/prp-prdslash command (originally by Wirasm's PRPs-agentic-eng). -
devfleet: A multi-agent orchestrator that dispatches parallel
codex execagents in isolated git worktrees with structured handoffs. Adapted from Claude DevFleet, which uses an MCP server for agent lifecycle management.
| Aspect | Claude Code | This Codex Version |
|---|---|---|
| prp-prd interaction | Built-in slash command with native conversation gates | Skill with phase instructions and GATE markers |
| DevFleet dispatch | MCP server (plan_project, dispatch_mission, etc.) |
codex exec + git worktrees + shell scripts |
| Agent isolation | MCP-managed worktrees with auto-merge | Git worktrees created by scripts/dispatch.sh |
| Monitoring | get_dashboard(), get_mission_status() MCP calls |
scripts/monitor.sh (file-based status) |
| Concurrency | Server-managed agent pool (configurable slots) | Background processes, max ~3 recommended |
The devfleet scripts provide real parallel execution — not just a process document — but the coordination layer is file-based rather than server-based.
| Skill | Purpose |
|---|---|
prp-prd |
Interactive PRD/PRP/task-plan/review-handoff generator |
devfleet |
Orchestrator: plan, dispatch, monitor, collect, review, verify |
devfleet-planner |
Write scoped work packets to .devfleet/packets/ |
devfleet-coder |
Implement one packet in an isolated worktree |
devfleet-reviewer |
Review merged code using handoff context |
devfleet-tester |
Verify acceptance criteria from work packets |
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo howdymary/codex-prpprd-devfleet \
--ref main \
--path skills/prp-prd \
--path skills/devfleet \
--path skills/devfleet-planner \
--path skills/devfleet-coder \
--path skills/devfleet-reviewer \
--path skills/devfleet-testerpython3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo howdymary/codex-prpprd-devfleet \
--ref main \
--path skills/prp-prdRestart Codex after install so the new skills are indexed.
- Codex CLI with
codex execsupport - Git (for worktree-based agent isolation)
- A git repository as the working directory (devfleet creates worktrees from HEAD)
$prp-prd "Add a payment processing system with Stripe"
Runs an 8-phase gated conversation:
- Initiate — confirm understanding
- Foundation — who, what, why, why now, how to measure
- Grounding — market research, competitor analysis
- Deep Dive — vision, primary user, JTBD, constraints
- Grounding — technical feasibility, codebase exploration
- Decisions — MVP scope, hypothesis, non-goals
- Generate — write PRD, PRP, task plan, review handoff
- Output — summary with validation status and next steps
$devfleet "Implement the payment system from the PRD"
- Plan —
$devfleet-plannerproduces work packets in.devfleet/packets/ - Approve — review packet list and parallelism plan
- Dispatch —
scripts/dispatch.shspawns codex exec agents in git worktrees - Monitor —
scripts/monitor.shtracks agent status - Collect —
scripts/collect.shmerges worktree branches - Review —
$devfleet-reviewerchecks merged code - Verify —
$devfleet-testerruns acceptance checks - Cleanup —
scripts/collect.sh --cleanupremoves worktrees
$devfleet-planner "Break this feature into work packets"
$devfleet-coder "Implement the auth-middleware packet"
$devfleet-reviewer "Review the merged coder output"
$devfleet-tester "Verify acceptance criteria for the payment flow"
- Open a fresh Codex session after installation.
- Confirm
prp-prdand thedevfleetskills appear in the skill picker. - Run
$prp-prdon a small feature idea — it should ask foundation questions before generating. - Run
$devfleeton the same idea — it should produce work packets and offer to dispatch agents. - Test dispatch with a trivial packet:
mkdir -p .devfleet/packets echo "## Objective\nCreate a hello.txt file" > .devfleet/packets/test-hello.md bash ~/.codex/skills/devfleet/scripts/dispatch.sh test-hello coder .devfleet/packets/test-hello.md --worktree bash ~/.codex/skills/devfleet/scripts/monitor.sh
.devfleet/ # ephemeral orchestration state (gitignored)
├── packets/ # work packet prompts from planner
│ ├── auth-middleware.md
│ └── db-schema.md
├── agents/ # PID, status, logs per agent
│ ├── auth-middleware.pid
│ ├── auth-middleware.status
│ ├── auth-middleware.log
│ └── ...
├── handoffs/ # structured handoff docs from agents
│ ├── auth-middleware.md
│ ├── db-schema.md
│ ├── review.md
│ └── testing.md
└── worktrees/ # isolated git worktrees per agent
├── auth-middleware/
└── db-schema/