planning-with-files

> Hermes note: lifecycle automation for this skill is provided by the Hermes adapter plugin in `.hermes/plugins/planning-with-files/`. # Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." ## FIRST: Restore Context (v2.2.0) **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. Then check for unsynced context from a previous session: ```bash # Linux/macOS $(command -v python3 || command -v python) "$HERMES_HOME/skills/planning-with-files/scripts/session-catchup.py" "$(pwd)" ``` ```powershell # Windows PowerShell & (Get-Command python -ErrorAction SilentlyContinue).Source "$env:HERMES_HOME\skills\planning-with-files\scripts\session-catchup.py" (Get-Location) ``` If catchup report shows unsynced context: 1. Run `git diff --stat` to see actual code changes 2. Read current planning files 3. Update planning files based on catchup + git diff 4. Then proceed with task ## Hermes Notes - Keep the original workflow below unchanged whenever possible. - In Hermes, the adapter plugin approximates lifecycle automation with `pre_llm_call` and `post_tool_call`. - Hermes currently has no full equivalent for the original `PreToolUse` behavior. - Hermes completion checking is surfaced by the adapter instead of a native stop-block hook. ## Important: Where Files Go - **Templates** are in `$HERMES_HOME/skills/plannin...