KBAISE/ for lovable
Head to head

planning-with-files vs graphify

planning-with-files and graphify solve the same job (Memory & context), so this is a pick-one decision. planning-with-files is our default here: 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.

Quick read
  • Editor's pick: planning-with-files.
Fieldplanning-with-filesgithub.com Not yet sweptgraphifygithub.com Not yet swept
What it isMakes 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.Turns a mixed corpus — code, docs, SQL schemas, configs, PDFs, images — into a queryable knowledge graph. Code extraction is deterministic and local; only prose and images route through Claude. Every edge is labeled EXTRACTED, INFERRED or AMBIGUOUS. Outputs graph.json, an interactive HTML visualization, a report and an Obsidian vault. ~107k stars.
CategoryMemory & contextMemory & context
Cost tierfreefree
PricingFree · MITFree
Why builders pick itThe 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.The mixed-corpus part is your project angle — it will ingest editorial PDFs, style guides and back-issue docs alongside the code, not just source files. The --wiki export produces agent-navigable markdown grouped by concept.
Watch out fornot loggednot logged
How to wire it upnpx skills add OthmanAdi/planning-with-files -guv tool install graphifyy
Editor's pickYesNo

Agent endpoint: GET /api/public/compare?slugs=graphify,planning-with-files