plan

Generates structured implementation and overview plans for complex coding tasks.

8|1|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/akiojin/llm-router --skill plan-akiojin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/akiojin/llm-router/tree/main/.codex/skills/.system/plan
Command: npx skills add https://github.com/akiojin/llm-router --skill plan-akiojin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate structured plans for complex coding tasks, with clear requirements, scope, and action items.

Core Features & Use Cases

  • Draft implementation or overview plans
  • Support saving plans to $CODEX_HOME/plans with frontmatter (name, description)
  • Plan discovery, read, create, update, and delete workflows

Quick Start

Draft a plan body in chat; choose to save as a plan file or proceed with execution steps.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a structured plan for a complex coding task?

Generate a plan by drafting structured steps with clear requirements and action items, then save it as a markdown file with frontmatter containing name and description to $CODEX_HOME/plans or ~/.codex/plans for reuse and version control.

Can I save and manage multiple plans for different projects?

Yes. Plans are stored as individual files in a dedicated plans directory with strict naming conventions and frontmatter metadata, enabling discovery, read, update, and delete workflows across projects.

What goes into a plan file and how is it structured?

A plan file contains frontmatter with name and description fields followed by a markdown body with actionable implementation or overview steps; the structure enforces clarity and enables parsing by helper scripts.

How do I find and reuse existing plans?

Plans stored in the designated directory are discoverable through find operations; read them to review scope and requirements before executing implementation steps or creating variations for similar tasks.

Do I need to modify my project repository to use plans?

No. Plans are managed entirely outside your repository in $CODEX_HOME/plans or ~/.codex/plans, keeping project files clean while maintaining centralized task documentation and execution tracking.