AI Skill MartBrowse skillsPromptsProgramsLearnWhat is a Skill?
 
← Back to list

Planning with Files (Spanish Edition)

A Manus-style planning skill that breaks complex work into task_plan.md, findings.md, and progress.md, and restores context automatically after /clear.

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

What it does

  • Creates task_plan.md (phases, status, decisions), findings.md (research notes), and progress.md (session log) in your project root so context lives on disk instead of in a fragile window.
  • Ships hooks (UserPromptSubmit, PreToolUse, PostToolUse, Stop, PreCompact) that re-inject the active plan before tool calls and nudge you to log progress after every Write/Edit.
  • Runs session-catchup.py to diff the plan against real repo changes (git diff --stat) and flag work that happened but was never recorded.
  • Encodes operational rules: save findings after every 2 lookups, re-read the plan before decisions, never repeat a failed action, and escalate to the user after three failures.
  • Adds a security boundary: external web/API content goes only into findings.md, since task_plan.md is auto-injected and would amplify indirect prompt injection.

Who it's for

  • Developers running multi-step refactors, research, or greenfield builds in Claude Code.
  • Anyone who loses the thread in long sessions or watches the agent repeat the same mistake.
  • Teams that want a durable, reviewable work log instead of ephemeral TodoWrite lists.
  • Spanish-speaking users (other language variants live in the same repo).

Example uses

  1. Ask for "add an auth module to this monorepo" and the skill writes a five-phase task_plan.md, flipping each phase to complete as work lands.
  2. While comparing three libraries, key notes are flushed to findings.md every two searches, so the rationale survives context compaction.
  3. After /clear, the catch-up script reports "plan says phase 3, but the code already contains phase 4 changes"; you reconcile the plan files and continue.

· · · 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-es/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)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. 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 AI 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.

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-es ~/.claude/skills/

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

  1. Open a terminal and clone the repo: git clone https://github.com/OthmanAdi/planning-with-files.git /tmp/planning-with-files
  2. Copy the skill into your user skills folder: cp -r /tmp/planning-with-files/skills/planning-with-files-es ~/.claude/skills/
  3. Make the helper scripts executable: chmod +x ~/.claude/skills/planning-with-files-es/scripts/*.sh
  4. Verify Python is available with python3 --version (needed by the session catch-up script).
  5. If you installed to a non-standard path, add export PWF_SCRIPT_DIR="$HOME/.claude/skills/planning-with-files-es/scripts" to your shell profile.
  6. Restart Claude Code, open a project, and ask it to "plan this task step by step" — confirm that task_plan.md appears.
  7. Plan files are written to your project root, so add them to .gitignore if you don't want them committed.
View source on GitHub ↗License: MIT