spec-governance-lite

Classifies tasks by difficulty and enforces staged spec-driven development with attributable drift review.

1|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill spec-governance-lite-igorganapolsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-governance-lite
Source: https://github.com/IgorGanapolsky/Random-Timer/tree/main/.cursor/skills/spec-governance-lite
Command: npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill spec-governance-lite-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams adopting spec-driven development often apply heavyweight specification ceremony to trivial changes or skip governance entirely on complex work, and AI-generated code reviews frequently make unsupported claims about catching bugs. This Skill applies proportionate governance: hard multi-constraint tasks get a staged approved baseline with attributable drift review, while easy tasks use lightweight reason-first reasoning. ## Core Features & Use Cases - Task Classification Gate: Runs scripts/spec_governance_gate.py to classify work as easy, medium, or hard and route it to the appropriate governance level. - Staged Baseline Workflow: For hard tasks, requires Spec Kit artifacts with named invariants, an approved baseline, then generation in a fresh step so drift findings cite specific clauses. - Claim Guardrails: Blocks false recall claims (e.g., "specs catch more bugs"), inline spec prompting, and unattributed drift findings, keeping a human Accountable for reconciliation. - Use Case: Before implementing a paywall gate with catalog loading, run the gate script to confirm it is a hard task, approve the spec baseline, then generate code in a separate step with drift findings anchored to invariant clauses. ## Quick Start Ask the assistant to classify your task with the spec governance gate script and follow the staged baseline workflow it prescribes before generating any code.

Frequently Asked Questions about spec-governance-lite

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

FAQPage Schema
How do I decide when spec-driven development is worth the overhead?▼

Classify the task with the gate script: hard multi-constraint work justifies a staged approved baseline and drift review, while easy tasks should use reason-first reasoning without added ceremony. The classification prevents both under-governance and process inflation.

How do I run the spec governance gate on a task?▼

Run `python3 scripts/spec_governance_gate.py --json --task "your task description"` to get a JSON classification. The output tells you whether the task is easy, medium, or hard and which governance workflow applies.

Can AI-generated specs claim to improve bug detection rates?▼

No. The skill explicitly blocks false recall claims; you may only claim attributable, contract-anchored review where drift findings cite specific spec clauses. Claiming specs raise bug recall is unsupported and rejected by the gate.

Why does the gate block my drift findings or inline spec prompt?▼

A `block_unattributed_drift` error means each finding must cite an invariant or clause id. A `block_inline_spec_prompt` error means you must approve the `specs/<###>/` baseline first, then generate code in a separate fresh step.

Who is responsible when the model generates code from a spec?▼

A human stays Accountable for reconciliation between the spec baseline and generated output. The model may be Responsible for generation, but final approval and drift resolution remain a human duty.