planning-with-files

Name: planning-with-files
Author: jarrodwatts

14installs121forks

How to install planning-with-files?

jarrodwatts/claude-code-config/planning-with-files

$npx -y skills add jarrodwatts/claude-code-config --skill planning-with-files

Installs into the current project.

Summary

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structur

Files · 1

View on GitHub

SKILL.md

1	# Planning with Files
2
3	Work like Manus: Use persistent markdown files as your "working memory on disk."
4
5	## Quick Start
6
7	Before ANY complex task:
8
9	1. Create `task_plan.md` in the working directory
10	2. Define phases with checkboxes
11	3. Update after each phase - mark [x] and change status
12	4. Read before deciding - refresh goals in attention window
13
14	## The 3-File Pattern
15
16	For every non-trivial task, create THREE files:
17
18	\| File \| Purpose \| When to Update \|
19	\|------\|---------\|----------------\|
20	\| `task_plan.md` \| Track phases and progress \| After each phase \|
21	\| `notes.md` \| Store findings and research \| During research \|
22	\| `[deliverable].md` \| Final output \| At completion \|
23
24	## Core Workflow
25
26	```
27	Loop 1: Create task_plan.md with goal and phases
28	Loop 2: Research → save to notes.md → update task_plan.md
29	Loop 3: Read notes.md → create deliverable → update task_plan.md
30	Loop 4: Deliver final output
31	```
32
33	### The Loop in Detail
34
35	Before each major action:
36	```bash
37	Read task_plan.md # Refresh goals in attention window
38	```
39
40	After each phase:
41	```bash
42	Edit task_plan.md # Mark [x], update status
43	```
44
45	When storing information:
46	```bash
47	Write notes.md # Don't stuff context, store in file
48	```
49
50	## task_plan.md Template
51
52	Create this file FIRST for any complex task:
53
54	```markdown
55	# Task Plan: [Brief Description]
56
57	## Goal
58	[One sentence describing the end state]
59
60	## Phases
61	- [ ] Phase 1: Plan and setup
62	- [ ] Phase 2: Research/gather information
63	- [ ] Phase 3: Execute/build
64	- [ ] Phase 4: Review and deliver
65
66	## Key Questions
67	1. [Question to answer]
68	2. [Question to answer]
69
70	## Decisions Made
71	- [Decision]: [Rationale]
72
73	## Errors Encountered
74	- [Error]: [Resolution]
75
76	## Status
77	Currently in Phase X - [What I'm doing now]
78	```
79
80	## notes.md Template
81
82	For research and findings:
83
84	```markdown
85	# Notes: [Topic]
86
87	## Sources
88
89	### Source 1: [Name]
90	- URL: [link]
91	- Key points:
92	- [Finding]
93	- [Finding]
94
95	## Synthesized Findings
96
97	### [Category]
98	- [Finding]
99	- [Finding]
100	```
101
102	## Critical Rules
103
104	### 1. ALWAYS Create Plan First
105	Never start a complex task without `task_plan.md`. This is non-negotiable.
106
107	### 2. Read Before Decide
108	Before any major decision, read the plan file. This keeps goals in your attention window.
109
110	### 3. Update After Act
111	After completing any phase, immediately update the plan file:
112	- Mark completed phases with [x]
113	- Update the Status section
114	- Log any errors encountered
115
116	### 4. Store, Don't Stuff
117	Large outputs go to files, not context. Keep only paths in working memory.
118
119	### 5. Log All Errors
120	Every error goes in the "Errors Encountered" section. This builds knowledge for future tasks.
121
122	## When to Use This Pattern
123
124	Use 3-file pattern for:
125	- Multi-step tasks (3+ steps)
126	- Research tasks
127	- Building/creating something
128	- Tasks spanning multiple tool calls
129	- Anything requiring organization
130
131	Skip for:
132	- Simple questions
133	- Single-file edits
134	- Quick lookups
135
136	## Anti-Patterns to Avoid
137
138	\| Don't \| Do Instead \|
139	\|-------\|------------\|
140	\| Use TodoWrite for persistence \| Create `task_plan.md` file \|
141	\| State goals once and forget \| Re-read plan before each decision \|
142	\| Hide errors and retry \| Log errors to plan file \|
143	\| Stuff everything in context \| Store large content in files \|
144	\| Start executing immediately \| Create plan file FIRST \|
145
146	## Advanced Patterns
147
148	See [reference.md](reference.md) for:
149	- Attention manipulation techniques
150	- Error recovery patterns
151	- Context optimization from Manus
152
153	See [examples.md](examples.md) for:
154	- Real task examples
155	- Complex workflow patterns

People who liked this also viewed

6 picks

Type

planning-with-files

14installs121forks

View on GitHub

How to install planning-with-files?

jarrodwatts/claude-code-config/planning-with-files

$npx -y skills add jarrodwatts/claude-code-config --skill planning-with-files

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Planning with Files
2
3	Work like Manus: Use persistent markdown files as your "working memory on disk."
4
5	## Quick Start
6
7	Before ANY complex task:
8
9	1. Create `task_plan.md` in the working directory
10	2. Define phases with checkboxes
11	3. Update after each phase - mark [x] and change status
12	4. Read before deciding - refresh goals in attention window
13
14	## The 3-File Pattern
15
16	For every non-trivial task, create THREE files:
17
18	\| File \| Purpose \| When to Update \|
19	\|------\|---------\|----------------\|
20	\| `task_plan.md` \| Track phases and progress \| After each phase \|
21	\| `notes.md` \| Store findings and research \| During research \|
22	\| `[deliverable].md` \| Final output \| At completion \|
23
24	## Core Workflow
25
26	```
27	Loop 1: Create task_plan.md with goal and phases
28	Loop 2: Research → save to notes.md → update task_plan.md
29	Loop 3: Read notes.md → create deliverable → update task_plan.md
30	Loop 4: Deliver final output
31	```
32
33	### The Loop in Detail
34
35	Before each major action:
36	```bash
37	Read task_plan.md # Refresh goals in attention window
38	```
39
40	After each phase:
41	```bash
42	Edit task_plan.md # Mark [x], update status
43	```
44
45	When storing information:
46	```bash
47	Write notes.md # Don't stuff context, store in file
48	```
49
50	## task_plan.md Template
51
52	Create this file FIRST for any complex task:
53
54	```markdown
55	# Task Plan: [Brief Description]
56
57	## Goal
58	[One sentence describing the end state]
59
60	## Phases
61	- [ ] Phase 1: Plan and setup
62	- [ ] Phase 2: Research/gather information
63	- [ ] Phase 3: Execute/build
64	- [ ] Phase 4: Review and deliver
65
66	## Key Questions
67	1. [Question to answer]
68	2. [Question to answer]
69
70	## Decisions Made
71	- [Decision]: [Rationale]
72
73	## Errors Encountered
74	- [Error]: [Resolution]
75
76	## Status
77	Currently in Phase X - [What I'm doing now]
78	```
79
80	## notes.md Template
81
82	For research and findings:
83
84	```markdown
85	# Notes: [Topic]
86
87	## Sources
88
89	### Source 1: [Name]
90	- URL: [link]
91	- Key points:
92	- [Finding]
93	- [Finding]
94
95	## Synthesized Findings
96
97	### [Category]
98	- [Finding]
99	- [Finding]
100	```
101
102	## Critical Rules
103
104	### 1. ALWAYS Create Plan First
105	Never start a complex task without `task_plan.md`. This is non-negotiable.
106
107	### 2. Read Before Decide
108	Before any major decision, read the plan file. This keeps goals in your attention window.
109
110	### 3. Update After Act
111	After completing any phase, immediately update the plan file:
112	- Mark completed phases with [x]
113	- Update the Status section
114	- Log any errors encountered
115
116	### 4. Store, Don't Stuff
117	Large outputs go to files, not context. Keep only paths in working memory.
118
119	### 5. Log All Errors
120	Every error goes in the "Errors Encountered" section. This builds knowledge for future tasks.
121
122	## When to Use This Pattern
123
124	Use 3-file pattern for:
125	- Multi-step tasks (3+ steps)
126	- Research tasks
127	- Building/creating something
128	- Tasks spanning multiple tool calls
129	- Anything requiring organization
130
131	Skip for:
132	- Simple questions
133	- Single-file edits
134	- Quick lookups
135
136	## Anti-Patterns to Avoid
137
138	\| Don't \| Do Instead \|
139	\|-------\|------------\|
140	\| Use TodoWrite for persistence \| Create `task_plan.md` file \|
141	\| State goals once and forget \| Re-read plan before each decision \|
142	\| Hide errors and retry \| Log errors to plan file \|
143	\| Stuff everything in context \| Store large content in files \|
144	\| Start executing immediately \| Create plan file FIRST \|
145
146	## Advanced Patterns
147
148	See [reference.md](reference.md) for:
149	- Attention manipulation techniques
150	- Error recovery patterns
151	- Context optimization from Manus
152
153	See [examples.md](examples.md) for:
154	- Real task examples
155	- Complex workflow patterns

People who liked this also viewed

6 picks

Type