doc-graph

Map relationships between product documents and code references in repository memory files.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill doc-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-graph
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/doc-graph
Command: npx skills add https://github.com/lalulali/vespyr --skill doc-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill keeps planning, memory, and implementation documents connected so teams can quickly see how requirements, decisions, and code relate to each other without manually re-tracing every file.

Core Features & Use Cases

  • Document Relationship Mapping: Builds and updates a graph of links between PRDs, user stories, ADRs, decisions, blockers, and code references.
  • Graph Status and Regeneration: Detects when the underlying markdown files change and regenerates the graph only when needed.
  • Traceability for Product Workflows: Helps answer questions like which requirement a user story fulfills or which decision constrains a code module.
  • Use Case: A product team updates several planning documents and then refreshes the graph to immediately see the new relationships and implementation references.

Quick Start

Ask the assistant to update the document graph for the current project and summarize whether it was refreshed or already up to date.

Frequently Asked Questions about doc-graph

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

FAQPage Schema
How do I keep product documents traceable when PRDs and user stories change?

To keep product documents traceable, you can map relationships between PRDs, user stories, ADRs, and code references. This process detects markdown file changes and regenerates the graph only when needed to maintain current traceability.

How does document relationship mapping work for active decisions and blockers?

Document relationship mapping builds a graph of links between active decisions, blockers, and implementation paths in repository memory files. It applies mtime-based freshness checks to determine if the graph requires regeneration.

What is the best way to trace which ADR constrains a specific code module?

The best way to trace which ADR constrains a code module is to map the relationships between your planning documents and code references. This graph quickly shows how decisions and implementation paths relate to each other.

Can I automatically check document graph freshness based on file modification times?

Yes, you can automatically check document graph freshness using mtime-based checks. The system evaluates whether underlying markdown files have changed and regenerates the graph only when updates are detected.

Do I need to manually re-trace every file to see relationships between requirements and code?

No, you do not need to manually re-trace every file. The system automatically maps relationships between product documents and code references, providing structured JSON output for document status and telemetry reporting.

When should I regenerate the document graph for my product workflow?

You should regenerate the document graph whenever underlying markdown files are updated. The system uses mtime-based freshness checks to detect changes, ensuring the traceability graph remains current without unnecessary rebuilds.