domains / families / agent-tooling / planning-with-files

planning-with-files

combined

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. Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

When to use

• Multi-step tasks (3+ steps)
• Research tasks
• Building/creating projects
• Tasks spanning many tool calls
• Anything requiring organization
• Simple questions
• Single-file edits
• Quick lookups

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three Vibe-Skills, skillsbench, and agentic-awesome-skills copies are near-identical reproductions of the same v2.1.2 procedure (task_plan.md, findings.md, progress.md, 2-Action Rule, 3-Strike Error Protocol, Read/Write matrix, 5-Question Reboot Test). The brycewang-stanford copy is a materially different v0.1.0 variant that uses a 3-file pattern (task_plan.md, notes.md, [deliverable].md), a 4-loop workflow, and inline templates, and it omits the 2-Action Rule, 3-Strike protocol, and Read/Write matrix. Because the copies overlap but each has material steps or constraints the others lack, and they disagree on file names and workflow, crowning one would hide a real alternative.