Borrowing it
Nothing to install: this file belongs to ddebixx/frontend-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ddebixx/frontend-template/main/.cursor/skills/spec-driven-development/SKILL.mdgit clone --depth 1 https://github.com/ddebixx/frontend-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ddebixx/frontend-template/spec-driven-development)<a href="https://agentmods.dev/skills/ddebixx/frontend-template/spec-driven-development"><img src="https://agentmods.dev/badge/skills/ddebixx/frontend-template/spec-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ddebixx/frontend-template/spec-driven-development"><img src="https://agentmods.dev/badge/skills/ddebixx/frontend-template/spec-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00126 | $0.01195 |
| Opus 5.5 | $0.00050 | $0.00478 |
| Sonnet 5.5 | $0.00025 | $0.00239 |
| Haiku 4.5 | $0.00013 | $0.00120 |
Grade A, and why
spec-driven-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-driven development
Treat the specification as the contract for the change. Do not begin non-trivial implementation while the specification is incomplete, contradictory, or missing testable acceptance criteria.
Core workflow
-
Inspect project context first
- Read relevant
.cursor/rules, existing architecture documentation, nearby code, tests, and existing specs. - Follow existing project conventions before introducing new ones.
- If the repository already has a spec location or template, use it. Otherwise use
docs/specs/<task-slug>.md.
- Read relevant
-
Classify the task
- Use the fast path only for changes that do not alter behavior, contracts, architecture, or meaningful UX.
- Treat new features, multi-file behavioral changes, refactors with risk, integrations, state/data changes, and UI flows as non-trivial.
- When uncertain, create a compact spec rather than skipping one.
-
Create or update the specification
- Use references/spec-template.md.
- State the problem and desired outcome before proposing implementation.
- Separate goals from non-goals.
- Number functional requirements as
FR-*, non-functional requirements asNFR-*, and acceptance criteria asAC-*. - Record assumptions explicitly. Do not silently invent product behavior.
- For blocking unknowns, mark the spec
Blockedand surface the smallest set of questions needed to proceed.
-
Make acceptance criteria executable in meaning
- Follow references/acceptance-criteria.md.
- Every material requirement must map to one or more acceptance criteria.
- Criteria must describe observable outcomes, including relevant error, empty, loading, permission, responsive, and accessibility states.
- Add a verification method for each criterion when useful: automated test, build/typecheck, browser interaction, visual inspection, API assertion, or manual check.
-
Challenge the specification before coding
- Delegate to the
spec-criticsubagent when available. - Ask the critic to find ambiguity, contradictions, missing states, hidden dependencies, unverifiable criteria, premature implementation constraints, and scope creep.
- Revise the spec until blocking findings are resolved.
- Set spec status to
Readyonly when implementation can proceed without guessing core behavior.
- Delegate to the
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 16d ago First seen · 98 lines · 126 tokens per session scan A d64fe0086013
spec-driven-development is a skill published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 17d ago), licensed MIT. It adds 126 tokens to every session and 1,195 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.