Individual skill
planning-with-files
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.
.gemini/skills/planning-with-files/SKILL.md
Source commit 2362ca385ad74f061aa0e7b73f56543a4b7e6df2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27,989
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: gemini-cli
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- manus Repository topic
- agent-skills Repository topic
- planning Repository topic
- autonomous-agents Repository topic
- codex Repository topic
- cursor Repository topic
- multi-agent-systems Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesSKILL.mdcore · 13,885 bytesreferences/examples.mddoc · 4,518 bytesreferences/plan-inventory.mddoc · 9,565 bytesreferences/reference.mddoc · 8,455 bytesscripts/attest-plan.ps1runs · 26,917 bytesscripts/attest-plan.shruns · 14,701 bytesscripts/check-complete.ps1runs · 12,857 bytesscripts/check-complete.shruns · 13,730 bytesscripts/init-session.ps1runs · 19,396 bytesscripts/init-session.shruns · 15,800 bytesscripts/plan-doctor.shruns · 9,248 bytesscripts/resolve-plan-dir.ps1runs · 11,785 bytesscripts/resolve-plan-dir.shruns · 15,717 bytesscripts/session-catchup.pyruns · 37,323 bytesscripts/set-active-plan.ps1runs · 43,697 bytesscripts/set-active-plan.shruns · 39,513 bytestemplates/analytics_findings.mddoc · 1,803 bytestemplates/analytics_task_plan.mddoc · 2,581 bytestemplates/findings.mddoc · 1,161 bytestemplates/loop.mddoc · 2,143 bytestemplates/progress.mddoc · 1,547 bytestemplates/task_plan.mddoc · 2,257 bytes
Read excerpt
# 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:
1. If `task_plan.md` exists, read `task_plan.md`, `progress.md`, and `findings.md` immediately.
2. 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:
```bash