Display Name
specdriven-skills
Category
Agent Skills
Sub-Category
None
Primary Link
https://github.com/acaprari/specdriven-skills
Author Name
Alessio Caprari
Author Link
https://github.com/acaprari
License
MIT
Other License
No response
Description
A suite of six skills for spec-driven development, where specs are treated as the source of truth and code as a derivative. It scaffolds a specs/ directory for new or existing projects, keeps specs synchronized as code changes, and audits spec coverage before merging. One of the skills also detects when code is about to be written in an area that has no corresponding spec and surfaces the gap before implementation proceeds.
Validate Claims
The central claim is that the suite makes spec gaps visible before code is written, rather than after. To verify with minimal setup: install the plugin, create an empty directory containing a specs/ folder with only a README.md (no capability specs), then ask Claude Code to implement a feature. The spec:core skill fires autonomously, observes that no spec covers the area being touched, blocks implementation, and routes to the appropriate spec skill instead of writing code. Removing the specs/ folder and repeating the prompt shows the contrast: implementation proceeds normally. The behavior is reproducible in under two minutes and requires no existing codebase.
Specific Task(s)
In a fresh project that has a specs/ directory but no spec describing user authentication, ask Claude Code to add a login feature.
Specific Prompt(s)
First run: mkdir -p demo/specs && cd demo && echo "# Specs" > specs/README.md
Then, in Claude Code from that demo/ directory, say:
Add a POST /login endpoint that authenticates a user with email and password.
Expected: instead of writing the endpoint, spec:core reports that no spec covers authentication, blocks the change, and points you to spec:bootstrap to author the spec first. For contrast, delete the specs/ directory and issue the same prompt - Claude proceeds to implement directly.
Additional Comments
Distributed as a Claude Code plugin with a marketplace.json, so the repository also functions as a single-plugin marketplace (/plugin marketplace add acaprari/specdriven-skills). Stable release: v0.2.0. MIT licensed, no telemetry, runs entirely locally.
Recommendation Checklist
Display Name
specdriven-skills
Category
Agent Skills
Sub-Category
None
Primary Link
https://github.com/acaprari/specdriven-skills
Author Name
Alessio Caprari
Author Link
https://github.com/acaprari
License
MIT
Other License
No response
Description
A suite of six skills for spec-driven development, where specs are treated as the source of truth and code as a derivative. It scaffolds a
specs/directory for new or existing projects, keeps specs synchronized as code changes, and audits spec coverage before merging. One of the skills also detects when code is about to be written in an area that has no corresponding spec and surfaces the gap before implementation proceeds.Validate Claims
The central claim is that the suite makes spec gaps visible before code is written, rather than after. To verify with minimal setup: install the plugin, create an empty directory containing a
specs/folder with only aREADME.md(no capability specs), then ask Claude Code to implement a feature. Thespec:coreskill fires autonomously, observes that no spec covers the area being touched, blocks implementation, and routes to the appropriate spec skill instead of writing code. Removing thespecs/folder and repeating the prompt shows the contrast: implementation proceeds normally. The behavior is reproducible in under two minutes and requires no existing codebase.Specific Task(s)
In a fresh project that has a
specs/directory but no spec describing user authentication, ask Claude Code to add a login feature.Specific Prompt(s)
First run:
mkdir -p demo/specs && cd demo && echo "# Specs" > specs/README.mdThen, in Claude Code from that
demo/directory, say:Expected: instead of writing the endpoint,
spec:corereports that no spec covers authentication, blocks the change, and points you tospec:bootstrapto author the spec first. For contrast, delete thespecs/directory and issue the same prompt - Claude proceeds to implement directly.Additional Comments
Distributed as a Claude Code plugin with a
marketplace.json, so the repository also functions as a single-plugin marketplace (/plugin marketplace add acaprari/specdriven-skills). Stable release: v0.2.0. MIT licensed, no telemetry, runs entirely locally.Recommendation Checklist