Planning with Files (German Edition)

A German-language planning skill that breaks complex work into task_plan.md, findings.md and progress.md, and restores context automatically after a session is cleared.

AutomationIntermediate★ 26,167⑂ 2,188AI score 10/10Last updated: Aug 9, 2026

What it does

Applies the Manus-style pattern: the context window is RAM, the filesystem is disk — anything important gets written to a file.
Creates and maintains three files before complex work starts: task_plan.md (phases, progress, decisions), findings.md (research notes) and progress.md (session log).
Ships hooks (UserPromptSubmit, PreToolUse, PostToolUse, Stop, PreCompact) that re-inject the current plan and nudge you to log progress after every write or edit.
Recovers from /clear and compaction using scripts/session-catchup.py plus git diff --stat to reconcile plan files with reality.
Encodes concrete anti-failure rules: the two-step save rule, a three-attempt protocol, and an error log table so the same mistake isn't repeated.
Includes a security-boundaries section: web and search output goes only into findings.md, never into the hook-amplified task_plan.md.

Who it's for

Developers running multi-step work — large refactors, feature builds, technical research.
Anyone who loses the original goal once a Claude session gets long.
German-speaking teams using Claude Code (an English variant lives in the same repo).
People who want an auditable paper trail of decisions and failures.

Examples

Large refactor: ask to migrate auth to JWT, and the skill drafts a 5-phase task_plan.md, flips each phase to complete, and records every error in a table.
Technology research: after every two searches or page views, key insights land in findings.md so nothing is lost when the context is trimmed.
Session recovery: after /clear, the catch-up script reports unsynced context, you diff it against git, refresh the plan files, then continue exactly where you left off.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/OthmanAdi/planning-with-files/HEAD/skills/planning-with-files-de/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

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.

↓ 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-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/planning-with-files && cp -r /tmp/planning-with-files/skills/planning-with-files-de ~/.claude/skills/

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

Open a terminal and clone the repository to a temp folder: git clone https://github.com/OthmanAdi/planning-with-files.git /tmp/planning-with-files
Make sure the skills directory exists: mkdir -p ~/.claude/skills
Copy the German variant into place: cp -r /tmp/planning-with-files/skills/planning-with-files-de ~/.claude/skills/
Make the hook scripts executable: chmod +x ~/.claude/skills/planning-with-files-de/scripts/*.sh
Verify Python is available with python3 --version (needed by the session-catchup script).
Restart Claude Code, open a project folder, and ask something like "help me plan this project" or use the German trigger "Projekt zerlegen".
If you installed to a non-standard path, export PWF_SCRIPT_DIR pointing at the skill's scripts directory so the hooks resolve.
Expect the plan files to appear in your project root — not inside the skill installation directory.

View source on GitHub ↗License: MIT