Build a queryable code-structure graph for a codebase using graphify (AST + optional semantic extraction), then file the result into the claude-mem wiki at wiki/code/. Trigger phrases - graphify this codebase, build the code graph, ingest the code, /graphify-ingest, refresh the graph.
Incrementally rebuild the code-structure graph after a feature is implemented. Detects changed files, re-extracts only those, merges into existing graph.json, preserves community labels via Jaccard matching, refreshes wiki/code/. One-shot - run after each feature, before commit. Trigger phrases - refresh the graph, update the code graph, /graphify-update, rebuild after this feature, graph update.
Autonomous plan-driven research loop. Takes a topic, decomposes it into research questions in a persisted plan artifact, dispatches research subagents per question, synthesizes findings, and files everything into the wiki as structured pages. Resumable: an interrupted session leaves the plan in the vault and the next run continues it. Based on Karpathy's autoresearch pattern plus OpenManus PlanningFlow patterns: program.md configures objectives and budgets, statuses live in the plan note. Triggers on: "/autoresearch", "autoresearch", "research [topic]", "deep dive into [topic]", "investigate [topic]", "find everything about [topic]", "research and file", "go research", "build a wiki on", "resume research".
Ingest sources into the Obsidian wiki vault. Reads a source, extracts entities and concepts, creates or updates wiki pages, cross-references, and logs the operation. Supports files, URLs, and batch mode. Triggers on: ingest, process this source, add this to the wiki, read and file this, batch ingest, ingest all of these, ingest this url.
Export the wiki's canonical BA / project deliverables to formal Office documents (.docx / .xlsx) and diagrams (PlantUML), written to .raw/exports/, by reusing the ba-suite skills. Optionally push to a tracker (ClickUp / Jira) over MCP. The wiki stays the source of truth; Office files are a generated view. For Mode ADLC and Mode C vaults. Triggers on: "/ba-export", "ba export", "export to docs", "export the BRD", "export the backlog", "generate the requirements doc", "export test cases", "export BA deliverables", "export to clickup", "export to jira", "produce office docs".
Plain-language explanation of one node in the project's graphify code graph: source file, type, community membership, and all incoming/outgoing edges with relations and confidence tags. Cheap (no LLM cost — direct graph lookup). Use for "what is X", "explain this function", "show me what touches Y" when Y is a single named symbol. Triggers on: "/graphify-explain", "explain node", "what is X (in the graph)", "describe node", "neighbors of", "what touches X", "show me X's connections" (when about code).
Find the shortest path between two named nodes in the project's graphify code graph. Returns the hop sequence with edge relations and confidence tags. Cheap (no LLM cost — NetworkX shortest path on the existing graph). Use for "how does A reach B", "trace the dependency chain from X to Y", "what connects A and B". Triggers on: "/graphify-path", "shortest path between", "how does X reach Y", "trace path from", "dependency chain from A to B", "path A to B" (when about code).
Free-form code-structural query against the project's graphify code graph. BFS (default) or DFS traversal from term-matched start nodes, returning relevant subgraph as node + edge listings with source file pointers and community tags. Cheap (no LLM cost — pure graph traversal). Use for "what's connected to X", "what touches Y", "explore the auth area", or any open-ended code-structural exploration when a graphify graph exists for the project. Triggers on: "/graphify-query", "graph query", "query the graph", "explore the graph", "what's connected to", "what touches", "what's in the X area" (when about code).