| name | planning-with-files |
| description | Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; Gemini lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. The session-end hook reports status only; it does not request continuation or run commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls. |
| metadata | {"version":"2.43.0","hooks":"Configured in .gemini/settings.json (SessionStart, BeforeTool, AfterTool, BeforeModel)"} |
Planning with Files
Work like Manus: Use persistent markdown files as your "working memory on disk."
FIRST: Restore Project State
Before doing anything else, check if planning files exist and read them:
- If
task_plan.md exists, read task_plan.md, progress.md, and findings.md immediately.
- Run
git diff --stat to see code changes that may not yet be recorded in the planning files.
Automatic recovery stops there. The following optional command reads same-project local session records and emits aggregate counts only:
python3 .gemini/skills/planning-with-files/scripts/session-catchup.py --metadata "$(pwd)" || python .gemini/skills/planning-with-files/scripts/session-catchup.py --metadata "$(pwd)"