spec-driven-dev

Enforce a formal spec file with goals, contracts, and acceptance criteria before coding.

Updated Apr 24, 2026

Search Tags:#workflow #planning #documentation #requirements #spec #acceptance

Ready to run

npx skills add https://github.com/SpencerGoss/agent-engineering --skill spec-driven-dev-spencergoss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/SpencerGoss/agent-engineering/tree/main/spec-driven-dev
Command: npx skills add https://github.com/SpencerGoss/agent-engineering --skill spec-driven-dev-spencergoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates drift in software development by enforcing a formal spec before coding.

Core Features & Use Cases

Enforces a pre-implementation spec gate to capture Goals, Non-Goals, User Stories, API Contracts, Data Models, Acceptance Criteria, and Implementation Tasks.
Provides a reproducible workflow that survives context resets and chat tool switches.

Quick Start

Create a docs/specs/YYYY-MM-DD-<feature>.md and fill every required section before touching code.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema

How do I prevent scope drift between planning and implementation?▼

To prevent scope drift, enforce a formal spec before coding that captures Goals, Non-Goals, User Stories, API Contracts, Data Models, and Acceptance Criteria. This pre-implementation gate ensures all stakeholders align on requirements before development starts.

What should be included in a software feature specification?▼

A software feature specification should include Goals, Non-Goals, User Stories, API Contracts, Data Models, Acceptance Criteria, and Implementation Tasks. It must also capture testable acceptance criteria and explicit Open Questions to ensure complete requirements coverage.

How do I create a reproducible workflow for feature planning across different chat tools?▼

Create a reproducible feature planning workflow by locking requirements into a formal spec file before implementation. Using a standardized markdown document ensures your planning context survives chat tool switches and context resets.

What is the best way to structure acceptance criteria for new features?▼

The best way to structure acceptance criteria is to define them within a formal spec file as testable requirements before coding begins. This ensures implementation tasks directly map to verifiable outcomes and prevents ambiguous feature completion.

When do I need to define non-goals in a software development spec?▼

You need to define non-goals in a software development spec during the pre-implementation phase to explicitly document what the feature will not deliver. This prevents scope creep and aligns stakeholder expectations before coding starts.

Does spec-driven development work without external dependencies?▼

Yes, spec-driven development works without external dependencies because it operates as a standalone workflow. It enforces a markdown-based spec file structure to guide feature planning and lock requirements independently of other tools.