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; 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. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.
.hermes/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)
- 28,000
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- 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 · 15,590 bytesSKILL.mdcore · 15,590 bytesSKILL.mdcore · 15,590 bytesSKILL.mdcore · 15,590 bytesSKILL.mdcore · 15,590 bytesSKILL.mdcore · 15,590 bytesplan-inventory.mddoc · 9,565 bytesscripts/check-complete.ps1runs · 1,985 bytesscripts/check-complete.shruns · 1,923 bytesscripts/check-continue.shruns · 1,013 bytesscripts/init-session.ps1runs · 5,261 bytesscripts/init-session.shruns · 5,128 bytesscripts/session-catchup.pyruns · 22,467 bytesscripts/set-active-plan.ps1runs · 43,697 bytesscripts/set-active-plan.shruns · 39,513 bytesscripts/sync-ide-folders.pyruns · 9,718 bytestemplates/analytics_findings.mddoc · 1,668 bytestemplates/analytics_task_plan.mddoc · 3,041 bytestemplates/findings.mddoc · 1,039 bytestemplates/progress.mddoc · 1,541 bytestemplates/task_plan.mddoc · 2,257 bytes
Read excerpt
> Hermes note: lifecycle automation for this skill comes from the Hermes adapter plugin in `.hermes/plugins/planning-with-files/`. Install it with `hermes plugins install OthmanAdi/planning-with-files/.hermes/plugins/planning-with-files`, then `hermes plugins enable planning-with-files`. Full guide: docs/hermes.md in the repository.
# 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 (in the project root, or in the active `.planning/<plan>/` directory), read `task_plan.md`, `progress.md`, and `findings.md` immediately. The `planning_with_files_status` tool or `/pwf-status` names the active plan.
When several plans are available, use `planning_with_files_select` with the exact `.planning/` directory name and project `cwd`, or an absolute plan-directory path. The selection belongs to this Hermes conversation. A successful read of a named plan's `task_plan.md` also selects it when this conversation is unbound; reading another plan for reference does not switch an existing selection.
2. Run `git diff --stat` to see code changes that may not yet be recorded in the planning files.