plan-execute

Plan Execute Skill

Purpose

When the user runs /plan-execute {plan-file-path}, start the "orchestrated plan execution" workflow:

1. I (Claude Code) ask Codex to implement the code according to the plan.
2. After Codex finishes, I review the generated code.
3. I write the review into the reviews/ directory, then ask Codex to inspect and fix the issues.
4. Repeat until the code quality bar is met.

Core principle: I do not write or edit code myself. I only do two things: review code and orchestrate Codex. All code changes, including implementation and fixes, are performed by Codex.

Usage

/plan-execute plans/my-feature-plan.md

Session Reuse

After each Codex invocation, extract session_id=xxx from the script output and save it as the session ID for the current task. In later Codex calls for the same task, pass --session <id> to reuse context so Codex remembers prior implementation and fix history instead of rereading the entire codebase every time.

My Workflow (Claude Code)

Step 1: Read the Plan and Split Execution Steps

Read the specified plan file and understand:

• The overall goal and scope of the plan
• The list of files to create or modify
• The order of implementation steps
• Relevant project conventions, especially from CLAUDE.md

If the plan already contains a checklist (- [ ] / - [x]), use those items as execution units. If it does not define clear steps, split the work into reasonable batches, with no more than 5 file changes per batch.

Step 2: Ask Codex to Implement the Code

Use the /codex skill and give Codex the following instruction:

Implement the code according to the plan in {plan-file-path}.

Current execution scope: {specific step or batch description}

Requirements:
- Follow the design in the plan exactly. Do not improvise beyond it.
- Obey the Code Quality Hard Limits defined in `CLAUDE.md`.
- Single file <= 800 lines, single function <= 50 lines, nesting <= 3 levels
- Run `pnpm build` after implementation to confirm compilation succeeds
- If the plan includes a checklist, mark completed steps as `[x]`

After implementation, list all changed files and provide a summary of each change.