Othmanadi Planning With Files
othmanadi-planning-with-files is a Claude Code plugin for the Build phase that implements Manus-style persistent markdown planning with hooks and on-disk progress tracking.
by OthmanAdi · github.com/OthmanAdi/planning-with-files
Run Manus-style persistent markdown planning in Claude Code so specs, progress, and knowledge survive across long solo-build sessions.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install othmanadi-planning-with-files@OthmanAdi/planning-with-filesBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:OthmanAdi/planning-with-files") and the paste-ready config with skillselion.get_install_config("plugin:OthmanAdi/planning-with-files").
What it does
The othmanadi-planning-with-files Claude Code plugin packages a skill that treats markdown files as the system of record for agent planning—the same persistent, inspectable pattern popularized in Manus-style workflows. Solo builders installing it gain a repeatable way to start a feature: write or extend plan files, let Claude update progress through hooks, and keep decisions versionable in the repo instead of buried in conversation history. It shines when projects run for days or weeks, when you hand off between sessions, or when you want Claude to follow a structured checklist without losing thread. The plugin count is one focused capability rather than a broad marketplace. Expect to pair it with your own repo conventions (where plans live, naming, DONE markers). It is intermediate in practice because you must discipline the agent to read files first and respect your planning schema—but the payoff is calmer builds, clearer scope during validation, and easier iteration during operate.
Highlights
- Single-plugin bundle implementing persistent markdown planning inspired by the widely cited Manus workflow pattern.
- Uses files plus hooks for progress tracking and knowledge storage instead of ephemeral chat-only plans.
- Supports integration-style workflows: plan on disk, agent reads/writes state, you audit diffs like real PM docs.
- Repo positioning references the Manus-style planning approach associated with a major acquisition narrative—useful menta
- Keywords emphasize planning, persistent storage, markdown, tracking, and hooks—not one-off code snippets.
Why builders use it
Long Claude Code sessions lose the plan when context resets, so solo builders re-explain scope and repeat mistakes.
After install, planning lives in markdown files with tracked progress so each session continues from an auditable plan instead of chat memory.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 18.1k stars, 0 votes.
FAQ
Who is othmanadi-planning-with-files for?
Solo builders on Claude Code who want durable markdown plans, progress tracking, and hook-driven updates across sessions.
When should I use othmanadi-planning-with-files?
Use it before and during any non-trivial build or scope exercise whenever the plan must survive context limits and be reviewable in git.
How do I add othmanadi-planning-with-files to my agent?
Install the OthmanAdi/planning-with-files plugin from the catalog, enable it in Claude Code, then invoke the planning skill and keep plan markdown in your project per the repo README.
Comments
Share how you use othmanadi-planning-with-files, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.