planning-with-files

Topics in the source

• Planning with Files
• Quick Start
• The 3-File Pattern
• Core Workflow
• The Loop in Detail
• taskplan.md Template
• notes.md Template
• Critical Rules

Work like Manus: Use persistent markdown files as your "working memory on disk." Before ANY complex task: 1. Create taskplan.md in the working directory 2. Define phases with checkboxes 3. Update after each phase - mark [x] and change status 4. Read before deciding - refresh goals in attention window For every non-trivial task, create THREE files: | File | Purpose | When to Update | |------|---------|----------------| | taskplan.md | Track phases and progress | After each phase | | notes.md | Store findings and research | During research | | [deliverable].md | Final output | At completion | Before each major action: After each phase: When storing information: Create this file FIRST for any complex task: For research and findings: Never start a complex task without taskplan.md. This is non-negotiable. Before any major decision, read the plan file. This keeps goals in your attention window. After completing any phase, immediately update the plan file: Mark completed phases with [x] Update the Status section Log any errors encountered Large outputs go to files, not context. Keep only paths in working memory. Every error goes in the "Errors Encountered" section. This builds knowledge f

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