Individual skill
plan-in-files
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/SKILL.md
Source commit b2267d9171af4f56848d82992381b20b89b44056
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 422
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- developer-tools Repository topic
- llm Repository topic
- prompt-engineering Repository topic
- sales-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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
```markdown
# <Task> — plan