spec-workflow

Automate spec-driven workflow state transitions and SPIDR-splitting.

5|Updated May 12, 2026
One-click install
npx skills add https://github.com/ramboz/jig --skill spec-workflow-ramboz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/ramboz/jig/tree/main/skills/spec-workflow
Command: npx skills add https://github.com/ramboz/jig --skill spec-workflow-ramboz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating the lifecycle of a spec-driven effort is complex: it requires SPIDR-splitting, state transitions, and governance gates across slices, docs, and ADRs. This skill provides a deterministic framework to manage that lifecycle, drive decisions, and surface drift or stale content.

Core Features & Use Cases

  • SPIDR-splitting of non-trivial specs into vertical slices for end-to-end value delivery.
  • Deterministic state transitions (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; with DEFERRED parking) and reconciliation gating.
  • Observability and governance surfaces (routing stats, project coverage, and traceability through use_cases and memory glossary) to prevent drift and ensure consistent delivery.

Quick Start

Use the spec-workflow tool to SPIDR-split a spec and begin tracking its lifecycle from draft to done.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I manage spec-driven workflow state transitions from drafting to implementation?

Spec-driven workflow state transitions are managed through a deterministic lifecycle tracking phases like DRAFT, READY_FOR_REVIEW, IN_PROGRESS, and DONE. The workflow enforces reconciliation gating and uses ADR-based auditing to prevent drift across slices and documentation.

What is SPIDR-splitting and when do I need it for specification documents?

SPIDR-splitting divides non-trivial specifications into vertical slices for end-to-end value delivery. You need it when coordinating complex spec-driven efforts that require breaking down large work items into manageable, trackable components with governance gates.

How do I track and reconcile parked or deferred specification work items?

Deferred specification work items are tracked using a DEFERRED parking state within the lifecycle. The workflow enforces a reconciliation checklist to surface drift or stale content, ensuring parked items are audited and eventually reconciled or closed properly.

Can I automate spec lifecycle governance and observability for non-trivial work items?

Spec lifecycle governance and observability are automated by delegating heavy steps to subagents via a workflow helper. This surfaces routing stats, project coverage, and traceability through memory glossaries to prevent drift and ensure consistent delivery across slices.

What's the best way to prevent documentation drift during spec implementation?

Preventing documentation drift during spec implementation requires deterministic state transitions, reconciliation gating, and ADR-based auditing. The workflow enforces a reconciliation checklist and provides observability surfaces to ensure traceability and consistent delivery across slices and docs.