planning-with-files

OthmanAdi/planning-with-files is an open-source project by OthmanAdi: Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Install from npm, the Claude Code plugin marketplace, or npx skills. Codex, Cursor, OpenCode, 60+ agents.. Indexed here so it can be found — not resold.

It is free. Get it from the upstream repository: https://github.com/OthmanAdi/planning-with-files

From the project's own README (excerpt, reproduced for discovery under its MIT license):

Planning with Files   

The planning skill your agent cannot ignore. Not a prompt it might follow. A hook that fires every turn, a plan on disk that survives /clear , and 3 out of 3 blind A/B wins to show it works.

Your agent's context window dies. The plan does not.

Persistent file-based planning for AI coding agents and long-running agent tasks: the skill keeps taskplan.md , findings.md , and progress.md on disk. Activated lifecycle hooks inject selected project planning context, so the plan survives context loss, /clear , crashes, and compaction. Automatic recovery reads project files only. Reading same-project local agent session records for aggregate counts or bounded replay requires an explicit catchup mode. Installs across 60+ agents via the Agent Skills standard, with native plugins for Claude Code, Codex CLI, Pi, Hermes Agent, OpenCode and DeepSeek Harness.

See it survive /clear · Install · Long-running tasks · First-class hosts · Multi-agent · The numbers

Proof, comparisons and the repository reference are further down · Full install guide

---

Before and after /clear

Every coding agent loses its working memory when the context window resets. The plan does not have to die with it.

Without planning files

The agent re-reads the repo, asks you to restate the goal, and rediscovers work it already finished.

---

With planning-with-files

The transcript is illustrative; the ===BEGIN PLAN DATA=== block is the skill's real injection format, written into context by the UserPromptSubmit hook from taskplan.md on disk. In the project's internal recovery benchmark, a fresh session with the files on disk resumed in 5.0 turns on average against 13.3 for a raw agent (internal v1,…