Planning With Files

Implements the "Manus-style" three-file pattern (task_plan.md, notes.md, deliverable.md) to give Claude persistent memory across context resets. Instead of relying on volatile TodoWrite tools, you track phases with checkboxes, log failures, and store research in markdown files. The core idea is simple: re-read your plan before making decisions so goals don't drift after 50 tool calls. Use it for multi-step tasks, research projects, or anything that needs organization beyond a single response. Skip it for quick edits or simple questions. The approach borrows directly from context engineering patterns that made Manus AI's agents more reliable, treating the filesystem as external memory rather than stuffing everything into context.

skills.sh installs: 1.1K
GitHub stars: 66
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add charon-fan/agent-playbook --skill planning-with-files --agent claude-code

Installs into .claude/skills of the current project.

Files

Planning with Files

"Work like Manus" — Uses persistent markdown files for planning, progress tracking, and knowledge storage.

Description

A skill that transforms your workflow to use persistent markdown files for planning and progress tracking.

The Problem

Claude Code (and most AI agents) suffer from:

Volatile memory — TodoWrite tool disappears on context reset
Goal drift — Original goals get forgotten after many tool calls
Hidden errors — Failures aren't tracked, mistakes repeat
Context stuffing — Everything crammed into context instead of stored

The Solution: 3-File Pattern

For every complex task, create THREE files:

task_plan.md      → Track phases and progress
notes.md          → Store research and findings
[deliverable].md  → Final output

The Workflow Loop

1. Create task_plan.md with goal and phases
2. Research → save to notes.md → update task_plan.md
3. Read notes.md → create deliverable → update task_plan.md
4. Deliver final output