planning-with-files
Work like Manus: Use persistent markdown files as your "working memory on disk."
Product ManagementProject & Program ManagementManagement & Team LeadershipExecutives & Strategy
Planning with Files
Work like Manus: Use persistent markdown files as your "working memory on disk."
Important: Where Files Go
When using this skill:
- Templates are stored in the skill directory at
${CLAUDE_PLUGIN_ROOT}/templates/ - Your planning files (
task_plan.md,findings.md,progress.md) should be created in your project directory — the folder where you're working
| Location | What Goes There |
|---|---|
Skill directory (${CLAUDE_PLUGIN_ROOT}/) | Templates, scripts, reference docs |
| Your project directory | task_plan.md, findings.md, progress.md |
This ensures your planning files live alongside your code, not buried in the skill installation folder.
Quick Start
Before ANY complex task:
- Create
task_plan.mdin your project — Use [templates/task_plan.md](templates/task_plan.md) as reference - Create
findings.mdin your project — Use [templates/findings.md](templates/findings.md) as reference - Create
progress.mdin your project — Use [templates/progress.md](templates/progress.md) as reference - Re-read plan before decisions — Refreshes goals in attention window
- Update after each phase — Mark complete, log errors
Note: All three planning files should be created in your current working directory (your project root), not in the skill's installation folder.
The Co
Subscribers only
The full skill, its 8 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | critical ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md, examples.md, reference.md, scripts/check-complete.sh, scripts/init-session.sh, templates/findings.md, templates/progress.md, templates/task_plan.md |
| Added | 2026-02-27 |
Related skills
blueprint
Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
decision-navigator
Guide stuck or overwhelmed users through targeted branching questions until they reach concrete next steps.
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
