Planning with Files (Spanish Edition)

What it does

Before starting any complex task, this skill creates three Markdown files in your project root and treats the filesystem as durable working memory:

• task_plan.md — phases, status, key decisions
• findings.md — research and discoveries
• progress.md — session log, test results, changed files

Hooks re-inject the plan on every tool call and before context compaction, and session-catchup.py restores context after /clear by comparing plan files with git diff --stat. It also codifies practical rules: save findings after every 2 lookups, a three-strike failure protocol (change approach, then ask the user), and a security boundary that untrusted web content must go into findings.md only, never into the auto-injected task_plan.md.

Who it's for

• Developers running long tasks that span many tool calls (migrations, refactors, audits)
• Anyone frustrated by Claude drifting from the original goal in long sessions
• Teams that want a file-based handoff trail between sessions
• Spanish-speaking users; the English variant lives in the planning-with-files folder

Examples

1. API migration: ask it to move a project to v2 — it writes a 6-phase plan, flips each phase to complete, and logs every error with the fix in a table.
2. Comparative research: while evaluating libraries, key notes land in findings.md every two searches, so evidence survives context compaction.
3. Session recovery: after /clear, it reads the plan files plus the git diff, reconciles what actually shipped, and resumes from the right phase.

Install the skill I found on Claude Skill Mart.
Copy the skills/planning-with-files-es folder from the GitHub repo OthmanAdi/planning-with-files into my ~/.claude/skills/planning-with-files-es/.
When it's done, tell me in one line what this skill can do.