Agent skill · operations · sundial-org
planning-with-files
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
Why this skill is useful
Adds executable scripts for session recovery and task management that enhance the AI's capability to handle complex multi-step tasks.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." FIRST: Check for Previous Session (v2.2.0) Before starting work, check for unsynced context from a previous session: If catchup report shows unsynced context: 1. Run git diff --stat to see actual code changes 2. Read current planning files 3. Update planning files based on catchup + git diff 4. Then proceed with task Important: Where Files Go Templates are in ${CLAUDEPLUGINROOT}/templates/ Your planning files go in your project directory Location What Goes There ---------- ----------------- Skill directory (${CLAUDEPLUGINROOT}/) Templates, scripts, reference docs Your project directory taskplan.md, findings.md, progress.md Quick Start Before ANY complex task: 1. Create taskplan.md — Use templates/taskplan.md as reference 2. Create findings.md — Use templates/findings.md as reference 3. Create progress.md — Use templates/progress.md as reference 4. Re-read plan before decisions — Refreshes goals in attention window 5. Update after each phase — Mark complete, log errors Note: Planning files go in your project root, not the skill installation folder. The Core Pattern File Purposes File Purpose When to Update ------ --------- ---------------- taskplan.md Phases, progress, decisions After each phase findings.md Research, discoveries After ANY discovery progress.md Session log, test results Throughout session Critical Rules 1. Create Plan First Never start a complex task without taskplan.md. Non-negotiable. 2. The 2-Action Rule "After every 2 view/browser/search operations, IMMEDIATELY save key findings to text files." This prevents visual/multimodal information from being lost. 3. Read Before Decide Before major decisions, read the plan file. This keeps goals in your attention window. 4. Update After Act After completing any phase: Mark phase status: inprogress → complete Log any errors encountered Note files created/modified 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/planning-with-files