Agent skill · writing content · aiskillstore
plan
Plan lifecycle management for Codex plans stored in $CODEX_HOME/plans (default ~/.codex/plans). Use when a user asks to create, find, read, update, delete, or manage plan documents for implementation work or overview/reference documentation.
Why this skill is useful
Adds specific scripts and workflows for managing Codex plan documents that the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Plan Overview Create and manage plan documents on disk. Plans stored on disk are markdown files with YAML frontmatter and free-form content. When drafting in chat, output only the plan body without frontmatter; add frontmatter only when stashing to disk. Support both implementation plans and overview/reference plans. Only write to the plans folder; do not modify the repository codebase. Core rules Resolve the plans directory as $CODEXHOME/plans or ~/.codex/plans when CODEXHOME is not set. Create the plans directory if it does not exist. Never write to the repo; only read files to understand context. Require frontmatter with only name and description (single-line values) for on-disk plans. When presenting a draft plan in chat, omit frontmatter and start at # Plan. Enforce naming rules: short, lower-case, hyphen-delimited; filename must equal <name>.md. If a plan is not found, state it clearly and offer to create one. Allow overview-style plans that document flows, architecture, or context without a work checklist. Decide the task 1. Find/list: discover plans by frontmatter summary; confirm if multiple matches exist. 2. Read/use: validate frontmatter; present summary and full contents. 3. Create: inspect repo read-only; choose plan style (implementation vs overview); draft plan; write to plans directory only. 4. Update: load plan; revise content and/or description; preserve frontmatter keys; overwrite the plan file. 5. Delete: confirm intent, then remove the plan file if asked. Plan discovery Prefer scripts/listplans.py for quick summaries. Use scripts/readplanfrontmatter.py to validate a specific plan. If name mismatches filename or frontmatter is missing fields, call it out and ask whether to fix. Plan creation workflow 1. Read relevant docs and entry points (README.md, docs/, key modules) to scope requirements. 2. Identify scope, constraints, and data model/API implications (or capture existing behavior for an overview). 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/plan--fa9d0c