planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
- Installs
- 47
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/yyh211/claude-meta-skill --skill planning-with-files- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads planning-with-files automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Planning with Files
Work like Manus: Use persistent markdown files as your "working memory on disk."
Quick Start
Before ANY complex task:
- Create
task_plan.mdin the working directory - Define phases with checkboxes
- Update after each phase - mark [x] and change status
- Read before deciding - refresh goals in attention window
The 3-File Pattern
For every non-trivial task, create THREE files:
| File | Purpose | When to Update |
|---|---|---|
task_plan.md | Track phases and progress | After each phase |
notes.md | Store findings and research | During research |
[deliverable].md | Final output | At completion |
Core Workflow
Loop 1: Create task_plan.md with goal and phases
Loop 2: Research → save to notes.md → update task_plan.md
Loop 3: Read notes.md → create deliverable → update task_plan.md
Loop 4: Deliver final output
The Loop in Detail
Before each major action:
Read task_plan.md # Refresh goals in attention window
After each phase:
Edit task_plan.md # Mark [x], update status
When storing information:
Write notes.md # Don't stuff context, store in file
task_plan.md Template
Create this file FIRST for any complex task:
# Task Plan: [Brief Description]
## Goal
[One sentence describing the end state]
## Phases
- [ ] Phase 1: Plan and setup
- [ ] Phase 2: Research/gather information
- [ ] Phase 3: Execute/build
- [ ] Phase 4: Review and deliver
## Key Questions
1. [Question to answer]
2. [Question to answer]
## Decisions Made
- [Decision]: [Rationale]
## Errors Encountered
- [Error]: [Resolution]
## Status
**Currently in Phase X** - [What I'm doing now]
notes.md Template
For research and findings:
# Notes: [Topic]
## Sources
### Source 1: [Name]
- URL: [link]
- Key points:
- [Finding]
- [Finding]
## Synthesized Findings
### [Category]
- [Finding]
- [Finding]
Critical Rules
1. ALWAYS Create Plan First
Never start a complex task without task_plan.md. This is non-negotiable.
2. Read Before Decide
Before any major decision, read the plan file. This keeps goals in your attention window.
3. Update After Act
After completing any phase, immediately update the plan file:
- Mark completed phases with [x]
- Update the Status section
- Log any errors encountered
4. Store, Don't Stuff
Large outputs go to files, not context. Keep only paths in working memory.
5. Log All Errors
Every error goes in the "Errors Encountered" section. This builds knowledge for future tasks.
When to Use This Pattern
Use 3-file pattern for:
- Multi-step tasks (3+ steps)
- Research tasks
- Building/creating something
- Tasks spanning multiple tool calls
- Anything requiring organization
Skip for:
- Simple questions
- Single-file edits
- Quick lookups
Anti-Patterns to Avoid
| Don't | Do Instead |
|---|---|
| Use TodoWrite for persistence | Create task_plan.md file |
| State goals once and forget | Re-read plan before each decision |
| Hide errors and retry | Log errors to plan file |
| Stuff everything in context | Store large content in files |
| Start executing immediately | Create plan file FIRST |
Advanced Patterns
See reference.md for:
- Attention manipulation techniques
- Error recovery patterns
- Context optimization from Manus
See examples.md for:
- Real task examples
- Complex workflow patterns
FAQ
What does the planning-with-files skill do?
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
How do I install planning-with-files?
Run npx skills add https://github.com/yyh211/claude-meta-skill --skill planning-with-files in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/planning-with-files/ (personal) or .claude/skills/planning-with-files/ (project).
Which AI agents can use planning-with-files?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is planning-with-files safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains planning-with-files?
It is published by yyh211 in yyh211/claude-meta-skill. It has 47 recorded installs.
More from yyh211/claude-meta-skill
daily-ai-news
yyh211/claude-meta-skill
Aggregates and summarizes the latest AI news from multiple sources including AI news websites and web search. Provides concise news briefs with direct links to original articles. Activates when user asks for 'today's AI news', 'AI updates', 'latest AI developments', or mentions wanting a 'daily AI briefing'.
frontend-design
yyh211/claude-meta-skill
Open the skill to read its SKILL.md instructions.
deep-reading-analyst
yyh211/claude-meta-skill
Open the skill to read its SKILL.md instructions.
prompt-optimize
yyh211/claude-meta-skill
Expert prompt engineering skill that transforms Claude into "Alpha-Prompt" - a master prompt engineer who collaboratively crafts high-quality prompts through flexible dialogue. Activates when user asks to "optimize prompt", "improve system instruction", "enhance AI instruction", or mentions prompt engineering tasks.
dry-refactoring
yyh211/claude-meta-skill
Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY principle, or mentions code smells like copy-paste, magic numbers, or repeated logic. Implements a 4-step workflow from identifying repetition to verified refactoring.
create-skill-file
yyh211/claude-meta-skill
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.