DBDelve
Dive deep into your data. A fast, native, multi-engine database client written in Rust. Free and open source, no telemetry.
翻訳待ち
Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project…
翻訳待ち
開発ツールShell · PythonGitHub @OthmanAdiオンライン所有者未確認
Have you tried it? One tap is enough. No sign-in needed.
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.
翻訳待ち
Loading the full README. The saved excerpt is shown below.
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.Read the full README ↗Code, documentation, and issue contributors. Select a portrait to open a GitHub profile or archived credit. Full credits.
| Fork | Author | What They Built |
|---|---|---|
| devis | @st01cs | Interview-first workflow, /devis:intv and /devis:impl commands, guaranteed activation |
| multi-manus-planning | @kmichels | Multi-project support, SessionStart git sync |
| plan-cascade | @Taoidle | Multi-level task orchestration, parallel execution, multi-agent collaboration |
| agentfund-skill | @RioTheGreat-ai | Crowdfunding for AI agents with milestone-based escrow on Base |
| openclaw-github-repo-commander | @wd041216-bit | 7-stage GitHub repo audit, optimization, and cleanup workflow for OpenClaw |
| planning-with-sysspec | @tianshan | Spec-first extension adding structured module specifications, spec deltas and validation matrices (source) |
| Project | What It Is |
|---|---|
| lincolnwan/Planning-with-files-copilot-agent | Entire Copilot agent repo built around the planning-with-files skill |
| cooragent/ClarityFinance | AI finance agent framework, Planning-with-Files approach directly credited |
| oeftimie/vv-claude-harness | Claude Code harness built on Manus-style persistent markdown planning |
| jessepwj/CCteam-creator | Multi-agent team orchestration skill using file-based planning |
| smallnest/langgraphgo: Manus Agent | Go implementation of the planning-with-files pattern with persistent task plans, research notes and output files (source) |
| a5c-ai/babysitter | SDK planning, execution, session-recovery and verification processes adapted from planning-with-files (source) |
| Registry | What It Is |
|---|---|
| buzhangsan/skill-manager | Bilingual (EN/中文) Claude Code skill hub; planning-with-files installable one-click |
| Project | Verified relationship |
|---|---|
| benchflow-ai/skillsbench | Bundles planning-with-files v2.1.2 in its organize-messy-files benchmark task (snapshot) |
| sickn33/agentic-awesome-skills | Cross-agent skill collection shipping an adapted planning-with-files copy, originally imported at v2.1.2 (import) |
Built something? Open an issue to get listed!
Full list of everyone who made this project better: CONTRIBUTORS.md.
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -g
All install methods: docs/installation.md.
Every coding agent loses its working memory when the context window resets. The plan does not have to die with it.
[!IMPORTANT] Most harnesses ship a to-do list that lives inside the context window. planning-with-files ships a plan that lives on disk, is re-injected every turn, is hash-attested, and can hold the agent's stop until the plan reports complete.
That is the difference between an agent that forgets after
/clear, compaction or a crash and one that resumes at the current phase. In the project's own measurements the plan on disk turned a 13.3-turn re-orientation into 5.0 turns, and the skill won 3 of 3 blind A/B comparisons (numbers and limits). Every mechanism below is a file on disk plus a hook, so it works the same on hour ten as on turn one.
Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)
→ Anything important gets written to disk.
The skill keeps your plan, findings, and progress in your project:
your-project/
├── task_plan.md ← phases + checkboxes; the resume point after /clear
├── findings.md ← research notes and decisions, appended as you go
└── progress.md ← session log and test results
Parallel tasks get isolated directories instead: .planning/YYYY-MM-DD-slug/ with the same three files, selected via .active_plan (v2.36.0+). Plain markdown, gitignored by default, no runtime state anywhere else.
This is the beginning of the README. Read the rest at the original. Read the full README ↗