ferrox-graphify

STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.

CJS-only (graphify): graphify subcommands are not registered on ferrox-tools query. Use the ferrox_run launcher shim (defined in each bash block below) or invoke the binary directly: node <runtime-home>/ferrox-core/bin/ferrox-tools.cjs graphify … where <runtime-home> is your runtime's config directory (e.g. ~/.claude, ~/.hermes, ~/.cursor). See docs/CLI-TOOLS.md for details. Other tooling may still use ferrox-tools query where a handler exists.

Step 0 -- Banner

Before ANY tool calls, display this banner:

Ferrox > GRAPHIFY

Then proceed to Step 1.

Step 1 -- Config Gate

Check if graphify is enabled by reading .planning/config.json directly using the Read tool.

DO NOT use the ferrox-tools config-get command -- it hard-exits on missing keys unless --default is passed.

1. Read .planning/config.json using the Read tool
2. If the file does not exist: display the disabled message below and STOP
3. Parse the JSON content. Check if config.graphify && config.graphify.enabled === true
4. If graphify.enabled is NOT explicitly true: display the disabled message below and STOP
5. If graphify.enabled is true: proceed to Step 2

Disabled message:

Ferrox > GRAPHIFY

Knowledge graph is disabled. To activate:

  node <runtime-home>/ferrox-core/bin/ferrox-tools.cjs config-set graphify.enabled true

Then run /ferrox-graphify build to create the initial graph.

---

Step 2 -- Parse Argument

Parse $ARGUMENTS to determine the operation mode:

Argument	Action
build	Run inline build (Step 3)
query <term>	Run inline query (Step 2a)
status	Run inline status check (Step 2b)
diff	Run inline diff check (Step 2c)
No argument or unknown	Show usage message