skills.rest
cbusillo
cbusilloCOMMUNITY
Explore all skills by this author →
GitHub

plan

Manages explicit local plan files as an offline alternative to GitHub-backed planning.

5|1|Updated May 5, 2026
Search Tags:#planning#project management#github#offline#plan files#local plans
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill plan-cbusillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/plan
Command: npx skills add https://github.com/cbusillo/codex-skills --skill plan-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a controlled escape hatch for creating local, offline plan files when GitHub-backed planning is unavailable, unwanted, or inappropriate for private context. ## Core Features & Use Cases - Explicit Local Plans Only: Activates only when the user explicitly requests a local or offline plan, preventing accidental divergence from the standard GitHub-backed workflow. - Plan File Resolution: Resolves the plans directory through $CODE_HOME/plans, $CODEX_HOME/plans, ~/.code/plans, or ~/.codex/plans. - Structured Plan Files: Saves concise, implementation-oriented plans with frontmatter containing name and description, ready to migrate into a GitHub Issue later. - Use Case: When working in a repository that is not GitHub-backed, or when a plan contains private context that should not be recorded in GitHub, use this Skill to draft and store a local plan file. ## Quick Start Ask the agent to create an explicit local offline plan file for the current task instead of using GitHub-backed planning.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a local plan file instead of a GitHub issue?▼

Explicitly request a local or offline plan, and the Skill drafts the plan in chat first, then saves it under the resolved plans directory with name and description frontmatter. It never creates local plans implicitly.

When should I use local plans versus GitHub-backed planning?▼

Use local plans only when explicitly requested, when the repository is not GitHub-backed, or when private context should not be recorded in GitHub. For all GitHub-backed repositories, the github-plan skill is the default for durable planning, milestones, and workstream status.

Where are local plan files stored?▼

Plans are saved under $CODE_HOME/plans when set, then $CODEX_HOME/plans for compatibility, falling back to ~/.code/plans or ~/.codex/plans. Each plan file includes frontmatter with a name and description.

Does this skill modify repository documentation?▼

No. It reads repo context only as needed and never modifies the repository. Repo docs should describe implemented behavior or stable policy, not roadmaps, scratch plans, or temporary handoffs.

Why does the plan skill not activate automatically?▼

Its policy sets allow_implicit_invocation to false, so it only runs on explicit request. This override exists to route normal planning to the github-plan skill and keep local plans as a deliberate offline escape hatch.

Related Skills

Explore More Product & Management Skills→
rensjaspersrensjaspers

research

Gather facts and context from codebase and context-hub MCP.

Community
Intermediate
mvillmowmvillmow
18

track-implementation-progress

Track GitHub issue implementation progress and identify blockers by phase.

Community
Basic
vosslabvosslab
2

agents-md-fixer

Trims AGENTS.md files to repo-specific rules and canonical documentation pointers.

Community
Intermediate
ladislasladislas
2

pac-grill-with-docs

Grill issue-backed work against codebase and persist outcomes to GitHub comments.

Community
Advanced