gsd-graphify

Build and explore a project knowledge graph using the graphify CLI.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-graphify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-graphify
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-graphify
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-graphify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Graph-based project knowledge organization helps teams quickly discover relationships between tasks, plans, and assets across the repository by building an executable knowledge graph.

Core Features & Use Cases

  • Build and query a project knowledge graph from the repository planning data.
  • Inspect the graph structure, edges, and metadata to validate project context.
  • Use cases include exploring relationships between planning graphs, tasks, and code components.

Quick Start

From the project root, run graphify build to generate the graph and then query it with gsd-graphify.

Frequently Asked Questions about gsd-graphify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a knowledge graph from my repository planning data?

To build a knowledge graph from your repository planning data, run the graphify build command from your project root. This generates executable graph artifacts in the .planning/graphs/ directory, enabling subsequent search and inspection of project relationships.

What is a project knowledge graph used for in software engineering?

A project knowledge graph surfaces connected insights by mapping dependencies and relationships across tasks, plans, and code components. It helps teams quickly discover connections during repository planning, architecture reviews, and cross-team task tracking.

Can I search and inspect graph edges to validate project context?

Yes, you can inspect the graph structure, edges, and metadata to validate project context. After building the graph using the graphify CLI, use subsequent search and inspection commands to explore relationships between planning graphs, tasks, and code components.

Does the graphify CLI require any external dependencies to generate planning graphs?

No external dependencies are required to generate planning graphs. The graphify CLI operates directly on your repository planning data to build the knowledge graph artifacts and supports search and inspection commands without additional component installations.

What's the best way to track cross-team task dependencies across a repository?

The best way to track cross-team task dependencies is applying a knowledge graph to repository planning. By building an executable graph with graphify, you surface connected insights and map complex relationships between tasks and code components.