Skip to content
SkillCheatSheet Sign in

spec-driven-development

An AI agent skill from addyosmani/agent-skills, scored 80 out of 100 by code and Verified.

80/ 100BVerified

Code score by group

  • Spec20/20
  • Description12/20
  • Procedure10/15
  • Done criteria13/15
  • Resources10/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Description (8), the group that checks whether the description says what the skill does and when to use it.

What the author says it does

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
addyosmani/agent-skills
Folder
skills/spec-driven-development
License
MIT
GitHub stars
116,263
SKILL.md lines
260
Other files
0

Add spec-driven-development to your agent

npx skills add addyosmani/agent-skills --skill spec-driven-development

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

Labelled for

More skills from addyosmani/agent-skills

  1. constraint-driven-development

    Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds wh…

    Verified91A
  2. interview-me

    Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlyin…

    Verified86A
  3. frontend-ui-engineering

    Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG acc…

    Verified83B
  4. doubt-driven-development

    Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testin…

    Verified81B
  5. planning-and-task-breakdown

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you…

    Verified81B
  6. code-simplification

    Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use…

    Verified80B
  7. documentation-and-adrs

    Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping feat…

    Verified80B
  8. observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production a…

    Verified80B

All skills in addyosmani/agent-skills

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.