What problem does it solve? Long agent sessions lose track of goals because context windows are volatile and limited. This Skill implements Manus-style file-based planning, storing task plans, findings, and progress logs as markdown files on disk so work survives context resets, /clear commands, and compaction. ## Core Features & Use Cases - Persistent Planning Files: Creates and maintains task_plan.md, findings.md, and progress.md in your project directory as external working memory. - Session Recovery: A session-catchup script detects unsynced context from previous sessions after /clear, supporting Claude Code, Codex, and OpenCode session stores. - Parallel Plan Isolation: Supports multiple concurrent plans under .planning/<date>-<slug>/ directories with an active-plan pointer and PLAN_ID pinning. - Tamper Protection: Optional SHA-256 attestation locks the plan file so hooks block injection if the plan is modified without re-approval. - Use Case: When asked to plan a multi-phase research or refactoring project, the agent writes a phased task_plan.md first, logs discoveries to findings.md after every search, and updates progress.md after each phase so the work can resume cleanly at any point. ## Quick Start Ask the agent to plan out your multi-step project using planning files, for example: "Plan and track the backend refactor using task_plan.md, findings.md, and progress.md."
