Claude Skill MartBrowse skillsWhat is a Skill?
Back to list

Planning with Files (Traditional Chinese Edition)

Turns complex multi-step work into three persistent Markdown files — task_plan.md, findings.md, progress.md — with automatic context recovery after /clear.

AutomationIntermediate26,0602,177AI score 8/10Last updated: Aug 9, 2026

What it does

Brings the Manus-style "working memory on disk" pattern to Claude Code. Before any complex task, Claude creates and maintains three Markdown files:

  • task_plan.md — phases, status, key decisions
  • findings.md — research results and discoveries
  • progress.md — session log, test results, errors hit

Hooks on UserPromptSubmit, PreToolUse and PreCompact re-inject the plan into context, while session-catchup.py reconstructs state after a /clear or compaction. The doc also ships operational rules: a three-strike failure protocol, a read-vs-write decision matrix, a five-question restart test, and a security boundary stating that untrusted web content must go into findings.md only (never into the hook-injected task_plan.md).

Who it's for

  • Anyone running refactors, research or build tasks that exceed ~5 tool calls
  • Users frustrated by Claude losing the goal after context compaction
  • Teams that need a file-based audit trail instead of ephemeral TodoWrite lists
  • Traditional Chinese speakers (English and other language variants live in the same repo)

Examples

  1. Legacy migration: ask for a plan to port a module to TypeScript — you get a five-phase task_plan.md, statuses flipped to complete as work lands, and an error table of failed attempts.
  2. Competitive research: after every two web lookups, key facts are flushed to findings.md so screenshot/multimodal detail isn't lost; the final report is written straight from that file.
  3. Resuming tomorrow: the catch-up script diffs git diff --stat against the plan files, reports unsynced work, and picks up exactly where the last session stopped.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/planning-with-files-zht folder from the GitHub repo OthmanAdi/planning-with-files into my ~/.claude/skills/planning-with-files-zht/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/OthmanAdi/planning-with-files.git /tmp/pwf && mkdir -p ~/.claude/skills && cp -r /tmp/pwf/skills/planning-with-files-zht ~/.claude/skills/

This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and clone the repo: git clone https://github.com/OthmanAdi/planning-with-files.git
  2. Create the skills folder if needed: mkdir -p ~/.claude/skills
  3. Copy the Traditional Chinese variant: cp -r planning-with-files/skills/planning-with-files-zht ~/.claude/skills/
  4. Make the helper scripts executable: chmod +x ~/.claude/skills/planning-with-files-zht/scripts/*.sh
  5. Skim the files in scripts/ before enabling — the hooks run them on every tool call.
  6. Restart Claude Code and confirm the skill appears via /skills or by asking it to "plan this task".
  7. If you installed to a non-standard path, export the override: export PWF_SCRIPT_DIR=~/path/planning-with-files-zht/scripts
  8. Run it from your project directory — the plan files are created in your project root, not in the skill folder.