planning-with-files-zht

Organizes complex multi-step tasks using persistent Markdown planning files.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill planning-with-files-zht-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-with-files-zht
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/plugins/cache/planning-with-files/planning-with-files/2.23.0/skills/planning-with-files-zht
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill planning-with-files-zht-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Long-running or multi-step tasks lose context when the conversation window fills up or the session is cleared. This Skill persists task state to disk as Markdown files so progress, findings, and decisions survive /clear and session restarts. ## Core Features & Use Cases - Persistent Planning Files: Creates and maintains task_plan.md, findings.md, and progress.md in your project directory as a durable working memory. - Automatic Session Recovery: Detects unsynced context from previous sessions via a catch-up script and lifecycle hooks that re-inject the plan before tool calls. - Failure Protocols: Enforces a three-attempt failure protocol, error logging, and a five-question restart test to keep long tasks on track. - Use Case: When asked to plan and execute a multi-phase project (research, implementation, testing, delivery), the Skill initializes the three planning files, tracks phase status, and resumes correctly after a context reset. ## Quick Start Ask the assistant to plan and break down your multi-step project using file-based planning so it creates task_plan.md, findings.md, and progress.md in your project directory.

Frequently Asked Questions about planning-with-files-zht

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

FAQPage Schema
How do I keep Claude Code from losing track of long tasks?▼

Use file-based planning: create task_plan.md, findings.md, and progress.md in your project root so state persists outside the context window. Hooks re-read the plan before tool calls, and the session-catchup script restores unsynced context after /clear.

What files does file-based task planning create?▼

It creates three Markdown files in your project directory: task_plan.md for phases and decisions, findings.md for research and discoveries, and progress.md for session logs and test results. Templates for each are included in the templates directory.

Does planning-with-files work on Windows?▼

Yes, it ships both PowerShell (.ps1) and Bash (.sh) versions of the init-session and check-complete scripts. The Stop hook tries PowerShell first and falls back to the shell script.

How does session recovery work after /clear?▼

The session-catchup.py script scans previous Claude session transcripts, finds the last planning file update, and reports unsynced messages. You then run git diff --stat, read the planning files, and update them before continuing.

When should I not use file-based planning?▼

Skip it for simple questions, single-file edits, and quick queries that finish in one or two steps. The overhead of maintaining three planning files only pays off for multi-step tasks spanning many tool calls.