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: ```bash # Linux/macOS $(command -v python3 || command -v python) ${CLAUDE_PLUGIN_ROOT}/scripts/session-catchup.py "$(pwd)" ``` ```powershell # Windows PowerShell & (Get-Command python -ErrorAction SilentlyContinue).Source "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\session-catchup.py" (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 **your project directory** | Location | What Goes There | |----------|-----------------| | Skill directory (`${CLAUDE_PLUGIN_ROOT}/`) | 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. **Re-read plan before decisions** — Refre...