planning-with-files
NewImplements 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.
Summary
md) to manage complex, multi-step tasks.
- It helps developers break down large projects, track progress, and document findings systematically, reducing cognitive load and ensuring nothing is overlooked.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "planning-with-files": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/planning-with-files Refactor the authentication module to support OAuth2, including updating models, controllers, and tests
/planning-with-files Research and compare three cloud providers for our microservices deployment, considering cost, performance, and scalability
I need to set up a CI/CD pipeline for our monorepo. Use planning-with-files to create a step-by-step plan covering build, test, and deploy stages
Security Audits
Frequently Asked Questions
What is planning-with-files?
This skill implements a file-based planning system inspired by Manus, creating and maintaining structured markdown files (task_plan.md, findings.md, progress.md) to manage complex, multi-step tasks. It helps developers break down large projects, track progress, and document findings systematically, reducing cognitive load and ensuring nothing is overlooked.
How to install planning-with-files?
To install planning-with-files: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "planning-with-files": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is planning-with-files best for?
planning-with-files is a mcp categorized under General. It is designed for: planning, productivity. Created by davila7.
What can I use planning-with-files for?
planning-with-files is useful for: Planning and executing a multi-module software refactor with dependencies; Conducting a research project that requires gathering information from multiple sources and synthesizing findings; Managing a complex deployment pipeline with multiple environments and rollback steps; Breaking down a large feature implementation into granular, trackable subtasks; Coordinating a code review process across multiple pull requests with checklists; Documenting troubleshooting steps and solutions for a recurring production issue.