Development Using Claude Code or Codex · Part 2
Part 2: Workflow Orchestrator from PRD to Production
April 8, 2026 · 2 min read
WorkflowOrchestrationPrdProduction
Your daily workflow is already clear:
- Get PRD/specs from Product
- Break PRD into tasks
- Develop each task
- Do code review
- QA
- UAT
- Production deployment and sanity checks
The mistake most teams make is keeping this as tribal knowledge. Instead, encode it once as an orchestrator skill and run it the same way in Claude Code and Codex.
Skill for This Post: workflow-orchestrator
Create .ai/skills/workflow-orchestrator/SKILL.md:
---
name: workflow-orchestrator
description: Route work through PRD -> Tasks -> Dev -> Review -> QA -> UAT -> Prod Sanity.
---
# Workflow Orchestrator
## Stages
1. PRD_INTAKE
2. TASK_BREAKDOWN
3. IMPLEMENTATION
4. CODE_REVIEW
5. QA
6. UAT
7. DEPLOY_AND_SANITY
## Rules
- Never skip a stage without explicit user approval.
- Each stage must produce a handoff artifact for the next stage.
- If a stage fails, return to the earliest failing stage.
## Required Output
For every run, return:
1) current stage
2) completed stages
3) blocked stages with reasons
4) next stage input checklistElegant Cross-Agent Sharing with Symlinks
Keep canonical skill files in your repo, then symlink into both agent homes:
mkdir -p ~/.claude/skills ~/.codex/skills
ln -sfn "$PWD/.ai/skills/workflow-orchestrator" ~/.claude/skills/workflow-orchestrator
ln -sfn "$PWD/.ai/skills/workflow-orchestrator" ~/.codex/skills/workflow-orchestratorOptional helper script:
#!/usr/bin/env bash
set -euo pipefail
skill="$1"
mkdir -p ~/.claude/skills ~/.codex/skills
ln -sfn "$PWD/.ai/skills/$skill" ~/.claude/skills/$skill
ln -sfn "$PWD/.ai/skills/$skill" ~/.codex/skills/$skillOne Skill per Post Roadmap
From Part 3 onward, each post defines exactly one stage skill:
- PRD intake
- task breakdown
- implementation
- code review
- QA
- UAT
- production deploy and sanity
This gives you a modular workflow where each stage can evolve independently without breaking the full pipeline.