Hooks not firing between tool calls

Check SKILL.md's frontmatter is intact; reinstall if the clone was partial.

planning-with-files (Claude Skill) — Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Automatic creation of task_plan.md, findings.md, progress.md at start of complex work
PreToolUse hook nudges Claude to re-read the plan before major decisions
Persistent failure log so the agent stops repeating the same mistakes
Recovers prior session state when context fills up or resumes
Won 3/3 blind A/B comparisons vs an unskilled baseline

Live-Demo

In der Praxis

planning-with-files-skill.replay ▶ bereit

0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: planning-with-files

Run a multi-day refactor without losing the thread

👤 Engineers doing migrations or large refactors with Claude Code ⏱ ~30 min intermediate

Wann einsetzen: You're breaking apart a monolith, migrating a framework, or doing anything that takes more than one session.

Ablauf

Kick off the work with the skill explicitly

We're migrating the auth module from JWT to session cookies. Use the planning-with-files skill to map this out before you start.✓ Kopiert

→ Claude writes task_plan.md with phases before touching code
Let Claude run; pause and resume across days

Pick up where we left off — read progress.md and continue.✓ Kopiert

→ Claude re-reads the plan and knows exactly which phase is next
Review findings.md for surprises

Summarize findings.md — anything that changed the original plan?✓ Kopiert

→ List of discoveries that would otherwise be lost

Ergebnis: A refactor that survives context resets with an audit trail you can actually review.

Fallstricke

Skill invoked for trivial one-line edits, adding overhead — Tell Claude 'skip planning-with-files, this is a one-shot fix'

Kombinieren mit: filesystem · git

Conduct a research investigation with a durable findings doc

👤 Anyone using Claude for multi-source research ⏱ ~45 min beginner

Wann einsetzen: You'll be asking Claude to gather information from many sources and synthesize.

Ablauf

Start with a research question

Research how modern rate-limiters handle burst traffic. Use planning-with-files — I want findings.md to build up over the session.✓ Kopiert

→ Claude writes findings.md incrementally as it searches
Ask for a synthesis at the end

Now synthesize findings.md into a 1-page brief.✓ Kopiert

→ Brief grounded in the durable notes, not hallucinated

Ergebnis: A findings doc you can re-use and a brief backed by it.

Fallstricke

findings.md balloons with noise — Instruct Claude to trim to signal-only at phase boundaries

Kombinieren mit: firecrawl · fetch

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

planning-with-files-skill + filesystem

Skill writes the markdown files; filesystem MCP lets Claude also edit code in the same session

Use planning-with-files to plan, then apply the fixes to the repo via filesystem.✓ Kopiert

planning-with-files-skill + git

Commit progress.md and findings.md at phase boundaries so you have a durable trail across machines

End of phase — commit the 3 planning files with a message summarizing what's done.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
create_plan	task description	Beginning of any task with 3+ steps	0 — local file write
log_finding	discovery text	Each time research turns up something worth remembering	0
update_progress	step completed	After each significant tool call or phase	0
resume_session	none	Start of any follow-up session in same working directory	0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: Modest — the 3 files consume tokens on re-reads, usually under 2k each
Kosten in €: Free — skill is pure prompts and hook scripts
Tipp: Let Claude trim progress.md periodically so it doesn't grow unbounded across long projects.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — skill is pure prompts and local file operations

Datenabfluss: None — all state stays on your disk in the working directory

The 3 files are written to your working directory — add them to .gitignore if you don't want them committed.

Fehlerbehebung

Häufige Fehler und Lösungen

The 3 files get committed to git accidentally

Add task_plan.md, findings.md, progress.md to .gitignore.

Prüfen: git check-ignore task_plan.md

Alternativen

planning-with-files vs. andere

Alternative	Wann stattdessen	Kompromiss
skillforge	You want a skill to create other skills, not just planning	Different goal — skillforge builds skills; planning-with-files runs tasks
Native TodoWrite tool	Lightweight in-context todos are enough and you don't need cross-session persistence	Free but evaporates when context resets

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen