Planning with Files
Manus-style persistent task planning via task_plan.md / findings.md / progress.md on disk—keeps Claude anchored across long multi-step work.
Overview
Planning with Files is a Claude skill added to LimeDock Directories from recent community and vendor roundups. Manus-style persistent task planning via task_plan.md / findings.md / progress.md on disk—keeps Claude anchored across long multi-step work. This page covers install, how to invoke it, example prompts, prerequisites, and concrete use cases.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
/plugin marketplace add OthmanAdi/planning-with-filesOr clone and copy skills into `~/.claude/skills/`.
How to use it
Activates on complex multi-step tasks. Enforce plan-first, 2-action save rule, read-before-decide, update-after-act.
Example prompts
- “Use the Planning with Files skill for: Multi-hour refactors without goal drift”
- “Walk me through Planning with Files step by step, then execute on my project.”
- “Review my current approach and improve it using Planning with Files.”
- “Produce a reusable checklist for running Planning with Files on similar work.”
Use cases and examples
- Multi-hour refactors without goal drift
- Research→implement pipelines
- Session recovery after /clear
- 3-strike error protocol on stuck loops
- Team playbook trial of Planning with Files on a real workflow
Prerequisites
- Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
- Permission to install third-party skills — audit SKILL.md and scripts first
- Project context (CLAUDE.md / product notes) for better outputs
Tips
- Keep triggers specific so Planning with Files only fires when relevant.
- Audit SKILL.md and any bundled scripts before production use.
- Pair with verification (tests, review, screenshots) before shipping.
- Re-audit installed skills monthly to avoid context tax from unused packs.