pi-planning-with-files

# Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." ## FIRST: Restore Context **Before doing anything else**, check if planning files exist and read them: 1. If `task_plan.md` exists, read `task_plan.md`, `progress.md`, and `findings.md` immediately. 2. The extension automatically checks for unsynced context from a previous session. 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 `templates/` inside this skill - **Your planning files** go in **your project directory** | Location | What Goes There | |----------|-----------------| | Skill directory | Templates, scripts, reference docs | | Your project directory | `task_plan.md`, `findings.md`, `progress.md` | ## Quick Start Before ANY complex task: 1. **Create `task_plan.md`** — Use [templates/task_plan.md](templates/task_plan.md) as reference 2. **Create `findings.md`** — Use [templates/findings.md](templates/findings.md) as reference 3. **Create `progress.md`** — Use [templates/progress.md](templates/progress.md) as reference 4. **Wait for approval before execution** — In Pi, hooks stay passive until the user runs `/plan-execute` 5. **Re-read plan before decisions** — Refreshes goals in attention window 6. **Update after each phase** — Mark complete, log errors...