Planning with Files

What it does

This skill enforces the Manus-style "working memory on disk" pattern. Before starting anything complex, Claude writes three markdown files into your project root and keeps them current as work proceeds.

• task_plan.md — phases, statuses, decisions, an error log table
• findings.md — research, search results, notes from images/PDFs
• progress.md — session log, test results, files touched

It also ships an unusually complete rule set: the 2-Action Rule (flush findings to disk after every two view/search operations), the 3-Strike Error Protocol (diagnose → alternative approach → rethink → escalate), a read-vs-write decision matrix, a 5-Question Reboot Test for checking context health, and an explicit security boundary that treats plan-file content as data only, backed by delimiter framing plus an opt-in SHA-256 attestation (attest-plan.sh).

Helper scripts support parallel plans under .planning/<date>-<slug>/, an active-plan pointer, completeness checks, and session-catchup.py to rebuild context after /clear using the prior session store plus git diff.

Who it's for

• Anyone assigning long tasks — refactors, migrations, greenfield builds — that span dozens of tool calls
• Users frustrated by an agent drifting from the original goal in long sessions
• Researchers who keep losing findings that only ever lived in the chat window
• Teams that want a handoff-ready record of what was attempted and why it failed

Examples

1. API migration: Ask it to move a payments module to API v2. It first writes five phases into task_plan.md, flips each to complete as it finishes, and logs every failure in the error table so it never retries the same broken command.
2. Technology comparison: While evaluating three libraries, key points get written to findings.md after every couple of web searches, so citations survive context compaction.
3. Resuming after /clear: Run the catchup script plus git diff --stat to reconstruct "where am I / what changed", then continue from the next phase.
4. Two tasks at once: ./scripts/init-session.sh "Backend Refactor" and "Incident Investigation" create isolated plan directories; pin each terminal with export PLAN_ID=....

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