planning-with-files

Name: planning-with-files
Availability: InStock
Author: noobmastercn

Plan multi-step tasks using persistent on-disk planning files.

Updated Dec 17, 2025

Search Tags:#planning #markdown #progress #project-management #findings #task-plan

Ready to run

npx skills add https://github.com/noobmastercn/claude-skills --skill planning-with-files-noobmastercn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-with-files
Source: https://github.com/noobmastercn/claude-skills/tree/main/planning-with-files
Command: npx skills add https://github.com/noobmastercn/claude-skills --skill planning-with-files-noobmastercn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manus-style planning relies on memory, and complex tasks can outgrow context windows; planning with files provides persistent on-disk planning artifacts (task_plan.md, findings.md, progress.md) to keep goals visible across long, multi-tool tasks and research projects.

Core Features & Use Cases

Persistent planning artifacts: task_plan.md, findings.md, progress.md created in your project directory, with templates and guided structure to track goals, discoveries, and progress.
Structured workflow for complex tasks: phases, status, and iterative decisions; re-read the plan before decisions to refresh goals; log findings and progress over time.
On-demand templates and hooks: templates in the skill directory; hooks like PreToolUse and Stop to enforce completion checks.

Quick Start

Create a planning setup in your project by initializing task_plan.md, findings.md, and progress.md from the templates.

Frequently Asked Questions about planning-with-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan complex research projects without losing track of goals in long context windows?▼

Persistent planning files keep complex research goals visible across long workflows. By maintaining on-disk artifacts like task_plan.md, findings.md, and progress.md, you can track multi-step tasks without relying on memory or risking context window overflow.

What is the best way to track project findings and progress over many tool calls?▼

Tracking project findings over many tool calls requires structured markdown files. You can log discoveries in findings.md and update status in progress.md, ensuring iterative decisions are based on re-read, persistent data rather than volatile memory.

How do I set up a structured project management workflow using markdown files?▼

Setting up a structured project management workflow involves initializing markdown templates in your project directory. You create task_plan.md, findings.md, and progress.md from provided templates to guide phases, track status, and structure iterative decisions.

Can I enforce task completion checks for multi-step planning workflows?▼

Yes, you can enforce task completion checks using hooks. The setup includes PreToolUse and Stop hooks that validate completion, requiring you to re-read the plan and log progress before finalizing multi-step workflows.

Does file-based planning work for tasks requiring heavy iterative decisions?▼

File-based planning is designed specifically for tasks requiring heavy iterative decisions. By re-reading the persistent task plan before taking action, you refresh goals and ensure that every iterative decision aligns with the original project scope.