planning-with-fileslisted

# Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." ## Runtime Portability The workflow in this document is the portable contract. Claude Code can additionally execute the frontmatter hooks; Codex and OpenCode may ignore those fields, so the agent must perform the same read-before-work and update-after-phase steps explicitly. Resolve this installed skill from the runtime's skill metadata when possible. In shell examples, the setup fallback is `~/.agents/skills/planning-with-files`, which points to the same source as Claude's skill root. ## FIRST: Restore Context (v2.2.0) **Before doing anything else**, check if planning files exist and read them: 1. If `task_plan.json` exists, read the three canonical JSON files first; generated Markdown views may be read for orientation but must never be edited. Legacy Markdown-only sessions remain readable and should be migrated deliberately. 2. Then check for unsynced context from a previous session: ```bash # Linux/macOS SKILL_DIR="${CLAUDE_SKILL_DIR:-$HOME/.agents/skills/planning-with-files}" $(command -v python3 || command -v python) "$SKILL_DIR/scripts/session-catchup.py" "$(pwd)" ``` ```powershell # Windows PowerShell & (Get-Command python -ErrorAction SilentlyContinue).Source "$env:USERPROFILE\.claude\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.