pyinx/ceo-skills-plugin/planning-with-files

Planning with Files

Work like Manus: Use persistent markdown files as your "working memory on disk."

Quick Start

Before ANY complex task:

1. Create `task_plan.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

The 3-File Pattern

For every non-trivial task, create THREE files:

Core Workflow

Loop 1: Create task_plan.md with goal and phases
Loop 2: Research → save to notes.md → update task_plan.md
Loop 3: Read notes.md → create deliverable → update task_plan.md
Loop 4: Deliver final output

The Loop in Detail

Before each major action:

Read task_plan.md  # Refresh goals in attention window

After each phase:

Edit task_plan.md  # Mark [x], update status

When storing information:

Write notes.md     # Don't stuff context, store in file

task_plan.md Template

Create this file FIRST for any complex task:

# Task Plan: [Brief Description]
 
## Goal
[One sentence describing the end state]
 
## Phases
-[ ] Phase 1: Plan and setup
-[ ] Phase 2: Research/gather information
-[ ] Phase 3: Execute/build
-[ ] Phase 4: Review and deliver
 
## Key Questions
1.[Question to answer]
2.[Question to answer]
 
## Decisions Made
-[Decision]: [Rationale]
 
## Errors Encountered
-[Error]: [Resolution]
 
## Status
**Currently in Phase X** - [What I'm doing now]

notes.md Template

For research and findings:

# Notes: [Topic]
 
## Sources
 
### Source 1: [Name]
-URL: [link]
-Key points:
  -[Finding]
  -[Finding]
 
## Synthesized Findings
 
### [Category]
-[Finding]
-[Finding]

Critical Rules

1. ALWAYS Create Plan First

Never start a complex task without task_plan.md. This is non-negotiable.

2. Read Before Decide

Before any major decision, read the plan file. This keeps goals in your attention window.

3. Update After Act

After completing any phase, immediately update the plan file:

• Mark completed phases with [x]
• Update the Status section
• Log any errors encountered

4. Store, Don't Stuff

Large outputs go to files, not context. Keep only paths in working memory.

5. Log All Errors

Every error goes in the "Errors Encountered" section. This builds knowledge for future tasks.

When to Use This Pattern

Use 3-file pattern for:

• Multi-step tasks (3+ steps)
• Research tasks
• Building/creating something
• Tasks spanning multiple tool calls
• Anything requiring organization

Skip for:

• Simple questions
• Single-file edits
• Quick lookups

Anti-Patterns to Avoid

Advanced Patterns

See reference.md for:

• Attention manipulation techniques
• Error recovery patterns
• Context optimization from Manus

See examples.md for:

• Real task examples
• Complex workflow patterns