Head to head
planning-with-files vs repomix
planning-with-files and repomix solve the same job (Memory & context), so this is a pick-one decision.
| Field | planning-with-filesgithub.com Not yet swept | repomixgithub.com Not yet swept |
|---|---|---|
| What it is | Makes the agent externalize its plan to disk (task_plan.md, findings.md, progress.md) so it survives /clear, compaction and crashes. Five lifecycle hooks re-read and re-inject the plan on session start and before major decisions. A Stop hook blocks termination until every phase is done. | Packs an entire repository into one AI-consumable file (XML, Markdown, JSON or text) with directory tree, contents and per-file token counts. Tree-sitter compression strips implementation bodies to signatures for ~70% token reduction. Honors .gitignore; Secretlint scans for credentials before output. |
| Category | Memory & context | Memory & context |
| Cost tier | free | free |
| Pricing | Free · MIT | Free · MIT |
| Why builders pick it | The fix for the single most annoying failure mode: Claude forgetting the design decisions you made two sessions ago and re-inventing the component. Deterministic completion gate means half-finished refactors do not get abandoned. | A one-shot context packer, not persistent memory — the right tool when you want to hand the whole project codebase to a model in a single message, or audit what is actually in there. The secret scan before output is a genuinely good safety default. |
| Watch out for | not logged | not logged |
| How to wire it up | npx skills add OthmanAdi/planning-with-files -g | npx repomix@latest |
| Editor's pick | Yes | Yes |
Other matchups worth running
Agent endpoint: GET /api/public/compare?slugs=planning-with-files,repomix