planning-with-files

Topics in the source

• Planning with Files
• Important: Where Files Go
• Quick Start
• The Core Pattern
• File Purposes
• Critical Rules
• 1. Create Plan First
• 2. The 2-Action Rule

Work like Manus: Use persistent markdown files as your "working memory on disk." When using this skill: Templates are stored in the skill directory at ${CLAUDEPLUGINROOT}/templates/ Your planning files (taskplan.md, findings.md, progress.md) should be created in your project directory — the folder where you're working | Location | What Goes There | |----------|-----------------| | Skill directory (${CLAUDEPLUGINROOT}/) | Templates, scripts, reference docs | | Your project directory | taskplan.md, findings.md, progress.md | This ensures your planning files live alongside your code, not buried in the skill installation folder. Before ANY complex task: 1. Create taskplan.md in your project — Use templates/taskplan.md as reference 2. Create findings.md in your project — Use templates/findings.md as reference 3. Create progress.md in your project — 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: All three planning files should be created in your current working directory (your project root), not in the skill's installation folder. | File | Purpose | When to Update |

This is an excerpt. Refer to the complete source and its current requirements.