How do I install the Planning With Files skill?

Run npx skillmds add tools-only/planning-with-files in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Planning With Files safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Planning With Files?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Planning With Files free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Planning With Files?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Planning With Files by tools-only — Agent Skill

Name: Planning With Files
Rating: 4.2 (5 reviews)
Author: tools-only

Planning With Files

Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.

tools-only f99c861 3 files · 6.0 KB Updated Sep 8, 2026 7 repo stars

File contents

Planning with Files

Work like Manus: Use persistent markdown files as your "working memory on disk."

FIRST: Check for Previous Session (v2.2.0)

Before starting work, check for unsynced context from a previous session:

python3 .continue/skills/planning-with-files/scripts/session-catchup.py "$(pwd)" || python .continue/skills/planning-with-files/scripts/session-catchup.py "$(pwd)"

If catchup report shows unsynced context:

Run git diff --stat to see actual code changes
Read current planning files
Update planning files based on catchup + git diff
Then proceed with task

Quick Start

Before any complex task:

Create task_plan.md, findings.md, progress.md in your project root
If they don't exist yet, initialize them using:
- macOS/Linux: bash .continue/skills/planning-with-files/scripts/init-session.sh
- Windows: powershell -ExecutionPolicy Bypass -File .continue/skills/planning-with-files/scripts/init-session.ps1
Re-read task_plan.md before major decisions
Update task_plan.md after each phase completes
Write discoveries to findings.md (especially after web/search/image/PDF viewing)

The Core Pattern

Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)

→ Anything important gets written to disk.

File Purposes

File	Purpose	When to Update
`task_plan.md`	Phases, progress, decisions	After each phase
`findings.md`	Research, discoveries	After any discovery
`progress.md`	Session log, test results	Throughout session

Critical Rules

1. Create Plan First

Never start a complex task without task_plan.md.

2. The 2-Action Rule

After every 2 view/browser/search operations, save key findings to text files.

3. Read Before Decide

Before major decisions, read task_plan.md to refresh goals.

4. Update After Act

After completing any phase, update statuses and log errors in task_plan.md.

5. Log ALL Errors

Every error goes in the plan file so you don't repeat it.

6. Never Repeat Failures

If an action failed, the next action must be different.

References

reference.md
examples.md

---name: planning-with-filesdescription: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.---# Planning with FilesWork like Manus: Use persistent markdown files as your "working memory on disk."## FIRST: Check for Previous Session (v2.2.0)Before starting work, check for unsynced context from a previous session:```bashpython3 .continue/skills/planning-with-files/scripts/session-catchup.py "$(pwd)" || python .continue/skills/planning-with-files/scripts/session-catchup.py "$(pwd)"```If catchup report shows unsynced context:1. Run `git diff --stat` to see actual code changes2. Read current planning files3. Update planning files based on catchup + git diff4. Then proceed with task## Quick StartBefore any complex task:1. Create `task_plan.md`, `findings.md`, `progress.md` in your project root2. If they don't exist yet, initialize them using: - macOS/Linux: `bash .continue/skills/planning-with-files/scripts/init-session.sh` - Windows: `powershell -ExecutionPolicy Bypass -File .continue/skills/planning-with-files/scripts/init-session.ps1`3. Re-read `task_plan.md` before major decisions4. Update `task_plan.md` after each phase completes5. Write discoveries to `findings.md` (especially after web/search/image/PDF viewing)## The Core Pattern```Context Window = RAM (volatile, limited)Filesystem = Disk (persistent, unlimited)→ Anything important gets written to disk.```## File Purposes| File | Purpose | When to Update ||------|---------|----------------|| `task_plan.md` | Phases, progress, decisions | After each phase || `findings.md` | Research, discoveries | After any discovery || `progress.md` | Session log, test results | Throughout session |## Critical Rules### 1. Create Plan FirstNever start a complex task without `task_plan.md`.### 2. The 2-Action RuleAfter every 2 view/browser/search operations, save key findings to text files.### 3. Read Before DecideBefore major decisions, read `task_plan.md` to refresh goals.### 4. Update After ActAfter completing any phase, update statuses and log errors in `task_plan.md`.### 5. Log ALL ErrorsEvery error goes in the plan file so you don't repeat it.### 6. Never Repeat FailuresIf an action failed, the next action must be different.## References- [reference.md](reference.md)- [examples.md](examples.md)

Frequently asked questions