Planning with Files (German edition)
A German-language skill that plans and tracks complex, multi-step work in task_plan.md, findings.md and progress.md, and restores context after /clear.
AutomationIntermediate★ 26,060⑂ 2,177AI score 8/10Last updated: Aug 9, 2026
What it does
Brings the Manus-style "context window = RAM, filesystem = disk" pattern to Claude Code.
- Creates
task_plan.md(phases, progress, decisions),findings.md(research notes) andprogress.md(session log) in your project root before complex work starts. - UserPromptSubmit / PreToolUse / PreCompact hooks re-inject the plan into context so goals never drift during long sessions.
session-catchup.pycompares the previous session with real code changes (git diff) so you can resume cleanly after/clearor a compaction.- Ships opinionated operating rules: two-step save rule, three-attempt protocol, read-vs-write decision matrix, five-question restart test, and an error log table.
- Documents prompt-injection boundaries: untrusted web content must go into
findings.mdonly, never into the auto-readtask_plan.md.
Note: all skill text and output strings are in German.
Who it's for
- Developers running refactors, migrations or research that span many tool calls
- Anyone who loses track of progress when the context window compacts
- Teams that want an auditable trail of decisions and failed attempts
- German-speaking users who prefer German planning docs
Examples
- API migration: ask for a plan and get a phased
task_plan.md; each finished phase flips tocompleteand failures land in the error table. - Vendor research: comparing three payment gateways — every two searches, key findings are flushed to
findings.mdbefore they fall out of context. - Resuming after /clear: run the catch-up report plus
git diff --stat, sync the plan files with what actually changed, then continue where you left off.
· · · 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-de folder from the GitHub repo OthmanAdi/planning-with-files into my ~/.claude/skills/planning-with-files-de/. 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 && cp -r /tmp/pwf/skills/planning-with-files-de ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Make sure Git is installed, plus
python3(for session catch-up) and a POSIX shell. - 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 German variant:
cp -r planning-with-files/skills/planning-with-files-de ~/.claude/skills/ - Make the helper scripts executable:
chmod +x ~/.claude/skills/planning-with-files-de/scripts/*.sh - If you install to a non-standard path, export
PWF_SCRIPT_DIRpointing at the skill'sscriptsdirectory so the hooks can findinject-plan.sh. - Restart Claude Code and try a German trigger such as "Hilf mir bei der Planung dieses Projekts"; confirm the three planning files appear in your project root.
- Because the hooks run shell/PowerShell scripts automatically on every tool call, skim those scripts once before trusting them.
View source on GitHub ↗License: MIT