plan-execute

Plan tasks with Opus and execute them with Codex.

11|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/brolag/neural-claude-code --skill plan-execute-brolag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-execute
Source: https://github.com/brolag/neural-claude-code/tree/main/skills/plan-execute
Command: npx skills add https://github.com/brolag/neural-claude-code --skill plan-execute-brolag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates complex tasks by planning with Opus and executing with Codex to optimize costs and outcomes.

Core Features & Use Cases

  • Planning with Opus to break tasks into atomic steps, generate a structured execution plan, and define success criteria.
  • Execution via Codex to implement plan steps, perform file operations, code changes, and system commands as needed.
  • Review and fallback: Opus validates results against criteria and recomputes plans if issues arise.

Quick Start

Use /plan-execute <task description> to trigger planning, execution, and review for the given task.

Frequently Asked Questions about plan-execute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate complex coding tasks using Opus and Codex?

This skill orchestrates complex tasks by planning with Opus to break them into atomic steps and executing with Codex to perform code changes. Opus then validates the results against success criteria and recomputes plans if issues arise.

What is the best way to automate multi-step feature implementations and refactors?

The best way to automate multi-step feature implementations is to generate a structured execution plan with Opus, then execute the file operations via Codex. This optimizes costs and outcomes by separating strategic planning from rapid execution.

Can I execute code changes with Codex if Opus generates the plan?

Yes, you can execute code changes with Codex after Opus generates the structured execution plan. Opus handles the strategic planning and review, while Codex handles the rapid execution of file operations and system commands.

Does the plan-execute workflow handle errors when Codex is unavailable?

Yes, the plan-execute workflow includes robust error handling and automatically falls back to Opus if Codex is unavailable. This ensures that task execution continues even when the primary execution engine encounters issues.

Do I need a structured plan.json file to orchestrate task execution?

Yes, you need a structured plan.json file containing the execution plan generated by Opus. The orchestration process requires this structured planning data alongside per-step execution logs to track and validate the task.