Practical overview
When it fits
Use it when an AI coding task spans multiple turns or needs durable project-local state rather than relying only on conversation context.
Who it is for
- Developers using AI coding agents
- Teams handling long-running coding tasks
- Builders who need file-backed task state and session recovery
Documented uses
- Maintain persistent plans, findings and progress across agent turns
- Recover coding-task context after /clear, crashes, compaction or other context loss
- Re-inject selected planning context during a session
- Check planned work before declaring a task complete
Requirements & limits
The project is a public, active, MIT-licensed repository. The supplied description lists CLI, cloud, self-hosted and server environments and names Claude Code, Codex, Cursor and OpenCode as supported agent environments. Installation and configuration details are not specified here.
- State is stored in three named Markdown files: task_plan.md, findings.md and progress.md.
- Lifecycle hooks re-inject selected planning context on each turn.
- Recovery covers context loss scenarios including /clear, crashes and compaction.
- A completion gate is included for deterministic task completion.
- A customized file schema is Likely compatible, but would require undocumented hook or parsing changes.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Planning With Files through the Agent Skills route
Add the planning skill, scripts, and templates to a supported coding-agent workflow.
Before you start
- A coding agent that reads Agent Skills installations.
- Node.js tooling capable of running npx.
- A project where persistent planning files can be stored.
Steps
Run the command below.
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -gStart a supported coding agent such as Codex, Cursor, or OpenCode.
Trigger the skill by typing
/planwhere the host supports the plugin route, or ask the agent to plan the task.Use the resulting
task_plan.md,findings.md, andprogress.mdfiles as the persistent task-state documents.
Expected outcome
The planning skill and its files are installed for use in long-running coding tasks, with planning state stored on disk.
Guide limitations
- The Agent Skills route provides the skill but not slash commands.
- The evidence does not document exact configuration steps for each supported agent.
- The package route does not register hooks on its own.
- Automatic recovery reads project files only; session-record replay requires explicit catchup mode.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Planning With Files | Maintain persistent plans, findings and progress across agent turns | CLI, Cloud, Self-hosted, Server | The project is a public, active, MIT-licensed repository. The supplied description lists CLI, cloud, self-hosted and server environments and names Claude Code, Codex, Cursor and OpenCode as supported agent environments. Installation and configuration details are not specified here. |
| Spectra | Clarify requirements and compare approaches before proposing a change. | CLI, Desktop | The README lists a macOS and Windows desktop app, and a Homebrew installation for macOS. The CLI is published through npm and requires Node.js 22.14 or newer. |
| Skills — michaelshimeles | Install reusable task-specific skills into a coding-agent setup. | CLI | The repository README provides an npx installation command for most coding agents and describes automatic or explicit skill invocation in Claude Code. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- OthmanAdi/planning-with-files · Official homepage title · retained in its source language

