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.
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 decisionsfindings.md— research results and discoveriesprogress.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
- Legacy migration: ask for a plan to port a module to TypeScript — you get a five-phase task_plan.md, statuses flipped to
completeas work lands, and an error table of failed attempts. - 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.
- Resuming tomorrow: the catch-up script diffs
git diff --statagainst the plan files, reports unsynced work, and picks up exactly where the last session stopped.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the 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.
- Open a terminal and clone the repo:
git clone https://github.com/OthmanAdi/planning-with-files.git - Create the skills folder if needed:
mkdir -p ~/.claude/skills - Copy the Traditional Chinese variant:
cp -r planning-with-files/skills/planning-with-files-zht ~/.claude/skills/ - Make the helper scripts executable:
chmod +x ~/.claude/skills/planning-with-files-zht/scripts/*.sh - Skim the files in
scripts/before enabling — the hooks run them on every tool call. - Restart Claude Code and confirm the skill appears via
/skillsor by asking it to "plan this task". - If you installed to a non-standard path, export the override:
export PWF_SCRIPT_DIR=~/path/planning-with-files-zht/scripts - Run it from your project directory — the plan files are created in your project root, not in the skill folder.