# Planning With Files

Transforms workflow to use Manus-style persistent markdown files for planning, progress...

- Repository: https://github.com/jarrodwatts/claude-code-config (1063 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-01-21
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add jarrodwatts/claude-code-config --skill planning-with-files -g -a claude-code -y`
Codex: `npx skills add jarrodwatts/claude-code-config --skill planning-with-files -g -a codex -y`
Cursor: `npx skills add jarrodwatts/claude-code-config --skill planning-with-files -g -a cursor -y`
Gemini CLI: `npx skills add jarrodwatts/claude-code-config --skill planning-with-files -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Planning with Files

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

## Quick Start

Before ANY complex task:

1. **Create `task_plan.md`** in the working directory
2. **Define phases** with checkboxes
3. **Update after each phase** - mark [x] and change status
4. **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:**
```bash
Read task_plan.md  # Refresh goals in attention window
```

**After each phase:**
```bash
Edit task_plan.md  # Mark [x], update status
```

**When storing information:**
```bash
Write notes.md     # Don't stuff context, store in file
```

## task_plan.md Template

Create this file FIRST for any complex task:

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

```markdown
# Notes: [Topic]

## Sources

### Source 1: [Name]
- URL: [link]
- Key points:
  - [Finding]
  - [Finding]

## Synthesized Findings

### [Category]
- [Finding]
- [Finding]
```

The rest: https://github.com/jarrodwatts/claude-code-config/blob/HEAD/skills/planning-with-files/SKILL.md