planning-with-files MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

planning-with-files-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "planning-with-files-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/planning-with-files",
        "~/.claude/skills/planning-with-files"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "planning-with-files-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/planning-with-files",
        "~/.claude/skills/planning-with-files"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "planning-with-files-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/planning-with-files",
        "~/.claude/skills/planning-with-files"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "planning-with-files-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/planning-with-files",
        "~/.claude/skills/planning-with-files"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "planning-with-files-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/planning-with-files",
        "~/.claude/skills/planning-with-files"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "planning-with-files-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/OthmanAdi/planning-with-files",
          "~/.claude/skills/planning-with-files"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add planning-with-files-skill -- git clone https://github.com/OthmanAdi/planning-with-files ~/.claude/skills/planning-with-files

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : planning-with-files

Run a multi-day refactor without losing the thread

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

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

Prérequis

Skill cloned to ~/.claude/skills/planning-with-files — git clone https://github.com/OthmanAdi/planning-with-files ~/.claude/skills/planning-with-files

Déroulement

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.✓ Copié

→ 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.✓ Copié

→ 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?✓ Copié

→ List of discoveries that would otherwise be lost

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

Pièges

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

Combiner avec : filesystem · git

Conduct a research investigation with a durable findings doc

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

Quand l'utiliser : You'll be asking Claude to gather information from many sources and synthesize.

Déroulement

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.✓ Copié

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

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

→ Brief grounded in the durable notes, not hallucinated

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

Pièges

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

Combiner avec : firecrawl · fetch

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Modest — the 3 files consume tokens on re-reads, usually under 2k each
Monétaire: Free — skill is pure prompts and hook scripts
Astuce: Let Claude trim progress.md periodically so it doesn't grow unbounded across long projects.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — skill is pure prompts and local file operations

Sortie de données : 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.

Dépannage

Erreurs courantes et correctifs

Claude ignores the skill and doesn't create task_plan.md

Reference it by name in your prompt: 'use the planning-with-files skill'. Confirm the clone landed in ~/.claude/skills/planning-with-files.

Vérifier : ls ~/.claude/skills/planning-with-files/SKILL.md

Hooks not firing between tool calls

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

Vérifier : head ~/.claude/skills/planning-with-files/SKILL.md

The 3 files get committed to git accidentally

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

Vérifier : git check-ignore task_plan.md

Alternatives

planning-with-files vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills