spec-driven-development

Create and refine feature specifications before coding using the GitHub spec-kit workflow.

Updated Dec 23, 2025

Search Tags:#workflow #TDD #specification #SDD #spec-kit #software-engineering

Ready to run

npx skills add https://github.com/vineethsoma/agent-packages --skill spec-driven-development-vineethsoma

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-first development ensures teams define the problem, context, and acceptance criteria before implementation, reducing drift and rework.

Core Features & Use Cases

Specification-centric planning: Create, refine, and validate feature specs with the GitHub spec-kit workflow.
Constitution-aligned governance: Ensure specs and plans adhere to project principles and governance.
TDD-aligned planning: Derive tests and acceptance criteria from specs to drive implementation across teams.

Quick Start

Draft a feature spec for a new login flow using /speckit.specify.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is spec-driven development and how does it reduce software rework?▼

Spec-driven development defines the problem, context, and acceptance criteria upfront before coding. This spec-first workflow reduces software drift and rework by ensuring teams fully specify features and align them with project governance prior to implementation.

How do I create a feature specification using the spec-kit workflow?▼

You create a feature specification by drafting the initial spec, refining it for constitution alignment, and validating acceptance criteria. This planning workflow produces traceable FR, NFR, and SC documentation along with TDD-aligned guidance for implementation.

Can I derive test cases directly from a feature specification?▼

Yes, you can derive tests and acceptance criteria directly from specifications to drive implementation. This TDD-aligned planning approach ensures the generated tasks and tests traceably validate the functional and non-functional requirements defined in the spec.

Does spec-driven development work for team-based product development cycles?▼

Yes, spec-driven development applies directly to product development cycles across teams. It enables constitution alignment, specification refinement, and task generation to ensure distributed teams build features based on fully specified and governed project principles.

What is the best way to maintain traceable requirements documentation during planning?▼

The best way to maintain traceable requirements is using a spec-first methodology to generate FR, NFR, and SC documentation. This ensures specification artifacts are validated against project governance before any implementation tasks are generated.

When should I not use a spec-first development workflow?▼

You should avoid spec-first development when rapid prototyping is needed without upfront constraints or when a project lacks defined governance principles. The methodology requires dedicated time for constitution alignment and specification refinement before generating implementation tasks.