planning-with-files

Files (9)

• SKILL.md
• examples.md
• reference.md
• check-complete.ps1 · scripts/
• init-session.ps1 · scripts/
• session-catchup.ps1 · scripts/
• findings.md · templates/
• progress.md · templates/
• task_plan.md · templates/

SKILL.md (first lines)

# Planning with Files

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

## FIRST: Check for Previous Session (v2.2.0)

**Before starting work**, check for unsynced context from a previous session:

```bash
# Windows Git Bash (MSYS2)
powershell -NoProfile -File "$HOME/.claude/skills/planning-with-files/scripts/session-catchup.ps1" "$(pwd)"
```

```powershell
# Windows PowerShell
& "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\session-catchup.ps1" (Get-Location)
```

If catchup report shows unsynced context:
1. Run `git diff --stat` to see actual code changes
2. Read current planning files
3. Update planning files based on catchup + git diff
4. Then proceed with task

## Important: Where Files Go

- **Templates** are in `${CLAUDE_PLUGIN_ROOT}/templates/`
- **Your planning files** go in **`Task/` under your project directory**

| Location | What Goes There |
|----------|-----------------|
| Skill directory (`${CLAUDE_PLUGIN_ROOT}/`) | Templates, scripts, reference docs |
| Your project directory | `Task/task_plan.md`, `Task/findings.md`, `Task/progress.md` |

## Quick Start

Before ANY complex task:

1. **Create `Task/task_plan.md`** — Use [templates/task_plan.md](templates/task_plan.md) as reference
2. **Create `Task/findings.md`** — Use [templates/findings.md](templates/findings.md) as reference
3. **Create `Task/progress.md`** — Use [templates/progress.md](templates/progress.md) as reference
4. **Re-read plan before decisions** — Refreshes goals in attention window
5. **Update after each phase** — Mark complete, log errors

> **Note:** Planning files go in `Task/` under your project root, not the skill installation folder.

## The Core Pattern

```
Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)

→ Anything important gets written to disk.
```

## File Purposes

| File | Purpose | When to Update |
|------|---------|----------------|
| `Task/task_plan.md` | Phases, progress, decisions | After each phase |
| `Task/findings.md` | Research, discoveries | After ANY discovery |
| `Task/progress.md` | Session log, test results | Throughout session |

## Critical Rules

### 1. Create Plan First
Never start a complex task without `Task/task_plan.md`. Non-negotiable.

### 2. The 2-Action Rule
> "After every 2 view/browser/search operations, IMMEDIATELY save key findings to text files."

This prevents visual/multimodal information from being lost.

### 3. Read Before Decide
Before major decisions, read the plan file. This keeps goals in your attention window.

### 4. Update After Act
After completing any phase:
- Mark phase status: `in_progress` → `complete`
- Log any errors encountered
- Note files created/modified

### 5. Log ALL Errors
Every error goes in the plan file. This builds knowledge and prevents repetition.

```markdown
## Errors Encountered
| Error | Attempt | Resolution |
|-------|---------|------------|
| FileNotFoundError | 1 | Created default config |
| API timeout | 2 | Added retry logic |
```

### 6. Never Repeat Failures
```
if action_failed:
    next_action != same_action
```
Track what you tried. Mutate the approach.

## The 3-Strike Error Protocol

```
ATTEMPT 1: Diagnose & Fix
  → Read error carefully
  → Identify root cause
  → Apply targeted fix

ATTEMPT 2: Alternative Approach
  → Same error? Try different method
  → Different tool? Different library?
  → NEVER repeat exact same failing action

ATTEMPT 3: Broader Rethink
  → Question assumptions
  → Search for solutions
  → Consider updating the plan

AFTER 3 FAILURES: Escalate to User

From bd-dxg/my-pi, AGPL-3.0.

More from bd-dxg/my-pi