spec-driven-development

Define a precise specification with objectives, constraints, and acceptance criteria before coding.

1|Updated Apr 5, 2026

Search Tags:#development #specification #verification #spec #project-management #acceptance-criteria

Ready to run

npx skills add https://github.com/mortenbroesby/playground --skill spec-driven-development-mortenbroesby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/mortenbroesby/playground/tree/main/.skills/spec-driven-development
Command: npx skills add https://github.com/mortenbroesby/playground --skill spec-driven-development-mortenbroesby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This process helps teams avoid ambiguous requirements by forcing a concise, testable spec before coding.

Core Features & Use Cases

Clear objective capture: Document objective, target user, constraints, non-goals, and acceptance criteria.
Grounding in repository rules: Ground the scope in repo rules, local AGENTS.md, and vault notes.
Verification-ready guidelines: Name acceptance criteria and concrete verification steps to prove completion.

Quick Start

Draft a compact spec for a new feature by listing objective, constraints, acceptance criteria, and a verification plan.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I write a specification before coding to prevent scope creep?▼

To write a specification before coding, document the objective, constraints, non-goals, acceptance criteria, and verification plan. This forces a concise, testable spec that prevents ambiguous requirements and scope creep.

What should be included in software acceptance criteria and verification plans?▼

Acceptance criteria and verification plans should include explicit objectives, constraints, non-goals, and concrete verification steps. These verification-ready guidelines prove completion and ground the project scope in repository rules.

When do I need to define a compact spec for a new feature or refactor?▼

You need to define a compact spec for a new feature or refactor when requirements are under-specified and need explicit boundaries. This applies to starting new features, refactors, or architectural changes to prevent misinterpretation.

How do I ground project management specifications in repository rules and vault notes?▼

Ground project management specifications in repository rules by aligning objectives and constraints with local AGENTS.md and vault notes. This ensures the specification respects existing repository rules before coding begins.

What is the best way to define explicit boundaries for under-specified architectural changes?▼

The best way to define explicit boundaries for under-specified architectural changes is drafting a compact spec. List the objective, target user, constraints, non-goals, acceptance criteria, and a verification plan to enforce testable requirements.