planning-with-files

> 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. 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 # Linux/macOS — auto-detects the Hermes home (HERMES_HOME or the platform default) SKILL_DIR="${HERMES_HOME:-$HOME/.hermes}/skills/planning-with-files" [ -d "$SKILL_DIR" ] || SKILL_DIR="${LOCALAPPDATA:-}/hermes/skills/planning-with-files" $(command -v python3 || command -v python) "${SKILL_DIR}/scripts/session-catchup.py" --metadata "$(pwd)" ``` ```powershell # Windows PowerShell — native Windows Hermes keeps its home under %LOCALAPPDATA%\hermes $HermesDi...