Agent skill · product strategy · borghei
spec-driven-workflow
Run development from an executable specification with traceable requirement IDs and merge-time coverage gates. Use when starting a greenfield feature, reviving a stale spec, or gating merges on requirement coverage.
Why this skill is useful
Adds a structured approach to managing specifications with traceable requirement IDs and merge-time coverage gates, which the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Spec-Driven Workflow Development where the specification is the source of truth and the code is its implementation, rather than a document that was true at kickoff and fiction by week three. The mechanism is unglamorous: every normative statement gets a stable ID, every ID appears in a test, and the merge gate fails when the two drift apart. Without that mechanical link a spec is a memo, and memos do not survive contact with a sprint. When to use this skill Starting a greenfield feature where the interface is contested and the cost of building the wrong thing is high Reviving a stale spec that no longer matches shipped behaviour and needs reconciling before the next change Gating merges on coverage so a PR that implements two of five committed requirements cannot silently land Auditing what actually shipped ahead of a stakeholder review or a compliance obligation Handing a feature to another team who need the intent, not just the code Generating an implementation from a spec — which only works if the spec is precise enough that two engineers would build the same thing Inputs the skill expects A specification document in markdown, with normative statements using must/shall/should/may Acceptance criteria per requirement, ideally in given/when/then form The source tree and test suite where implementations will be annotated The coverage bar the merge gate enforces (mandatory-requirement coverage, typically 1.0) The previous requirements snapshot, when checking for drift against a baseline Which requirements are explicitly out of scope for the current milestone Clarify First Before writing or auditing a spec, confirm these inputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/spec-driven-workflow