traverspec-write

Reconcile facts from code, documents, and human input into a typed spec graph.

3|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/alvazone/traverspec --skill traverspec-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traverspec-write
Source: https://github.com/alvazone/traverspec/tree/main/templates/skills/traverspec-write
Command: npx skills add https://github.com/alvazone/traverspec --skill traverspec-write

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of maintaining a synchronized, traversable specification graph that keeps AI agents aligned with the actual intent and structure of a codebase, preventing the drift that occurs when documentation and code diverge.

Core Features & Use Cases

  • Fact Reconciliation: Automatically reconciles facts across disparate sources like code, documents, and conversations to ensure the spec graph remains the single source of truth.
  • Structured Authoring: Provides a rigorous schema for nodes and edges, ensuring that every feature, data model, and business rule is explicitly defined and connected.
  • Use Case: When a developer updates a feature, use this skill to ingest the code changes, reconcile them against existing documentation, and update the graph.yaml to reflect the new dependencies and business rules.

Quick Start

Use the traverspec-write skill to ingest the current code changes and update the spec graph with the new feature definitions.

Frequently Asked Questions about traverspec-write

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

FAQPage Schema
What is spec-driven development and how does a specification graph keep documentation aligned with code?

Spec-driven development uses a typed, traversable specification graph to synchronize product intent with codebase structure. The graph reconciles facts from code, documents, and human input, preventing drift by maintaining a single source of truth for features, data models, and business rules.

How do I reconcile code changes with existing documentation to maintain referential integrity?

You can reconcile code changes with existing documentation by ingesting the updates into the specification graph. The skill automatically reconciles facts across disparate sources, updating the graph to reflect new dependencies while ensuring structured node-edge relationships and referential integrity.

Can I use this specification graph skill for AI coding workflows that require strict alignment between product intent and technical implementation?

Yes, this skill is designed specifically for AI coding workflows requiring strict alignment between product intent and technical implementation. It maintains a synchronized, traversable spec graph that keeps AI agents aligned with the actual structure and intent of the codebase.

What is the best way to author structured software specifications using a typed graph schema?

The best way to author structured specifications is using a rigorous schema for nodes and edges. This approach explicitly defines and connects every feature, data model, and business rule, creating an evidence-based spec graph that serves as the single source of truth for development.

Why does documentation drift from code and how do I prevent it during software development?

Documentation drifts from code when updates to features are not synchronized across sources. You can prevent this drift by using a specification graph that automatically reconciles facts from code, documents, and conversations, ensuring the graph remains the single source of truth.

Do I need any external dependencies to scaffold and maintain a typed specification graph?

No external dependencies are required to scaffold and maintain a typed specification graph. The skill operates independently to ingest code changes, reconcile facts from disparate sources, and update the graph to reflect new feature definitions and dependencies.