Where are the planning files stored?

All planning files (task_plan.md, findings.md, and progress.md) are created directly in your current project root directory, ensuring they live alongside your code for easy access.

When should I use the Planning with Files skill?

Use this skill for any complex task requiring more than five tool calls, multi-step research, or projects involving significant code modifications where state needs to persist.

What is the 3-strike error protocol?

It is a systematic approach to failures: first diagnose and fix, second try an alternative method, and third perform a broad rethink or search for solutions before finally escalating to the user for guidance.

How does this prevent AI context loss?

By writing plans and findings to physical files in your project directory, the skill creates a persistent 'disk' storage that Claude can re-read to refresh its memory, bypassing the limits of volatile context windows.

Manus-Style File Planning

Name: Manus-Style File Planning
Author: jukasdrj

byjukasdrj

•

Productivity & Workflow

Implements a persistent, file-based planning system to manage complex multi-step tasks and research projects within Claude Code.

About

This skill equips Claude with a robust 'working memory on disk' by utilizing markdown files for task orchestration and state management. Inspired by the Manus workflow, it ensures continuity and accuracy during complex engineering tasks or research by maintaining dedicated files for planning, findings, and progress tracking. By shifting critical context from the volatile context window to persistent storage, it prevents information loss, manages error recovery through a structured 3-strike protocol, and enforces rigorous documentation of discoveries across long sessions.

Key Features

Persistent markdown-based task orchestration using task_plan.md, findings.md, and progress.md
2-Action Rule for immediate persistence of research and multimodal findings
Standardized templates for research, phase tracking, and session logging
1 GitHub stars
Structured 3-Strike Error Protocol for systematic debugging and escalation
Automated PreToolUse hooks to refresh task context before major edits

Use Cases

Orchestrating complex refactors or multi-file migrations requiring more than 5 tool calls
Conducting deep-dive technical research where discoveries must be synthesized and saved
Managing long-running autonomous debugging sessions with a clear audit trail of attempts

About

Key Features

Persistent markdown-based task orchestration using task_plan.md, findings.md, and progress.md
2-Action Rule for immediate persistence of research and multimodal findings
Standardized templates for research, phase tracking, and session logging
1 GitHub stars
Structured 3-Strike Error Protocol for systematic debugging and escalation
Automated PreToolUse hooks to refresh task context before major edits

Use Cases

Orchestrating complex refactors or multi-file migrations requiring more than 5 tool calls
Conducting deep-dive technical research where discoveries must be synthesized and saved
Managing long-running autonomous debugging sessions with a clear audit trail of attempts