Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
A skill your agent uses for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash.
Install Plan In Files
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OneWave-AI/claude-skills plan-in-files --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plan-in-files .claude/skills/plan-in-files && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .claude/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-filesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OneWave-AI/claude-skills plan-in-files --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plan-in-files .agents/skills/plan-in-files && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .agents/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OneWave-AI/claude-skills plan-in-files --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plan-in-files .cursor/skills/plan-in-files && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .cursor/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OneWave-AI/claude-skills.git --path plan-in-files--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OneWave-AI/claude-skills plan-in-files --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plan-in-files .gemini/skills/plan-in-files && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .gemini/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OneWave-AI/claude-skills plan-in-filesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plan-in-files .github/skills/plan-in-files && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .github/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OneWave-AI/claude-skills --skill plan-in-files -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OneWave-AI/claude-skills plan-in-files --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plan-in-files .opencode/skills/plan-in-files && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-in-files" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/plan-in-files into .opencode/skills/plan-in-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-in-files", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-in-files- GitHub stars
- 336
- Token cost
- ~802 tokens
- SKILL.md length
- 423 words
- Files
- 1
- Skills in repo
- 69
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash.
- Works in 5 steps: Write it. Show it to the user before… → Do one step. → Tick the box in the file, immediately.… → …
- Any task that spans more than a couple of steps
- SKILL.md covers Core Behavior, Plan Shape, Working the Plan and Rules, plus 2 more sections
- Calls git
What it does
Plan In Files is an agent skill from OneWave-AI/claude-skills. Use for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash. Trigger when the user asks for a plan, says "keep track of this", "don't lose the thread", or when a task is large enough that forgetting step four is likely.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Refactoring. The repository describes itself as: 200+ production-ready Claude Code skills for sales, marketing, design, engineering, and AI agent architecture. Built and maintained by OneWave AI. The licence is MIT.
When your agent uses it
- Any task that spans more than a couple of steps
- Sessions — refactors
- Multi-file features
- Anything that must survive a context reset
Example prompts
- “keep track of this”
- “t lose the thread”
- “/plan-in-files”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Write it. Show it to the user before executing when the work is large or destructive.
- Do one step.
- Tick the box in the file, immediately. Not at the end — a crash between step three and the end loses everything.
- When reality disagrees with the plan, edit the plan. A plan you silently abandoned is worse than no plan.
- Append surprises to Notes as you hit them. That is where the next session's time savings live.
What it can do on your machine
Read from SKILL.md and the folder at commit fc5b785. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan In Files loads about 802 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 423 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OneWave-AI/claude-skills at commit fc5b785, republished under its MIT licence (© OneWave-AI). 423 words, ~802 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-in-files/SKILL.md (or your agent's skills folder).- name
- plan-in-files
- description
- Use for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash. Trigger when the user asks for a plan, says "keep track of this", "don't lose the thread", or when a task is large enough that forgetting step four is likely.
Plan in Files
A plan that lives in the conversation dies with the conversation. A plan that lives in a file survives a crash, a /clear, a laptop reboot, and a different person picking the work up on Monday.
Core Behavior
Before starting multi-step work, write the plan to disk. Update it as you go. The file is the source of truth about progress — not memory, not the chat.
Default location: PLAN.md at the repo root for one-off work, or docs/plans/<yyyy-mm-dd>-<topic>.md when the repo keeps plan history. Gitignore it or commit it — ask once, then follow the repo's convention.
Plan Shape
# <Task> — plan
**Goal:** <one sentence, in the user's words>
**Done when:** <the observable condition that ends this work>
## Constraints
- <the things that must stay true: no API break, no new deps, ships today>
## Steps
- [ ] 1. <action> — `path/to/file`
- [ ] 2. <action> — `path/to/file`
- [ ] 3. <action> — verify with `<command>`
## Notes
<discoveries, gotchas, things that turned out to be false>
## Log
- <date/time> — <what happened>Each step is one action on a named file or a named command. "Refactor the auth layer" is not a step; "move verifyToken out of api/auth.ts into lib/token.ts and update the three imports" is.
Working the Plan
- Write it. Show it to the user before executing when the work is large or destructive.
- Do one step.
- Tick the box in the file, immediately. Not at the end — a crash between step three and the end loses everything.
- When reality disagrees with the plan, edit the plan. A plan you silently abandoned is worse than no plan.
- Append surprises to Notes as you hit them. That is where the next session's time savings live.
Show full SKILL.md (204 more words)Show less
Rules
- Never tick a box for work you have not verified. "Edited the file" is not "step done" if the step said the tests pass.
- Never fake progress to make the plan look finished. An honest half-done plan is useful; a dishonest complete one is a trap.
- Keep the plan under a page. A plan longer than the work is a symptom of avoiding the work.
- If a step turns out to be five steps, split it in the file before continuing.
- When work finishes, write one closing line in the Log and leave the file. It becomes the record of why the code looks the way it does.
Resuming
When picking up an existing plan file:
- Read it.
- Verify the ticked steps against reality —
git log,git diff, run the tests. Ticked does not always mean true. - Correct the file if it lied.
- Start at the first genuinely unfinished step.
When Not to Use This
A single-file edit, a one-line fix, a question. Writing a plan file for a two-minute change is ceremony, and ceremony is the thing this library is against. The test: if losing the session would cost more than five minutes of rework, write the file.
© OneWave-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plan-in-files of OneWave-AI/claude-skills.
Open the folder on GitHubat commit fc5b785
Compare with similar skills
Plan In Files next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan In Files this skillOneWave-AI/claude-skills | 336 | — | ~802 | Automated safety check: Pass | MIT | |
| Guidelinesakash-network/node | 1.1k | 20 repos | ~577 | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Component Refactoringlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Ponytail Lazy Developer ModeDietrichGebert/ponytail | 160k | 1 repos | ~873 | Automated safety check: Pass | MIT | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
Ponytail Lazy Developer Mode
DietrichGebert/ponytail
Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
More from OneWave-AI/claude-skills
All 69 skills in this repoCRM Data Cleanup
OneWave-AI/claude-skills
Finds duplicate and junk records in a CRM CSV export with fuzzy matching, normalizes fields and writes a reviewable merge plan plus import-ready files without touching the live CRM.
Design Export Repair
OneWave-AI/claude-skills
Repairs broken decks and PDFs exported from Claude Design or similar AI deck generators: clipped text, wrong fonts and corrupted .pptx package structure.
Bi Measure Builder
OneWave-AI/claude-skills
Writes, explains, debugs, and optimizes BI calculations - Power BI / Fabric DAX measures and calculated columns, Tableau calculated fields (FIXED/INCLUDE/EXCLUDE LOD expressions, table…
Bookkeeping Close
OneWave-AI/claude-skills
Categorizes transactions, reconciles bank and card statements to the ledger, works a month-end checklist and prepares a close package, without ever forcing a balance.
CSV and Excel Merger
OneWave-AI/claude-skills
Combines CSV, TSV and Excel files into one verified table with pandas, by stacking or joining, mapping columns, normalizing keys and removing duplicates.
Sec Filing Puller
OneWave-AI/claude-skills
Pulls financial statement numbers for US public companies straight from SEC EDGAR's free official XBRL APIs (companyfacts, companyconcept, frames, submissions) into a cited table.
Related
Categories
Questions about Plan In Files
What does Plan In Files do?
A skill your agent uses for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash. Plan In Files is an agent skill from OneWave-AI/claude-skills. Use for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash.
When should I use Plan In Files?
Plan In Files fits situations like: any task that spans more than a couple of steps; sessions — refactors; multi-file features; anything that must survive a context reset.
How do I install Plan In Files in Claude Code?
Run `npx skills add OneWave-AI/claude-skills --skill plan-in-files -a claude-code`. Or copy the skill folder (plan-in-files in OneWave-AI/claude-skills) into .claude/skills/plan-in-files in your project. Claude Code loads it when a task matches its description.
How do I install Plan In Files in Codex?
Run `npx skills add OneWave-AI/claude-skills --skill plan-in-files -a codex`. Or copy the skill folder (plan-in-files in OneWave-AI/claude-skills) into .agents/skills/plan-in-files in your project. Codex loads it when a task matches its description.
Can I use Plan In Files in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OneWave-AI/claude-skills --skill plan-in-files -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-in-files, .gemini/skills/plan-in-files, .github/skills/plan-in-files and .opencode/skills/plan-in-files in your project.
What does Plan In Files need to run?
Going by SKILL.md and its folder, Plan In Files needs the command-line tools its instructions call (git).
Does Plan In Files access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plan In Files safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan In Files use?
Plan In Files is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan In Files use?
About 802 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plan In Files?
Skills that share tags, products or a category with Plan In Files: Guidelines (akash-network/node, 1.1k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Component Refactoring (langflow-ai/langflow, 155k stars) and Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 160k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan In Files?
OneWave-AI (a GitHub organization) maintains it in OneWave-AI/claude-skills, which has 336 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.
Source: OneWave-AI/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.