spec-graph

Manage software specifications and requirements through a typed semantic graph.

8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/tyeongkim/spec-graph --skill spec-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-graph
Source: https://github.com/tyeongkim/spec-graph/tree/main/skill
Command: npx skills add https://github.com/tyeongkim/spec-graph --skill spec-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-graph, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables structured management of software specifications, requirements, and development phases through a typed semantic graph, reducing miscommunication and oversight.

Core Features & Use Cases

  • Impact Analysis: Determine what changes affect related entities across the development workflow.
  • Gap Detection: Identify missing requirements, unverified assumptions, or unimplemented features.
  • Workflow Validation: Ensure phases are properly ordered, requirements are covered, and deliveries are complete.
  • Use Case: A team reviews impact of a requirement modification and promptly updates contributing tasks to maintain consistency.

Quick Start

Use the spec-graph skill to initialize a project, define requirements, phases, and analyze impacts of proposed changes.

Frequently Asked Questions about spec-graph

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

FAQPage Schema
How do I trace the impact of a requirement change across my development workflow?

Impact analysis traces requirement changes across your development workflow by using a typed semantic graph to identify and update all affected entities, ensuring consistency. This structured approach immediately highlights contributing tasks that need modification.

How do I initialize a project for semantic impact analysis and workflow validation?

To initialize a project for semantic impact analysis, you use the spec-graph skill to define requirements, establish phases, and set up a typed graph. This process structures your development workflow for subsequent validation and impact assessment operations.

Can I use this typed graph approach for requirements tracing in team-based software engineering?

Yes, you can use this typed graph approach for requirements tracing in team-based software engineering. It facilitates process coordination by enabling teams to review the impact of requirement modifications and promptly update contributing tasks to maintain consistency.

Do I need the spec-graph CLI tool to manage development workflows with semantic impact analysis?

Yes, you need the spec-graph CLI tool implemented in Go to manage development workflows with semantic impact analysis. The skill depends on this CLI tool to perform core operations on entities, relations, and validation rules.