spec-workflowlisted

Drive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition state markers (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; also DEFERRED for parked slices with a stated resolution trigger), enforce the reconciliation checklist before commit, and surface stale specs/ADRs whose `last_verified` date has aged past dependency changes. Use when starting non-trivial new work, creating a spec, transitioning a slice's state, parking a slice as DEFERRED, reconciling a reviewed slice, or auditing doc freshness. Do not use for quick one-off fixes that don't need a spec, or for bug-shaped work where `jig:bug-fix` is the better fit.
ramboz/jig · ★ 4 · Testing & QA · score 73

Install: claude install-skill ramboz/jig

> Spec 003 promoted this skill from stub to active. The deterministic state > mutations live in `workflow.py`; this SKILL.md drives the judgment layer. ## What this skill does - Guides SPIDR-splitting a new spec into vertical slices (Spike last, not first — try Rules / Data / Interface / Path first). - Flags slices that look like horizontal phasing (no user-facing layer touched). - Drives the spec lifecycle state transitions via `workflow.py`. - Coordinates implementer + reviewer subagent invocations at the right points. - Enforces the reconciliation checklist before a slice goes DONE. - Consults `docs/memory/glossary.md` when drafting ACs to surface unknown domain terms. - Surfaces skill-routing observability via `workflow.py routing-stats [--days N]` — a read-only histogram of which skills fired (jig baseline vs. richer/"other" skill per category) from `.codex/skill-usage.jsonl` (slice 041-02). - Surfaces use-case coverage via `workflow.py coverage [--project-dir DIR]` — a read-only, **advisory** (non-blocking), project-wide **bidirectional** check (slice 068-03): a deterministic set-difference over the `use_cases:` trace links that reports use cases with no implementing spec (coverage gap) and specs citing no parent use case (scope creep). No-op when the project has no `## Use cases` section. - Surfaces gate-bypass telemetry via `workflow.py gate-stats [--days N]` — a read-only per-gate histogram of how often each gate honored its env-var override (an