generate-codex-plan

Convert basic plans into multi-file Codex CLI execution artifacts.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/arielZusman/imai-dev-plugin --skill generate-codex-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-codex-plan
Source: https://github.com/arielZusman/imai-dev-plugin/tree/main/skills/generate-codex-plan
Command: npx skills add https://github.com/arielZusman/imai-dev-plugin --skill generate-codex-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill automates the process of turning simple planning inputs into Codex CLI execution-ready documents, so teams can ship automated plan execution with consistent structure and governance.

Core Features & Use Cases

  • Multi-file plan enrichment: Converts a plan into a structured set of intro and task files under docs/plans/codex.
  • Context embedding: Injects inline context, templates, and verification steps to streamline Codex-driven implementations.
  • Governed execution: Segregates responsibilities between Codex (code changes) and Claude Code (verification, reviews, commits).

Quick Start

Use this skill after you have created a basic plan and want to prepare it for Codex CLI execution. The skill reads plan references, applies the INTRO-TEMPLATE.md and TASK-TEMPLATE.md, and outputs a ready-to-run codex plan under docs/plans/codex/YYYY-MM-DD-<feature-name>/ with intro.md and task-*.md files. It also updates docs/plans/codex/INDEX.md.

Frequently Asked Questions about generate-codex-plan

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

FAQPage Schema
How do I turn a basic plan into Codex CLI execution-ready files?

To turn a basic plan into Codex CLI execution-ready files, you use automated multi-file plan enrichment to apply INTRO-TEMPLATE.md and TASK-TEMPLATE.md, generating structured intro.md and task-*.md outputs under docs/plans/codex.

What is multi-file plan enrichment for automated code changes?

Multi-file plan enrichment is the process of converting simple plan prompts into structured intro and task files, injecting inline context and verification steps to streamline Codex-driven code implementations.

Do I need specific plan references to generate Codex-ready workflows?

Yes, generating Codex-ready workflows requires plan references located under ~/.claude/plans or ~/.codex/plans, alongside the INTRO-TEMPLATE.md and TASK-TEMPLATE.md templates found in assets.

How does governed execution separate responsibilities between Codex and Claude Code?

Governed execution separates responsibilities by using Codex CLI for automated code changes and Claude Code for verification, reviews, and commits, ensuring consistent structure and governance across the workflow.

What is the best way to automate multi-file plan generation for Codex?

The best way to automate multi-file plan generation for Codex is to apply templates to basic plan inputs, outputting a ready-to-run codex plan under docs/plans/codex/YYYY-MM-DD-<feature-name>/ and updating docs/plans/codex/INDEX.md.

Can I use this automated plan execution approach without writing to docs/plans/codex?

No, this automated plan execution approach requires the ability to write to docs/plans/codex, as this directory stores the generated intro.md, task-*.md files, and the updated INDEX.md for workflow governance.