spec-graph

Manages spec-graph updates during implementation. Tracks phase progress by registering new entities discovered during development (API, STT, TST, QST, ASM, CHG), adding delivers relations for completed work, and running impact analysis before changes. Does NOT control how implementation is done — only keeps the graph in sync with reality. Use when implementing a phase and needing to update spec-graph, when starting work on a phase, when checking what remains to implement, or when registering implementation artifacts in the graph. Requires spec-graph CLI and an existing .spec-graph/ with a plan created by spec-planner.

Use this skill whenever the project uses spec-graph for managing requirements, decisions, phases, changes, interfaces, states, tests, and other semantic entities in a typed graph. Trigger when the user mentions spec-graph, or when the task involves any of: tracking requirements or decisions, planning development phases, analyzing change impact, validating workflow gates, managing entity relationships in a specification graph, or coordinating agent work through structured impact analysis. Also trigger when you see a .spec-graph/ directory in the project, or when the user asks about impact analysis, gap detection, coverage checks, or phase exit criteria. This skill is essential for any phase-based development workflow that uses spec-graph as its semantic operator layer.

Transforms specifications, requirements documents, or natural language project descriptions into a fully registered spec-graph plan. Creates arch entities (REQ, DEC, ACT, RSK), execution entities (PLN, PHS), and mapping relations (covers). Validates the graph across all three layers before finalizing. Use when user asks to "plan this project", "create a spec-graph plan", "register requirements", "break this into phases", "turn this spec into a plan", or provides a requirements document and wants it converted into a spec-graph structure. Requires spec-graph CLI installed and a .spec-graph/ directory (will init if absent). Does NOT generate Markdown phase files — spec-graph is the sole source of truth.

Verifies implementation against spec-graph, confirms delivery completeness, and signs off phases. Performs graph-level validation (mapping, arch coverage, unresolved items) and code-level verification (structural + behavioral). Auto-fixes failures when possible by delegating code corrections. Only this skill can transition a phase to resolved status. Use when user asks to "verify the implementation", "check phase completion", "sign off this phase", "validate against the spec", "run spec verification", or when a phase implementation is complete and needs acceptance. Requires spec-graph CLI and an existing .spec-graph/ with phases in active status.