planning-with-files

To maintain task planning context for complex workflows, use a system that creates persistent markdown files like task_plan.md, findings.md, and progress.md to sync goals, decisions, and discoveries across iterative tool calls.

Yes, you can automate planning file creation for large research projects using included scripts and activation hooks that trigger the initialization of task_plan.md, findings.md, and progress.md files automatically.

The best way to track progress across multiple tool calls is by maintaining a persistent progress.md file that records session progress, preventing context drift as you execute iterative decisions throughout the project.

You need a root directory containing a SKILL.md frontmatter file with name and description, and you can optionally create scripts, references, and assets directories to support your planning workflows.

Use persistent markdown planning files instead of standard tracking for complex, multi-step activities like large feature initiatives or research projects requiring many tool calls, where context drift and iterative decisions are likely.