Planning With Files
A planning skill that keeps three Markdown files on disk for a multi-step task: a task plan, a findings log and a progress log. Lifecycle hooks read the plan back into the agent's context on each turn and check completion before the agent stops, so work can resume after the context is cleared or a session ends. The same skill is packaged for many agent hosts and translated into several languages. Aimed at people running long coding or research tasks with an agent who want the plan to survive across sessions.
- Task planning
Source: OthmanAdi/planning-with-files · pinned commit 3cbb7dc
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Keep durable task state without confusing it with completed work
Files can preserve plans and findings between sessions. They help only when observations, decisions and unfinished tasks are recorded accurately and ownership is clear.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
Consider this entry for a task that spans sessions and needs a durable plan, findings and progress record. The README describes file-based state and host lifecycle features; persistent documents can reduce the need to reconstruct decisions from a long conversation.
When to choose something else
For a short answer, maintaining several state files is unnecessary overhead. For longer work, do not mark a planned check as passed merely because the plan was written. Parallel workers editing the same state can also lose decisions unless ownership and merge rules are explicit.
What to provide and what to expect
Provide the objective, current evidence, open decisions and authorized next steps. Expect persistent documents separating planned work, discovered facts and actual progress. Each completed claim should point to a concrete artifact or check result that another session can inspect.
Tools, permissions and boundaries
Persistent state needs scoped file writes. Automatic context injection or lifecycle hooks require compatible host setup and should not be assumed from plain text instructions. Keep credentials and private source bodies out of broadly shared task records.
The tradeoff and an alternative
A single handoff note can be enough if the task has few decisions. Multiple state files help when the distinctions remain useful across interruptions. Their tradeoff is synchronization: stale progress can be worse than no record because it invites confident continuation from incorrect premises.
A small acceptance exercise
Proposed exercise: stop a task after one completed check and one unresolved decision, then resume from the files alone. Confirm the next session distinguishes those states and does not repeat or skip work. If hooks are expected, verify their activation rather than assuming the files enabled them.
Source, version and what was actually read
The pinned README opening description of persistent files and lifecycle features was read. Hook implementations, recovery behavior and benchmark claims were not evaluated. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: 3cbb7dc
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.