bd-dxg/my-pi/planning-with-files

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:

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

# 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

Quick Start

Before ANY complex task:

1. Create `Task/task_plan.md` — Use templates/task_plan.md as reference
2. Create `Task/findings.md` — Use templates/findings.md as reference
3. Create `Task/progress.md` — Use 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

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.

## 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
  → Explain what you tried
  → Share the specific error
  → Ask for guidance

Read vs Write Decision Matrix

The 5-Question Reboot Test

If you can answer these, your context management is solid:

When to Use This Pattern

Use 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

Templates

Copy these templates to start:

• templates/task_plan.md — Phase tracking
• templates/findings.md — Research storage
• templates/progress.md — Session logging

Scripts

Helper scripts for automation:

• scripts/init-session.sh — Initialize all planning files
• scripts/check-complete.sh — Verify all phases complete
• scripts/session-catchup.ps1 — Recover context from previous session (v2.2.0)

Advanced Topics

• Manus Principles: See reference.md
• Real Examples: See examples.md

Security Boundary

This skill uses a PreToolUse hook to re-read Task/task_plan.md before every tool call. Content written to Task/task_plan.md is injected into context repeatedly — making it a high-value target for indirect prompt injection.

Anti-Patterns