Build and query project knowledge graph

gsd:graphifyskillsetup L23,035
davepoon/buildwithclaude
What it does

Build, query, and inspect the project knowledge graph

Best for

Maintaining a queryable knowledge graph of project decisions, artifacts, and relationships without manual documentation.

Inputs
  • · Command: build | query <term> | status | diff
  • · Optional --path for project root override
Outputs
  • · For build: .planning/graphs/{graph.json, graph.html, GRAPH_REPORT.md}, diff snapshot
  • · For query: matched nodes grouped by type with edge relationships
  • · For status: node/edge/hyperedge counts, freshness indicator
  • · For diff: added/removed/changed counts since last build
Requires
  • · gsd-tools.cjs graphify subcommands (CJS-only)
  • · .planning/graphs/ directory
Preconditions
  • · graphify.enabled === true in .planning/config.json
  • · .planning/ directory exists with STATE.md and phases/
  • · gsd-tools.cjs available at ~/.claude/get-shit-done/bin/
Failure modes
  • · graphify.enabled not set → displays disabled message
  • · .planning/config.json missing → stops with config gate error
  • · graphify build timeout → may return partial graph
  • · No baseline for diff → suggests running build twice
  • · graph.json malformed → status/query fail with parse error
Trust signals
  • · Non-destructive query/status/diff operations
  • · Dry-run preview for build before writing
  • · SHA256 incremental caching for build performance
  • · HTML visualization (graph.html) for manual inspection
  • · Freshness indicator (STALE/FRESH) on status