Skip to main content
skill CX Codex

planning-with-files · zhaono1 — Claude Code skill: plans and notes in files

Keeps the plan, research notes and final output in markdown files instead of context. Useful for multi-step tasks and research work.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaono1/agent-playbook --skill planning-with-files -a claude-code
Open on GitHub

What planning-with-files does

The skill splits a task across three files: task_plan.md holds the goal and phases, notes.md collects findings, and a third file becomes the deliverable. The agent writes the plan, appends notes as it goes, ticks off phases, and only then hands over the result.

Why bother? TodoWrite vanishes on a context reset, and after enough tool calls the original goal drifts out of view. Files survive both. Failures land in the plan file too, so the same mistake doesn't repeat.

Install it globally and it works in Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Skip it for simple questions or a single-file edit — three files for a two-step job is just clutter. The skill runs with Read, Write, Edit, Bash, Grep and Glob, so no API key is involved.

What it helps with

  • keep the original goal in sight across a long tool-call chain
  • preserve research findings through context resets
  • log a failure so the agent stops repeating it
  • break a multi-step task into phases with visible progress
  • move intermediate data out of context and into files

Example prompts for the agent

  • Create a plan for "research the benefits of TypeScript and write a summary" and track it in task_plan.md
  • Set up notes.md, save sources there as you research, and tick off finished phases in the plan
  • Update task_plan.md: mark the current phase and note what broke on the last step

How to install planning-with-files

1Skills CLI (Vercel)

npx skills add zhaono1/agent-playbook --skill planning-with-files -a claude-code

2Manually: put the files in place

~/.claude/skills/planning-with-files/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/planning-with-files/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about planning-with-files

How do I install planning-with-files in Claude?

Run npx skills add zhaono1/agent-playbook --skill planning-with-files -a claude-code. The skill lands at ~/.claude/skills/planning-with-files/SKILL.md.

What does planning-with-files do?

It runs a task through three markdown files: a phased plan, research notes, and the final deliverable. The agent re-reads the plan before decisions and tracks progress with checkboxes.

How is it different from prd-planner?

This one covers general organisation and research, with no PRD involved. Use prd-planner when the work is PRD-specific.

Source text

SKILL.md · MIT
---
name: planning-with-files
description: Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
metadata:
  hooks:
    after_complete:
      - trigger: session-logger
        mode: auto
        reason: "Log planning activity"
---

# 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:

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

### The Workflow Loop

```text
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
```

## When to Use

**Use this pattern for:**
- Multi-step tasks (3+ steps)
- Research tasks
- Building/creating projects
- Tasks spanning many tool calls
- Anything requiring organization

**Skip for:**
- Simple questions
- Single-file edits
- Quick lookups

## Installation

This skill is typically installed globally at `~/.claude/skills/planning-with-files/`.

From this repository:

```bash
ln -s /path/to/agent-playbook/skills/planning-with-files ~/.claude/skills/planning-with-files
```

If you prefer the standalone workflow, see the upstream repository in the Links section.

## The Manus Principles

| Principle | Implementation |
|-----------|----------------|
| Filesystem as memory | Store in files, not context |
| Attention manipulation | Re-read plan before decisions |
| Error persistence | Log failures in plan file |
| Goal tracking | Checkboxes show progress |
| Append-only context | Never modify history |

## Example

**You:** "Research the benefits of TypeScript and write a summary"

**Claude creates:**

```markdown
# Task Plan: TypeScript Benefits Research

## Goal
Create a research summary on TypeScript benefits.

## Phases
- [x] Phase 1: Create plan ✓
- [ ] Phase 2: Research and gather sources (CURRENT)
- [ ] Phase 3: Synthesize findings
- [ ] Phase 4: Deliver summary

## Status
**Currently in Phase 2** - Searching for sources
```

## Links

- [GitHub Repository](https://github.com/OthmanAdi/planning-with-files)
- [Context Engineering for AI Agents](https://manus.im/de/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-Manus)

© zhaono1 · MIT · zhaono1/agent-playbook

Similar skills

All skills for Agent setup: memory, context, orchestration →

planning-with-files by other authors comes first.

planning-with-files OthmanAdi Keeps a task plan, findings and progress in project Markdown files. It suits agent work that needs 5+ tool calls. CX Codex +1 47,000installs planning-with-files sickn33 Keeps task context in markdown files inside the project folder, turning disk storage into agent working memory. Useful for multi-step builds and research tasks. CX Codex +1 933installs planning-with-files Galaxy-Dawn Stores an agent's working memory in disk files. Helpful for multi-step tasks across multiple tool calls where chat context might degrade. CX Codex +1 368installs planning mblode Writes and reviews executable implementation plans grounded in repository evidence, with vertical slices and verification criteria. Useful before a big change. CX Codex +1 446installs planning-cadence RefoundAI A skill that sets up planning across annual, quarterly and weekly horizons. Useful when strategy exists but plans keep slipping. CX Codex +1 411installs concise-planning davila7 Turns a coding request into one plan of atomic steps. Useful when you want the scope agreed before anyone edits files. 117installs planning-and-task-breakdown addyosmani Breaks specifications into small, testable tasks with clear acceptance criteria. Prevents agents from jumping straight into coding before dependencies and risks are mapped. CX Codex +1 64,300installs agent-organizer VoltAgent Community Breaks down complex projects into subtasks, maps them to available subagents, and writes an execution plan in Markdown. Useful for coordinating multi-agent setups. 562installs blueprint affaan-m Turns a one-line objective into a step-by-step construction plan: PR-sized steps, a dependency graph, parallel branches and an adversarial review pass. CX Codex +1 4,600installs

From the same set18

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor