Individual skill
planning-with-files
Use this by default for non-trivial multi-step work that needs persistent planning, progress tracking, or durable notes on disk. Trigger when a task will likely span multiple tool calls, research steps, verification loops, or enough context that the plan should not live only in transient chat memory.
skills/planning-with-files/SKILL.md
Source commit d394fb599ed9e6ea2212a9e6daa864345fe97a26
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 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)
- 6,016
- Repository last updated
- Oct 19, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-research Repository topic
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- developer-tools Repository topic
- mcp Repository topic
- paper-writing Repository topic
- zotero Repository topic
- codex-cli Repository topic
- openai-codex Repository topic
- productivity Derived category
- research Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,290 bytesSKILL.mdcore · 4,290 bytesSKILL.mdcore · 4,290 bytesSKILL.mdcore · 4,290 bytesexamples.mddoc · 4,426 bytesreference.mddoc · 3,478 bytes
Read excerpt
# Planning with Files
Work like Manus: use persistent markdown files as your working memory on disk.
This is not just an optional planning style. It should be the default persistence layer for complex Codex work.
Use it proactively when:
- the task will likely take more than a few tool calls
- progress needs to be tracked across phases
- findings or evidence must be preserved while working
- the task may branch, pause, or resume later
- relying on chat context alone would be fragile
