Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.
Passed 13 of 17 test cases with the skill, and 4 of 17 without it.
and 13 more in the full report
12 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have completed research in notes.md and updated our task_plan.md for a cloud security policy document. Where does the final polished document belong in the 3-file pattern?
| Checked | Without skill | With skill |
|---|---|---|
| Places final output in a dedicated deliverable markdown file | Missed | Passed |
The instructions your model reads when the skill loads.
Work like Manus: Use persistent markdown files as your "working memory on disk."
Before ANY complex task:
task_plan.md in the working directoryFor every non-trivial task, create THREE files:
| File | Purpose | When to Update |
|---|---|---|
task_plan.md | Track phases and progress | After each phase |
notes.md | Store findings and research | During research |
[deliverable].md | Final output | At completion |
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
Before each major action:
Read task_plan.md # Refresh goals in attention window
After each phase:
test cases passed, vs 4 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.