# Planning With Files

Use this by default for non-trivial multi-step work that needs persistent planning...

- Repository: https://github.com/Galaxy-Dawn/claude-scholar (5959 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Galaxy-Dawn/claude-scholar --skill planning-with-files -g -a claude-code -y`
Codex: `npx skills add Galaxy-Dawn/claude-scholar --skill planning-with-files -g -a codex -y`
Cursor: `npx skills add Galaxy-Dawn/claude-scholar --skill planning-with-files -g -a cursor -y`
Gemini CLI: `npx skills add Galaxy-Dawn/claude-scholar --skill planning-with-files -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Galaxy-Dawn/claude-scholar`

## Description

Use this by default for non-trivial multi-step work that needs persistent planning, progress tracking, or durable notes on disk. Trigger when a task will likely span multiple tool calls, research steps, verification loops, or enough context that the plan should not live only in transient chat memory.

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

This is not just an optional planning style. It should be the default persistence layer for complex Codex work.

Use it proactively when:

- the task will likely take more than a few tool calls
- progress needs to be tracked across phases
- findings or evidence must be preserved while working
- the task may branch, pause, or resume later
- relying on chat context alone would be fragile

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

The rest: https://github.com/Galaxy-Dawn/claude-scholar/blob/HEAD/skills/planning-with-files/SKILL.md