Retrieve and sequence context from a traversable spec graph.
npx skills add https://github.com/alvazone/traverspec --skill traverspec-read
Please help me install this Agent Skill. Skill: traverspec-read Source: https://github.com/alvazone/traverspec/tree/main/templates/skills/traverspec-read Command: npx skills add https://github.com/alvazone/traverspec --skill traverspec-read
This skill solves the problem of fragmented or overwhelming documentation by providing a structured, traversable graph that allows you to understand exactly how code, features, and business rules are connected.
Use the traverspec-read skill to show the forward dependencies for the feature node feature:checkout.
High-intent search queries and answers about installing and using this skill.
Spec-driven development uses a traversable spec graph to map dependencies, mutations, and business rules, solving fragmented documentation by structuring how features, data models, and code connect.
To map downstream business rules and data models, you gather context by traversing forward dependencies in the spec graph, identifying every connected node and edge affected by your changes.
Yes, you can use the traverspec CLI to retrieve deterministic, non-hallucinated context by performing structural traversal across the node-based architecture defined in graph.yaml and markdown assets.
The best way to visualize feature relationships and prevent breaking changes is dependency mapping via a spec graph, which sequences context to reveal downstream data models and business rules.
Yes, traverspec-read operates on associated markdown assets combined with a graph.yaml file to map dependencies and mutations, providing a structured graph over your existing documentation.
Dependency analysis returns inconsistent context without a graph structure because standard documentation is fragmented, lacking the node-based architecture needed for deterministic structural traversal.
JeromyJSmithGenerate a codebase knowledge graph introduction with communities, hotspots, and dependency paths.
LeandroBenjaminLAssess code changes through structured investigation, dependency analysis, and impact assessment.
darelabs-techQuery and visualize project knowledge graphs with Mermaid diagrams.
fukukei23Analyze codebases by querying knowledge graphs for structural relationships and dependencies.
