/ Каталог / Песочница / planning-with-files
● Сообщество OthmanAdi ⚡ Сразу

planning-with-files

автор OthmanAdi · OthmanAdi/planning-with-files

Forces Claude to use disk-based markdown files as persistent memory — task_plan.md, findings.md, progress.md — instead of losing state in context resets.

A Claude Code skill that implements the Manus AI 3-file planning pattern. With it installed, Claude automatically writes a task_plan.md before starting multi-step work, logs discoveries to findings.md, and updates progress.md throughout the session. Benchmarks show 96.7% pass rate vs 6.7% without on multi-step tasks. Best for work spanning 3+ steps or many tool calls.

Зачем использовать

Ключевые функции

Живое демо

Как выглядит на практике

planning-with-files-skill.replay ▶ готово
0/0

Установка

Репозиторий автора · Официальная документация Claude Skills

Сценарии использования

Реальные сценарии: planning-with-files

Run a multi-day refactor without losing the thread

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

Когда использовать: You're breaking apart a monolith, migrating a framework, or doing anything that takes more than one session.

Поток
  1. 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.✓ Скопировано
    → Claude writes task_plan.md with phases before touching code
  2. Let Claude run; pause and resume across days
    Pick up where we left off — read progress.md and continue.✓ Скопировано
    → Claude re-reads the plan and knows exactly which phase is next
  3. Review findings.md for surprises
    Summarize findings.md — anything that changed the original plan?✓ Скопировано
    → List of discoveries that would otherwise be lost

Итог: A refactor that survives context resets with an audit trail you can actually review.

Подводные камни
  • Skill invoked for trivial one-line edits, adding overhead — Tell Claude 'skip planning-with-files, this is a one-shot fix'
Сочетать с: filesystem · git

Conduct a research investigation with a durable findings doc

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

Когда использовать: You'll be asking Claude to gather information from many sources and synthesize.

Поток
  1. 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.✓ Скопировано
    → Claude writes findings.md incrementally as it searches
  2. Ask for a synthesis at the end
    Now synthesize findings.md into a 1-page brief.✓ Скопировано
    → Brief grounded in the durable notes, not hallucinated

Итог: A findings doc you can re-use and a brief backed by it.

Подводные камни
  • findings.md balloons with noise — Instruct Claude to trim to signal-only at phase boundaries
Сочетать с: firecrawl · fetch

Комбинации

Сочетайте с другими MCP — эффект 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.✓ Скопировано
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.✓ Скопировано

Инструменты

Что предоставляет этот MCP

ИнструментВходные данныеКогда вызыватьСтоимость
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

Стоимость и лимиты

Во что обходится

Квота API
None
Токенов на вызов
Modest — the 3 files consume tokens on re-reads, usually under 2k each
Деньги
Free — skill is pure prompts and hook scripts
Совет
Let Claude trim progress.md periodically so it doesn't grow unbounded across long projects.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: No credentials — skill is pure prompts and local file operations
Исходящий трафик: None — all state stays on your disk in the working directory

Устранение неполадок

Частые ошибки и исправления

The 3 files get committed to git accidentally

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

Проверить: git check-ignore task_plan.md

Альтернативы

planning-with-files в сравнении

АльтернативаКогда использоватьКомпромисс
skillforgeYou want a skill to create other skills, not just planningDifferent goal — skillforge builds skills; planning-with-files runs tasks
Native TodoWrite toolLightweight in-context todos are enough and you don't need cross-session persistenceFree but evaporates when context resets

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills