Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
The 'pi-planning-with-files' skill implements a Manus-style file-based approach to project planning and task tracking. It leverages persistent markdown files, enabling users to organize and track complex tasks across multiple phases. The skill ensures that users have a structured workflow for handling multi-step projects, research tasks, or work that requires numerous tool interactions (5+ calls). By using markdown files such as 'task_plan.md', 'findings.md', and 'progress.md', users can maintain a clear, evolving record of their tasks and discoveries, ensuring they stay organized and on track throughout the project lifecycle.
The key features of this skill include session recovery via automatic syncing of unsynced context, file-based planning and discovery logging, and an error tracking protocol to prevent repeated failures. The workflow includes creating specific markdown files before beginning a task, updating them after each phase or discovery, and logging errors meticulously to build knowledge over time. It also encourages a structured approach to problem-solving with the '3-strike error protocol'. This skill is ideal for project managers, researchers, developers, and anyone working on complex, multi-step tasks requiring extensive planning and continuous feedback loops.
You can check for unsynced context by running the session-catchup.py script from the 'scripts/' directory in the skill folder. The script will provide a report of any unsynced context.
If the session-catchup.py script is missing, simply ask Pi to locate it for you by saying: 'Run the session-catchup.py script from the planning-with-files skill'.
Your project files, including 'task_plan.md', 'findings.md', and 'progress.md', should be stored in your project directory, not in the skill installation folder.
Errors should be logged immediately in the plan file. Each error should be tracked with details on attempts and resolutions. Use the 3-strike error protocol to manage repeated issues and escalate after three failed attempts.
Quick Setup:
.claude/skills/Repository
othmanadi/planning-with-files