Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →minicoohei/planning-with-files
複雑なタスクをファイルベースで計画管理するスキル。task_plan.md、findings.md、progress.mdを作成。 「計画を立てて」「タスクを整理して」「プランニング」等のリクエストで発動。
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 5 more in the full report
7 fixed4 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
After recovering context, you need to verify 'What have I done during this session?'. Which file serves as the log for session history and command outputs?
| Checked | Without skill | With skill |
|---|---|---|
| References progress.md as the session log source | 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 starting work, check for unsynced context from a previous session:
# Linux/macOS/WSL
$(command -v python3 || command -v python) ${CLAUDE_PLUGIN_ROOT}/scripts/session-catchup.py "$(pwd)"
If catchup report shows unsynced context:
git diff --stat to see actual code changes${CLAUDE_PLUGIN_ROOT}/templates/| Location | What Goes There |
|---|---|
Skill directory (${CLAUDE_PLUGIN_ROOT}/) | Templates, scripts, reference docs |
| Your project directory | task_plan.md, findings.md, progress.md |
Before ANY complex task:
task_plan.md — Use templates/task_plan.md as referencefindings.md — Use templates/findings.md as referenceprogress.md — Use templates/progress.md as referenceNote: Planning files go in your project root, not the skill installation folder.
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.