spec-driven-development

Enforce spec-driven code generation and validation from formal Markdown specifications.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/UBAIDRAZA1/UBAIDRAZA1-Todo-Web-Application --skill spec-driven-development-ubaidraza1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/UBAIDRAZA1/UBAIDRAZA1-Todo-Web-Application/tree/main/.gemini/skills/spec-driven-development
Command: npx skills add https://github.com/UBAIDRAZA1/UBAIDRAZA1-Todo-Web-Application --skill spec-driven-development-ubaidraza1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development enforces a formal specification → generate → review cycle, preventing drift from requirements and reducing rework.

Core Features & Use Cases

  • Mandatory spec artifacts (spec.md, plan.md, tasks.md, ADR) ensure traceability and accountability.
  • Enforces generation directly from specs and supports structured review to validate implementation against the spec.
  • Forbids manual patches and skipped specifications to maintain a single source of truth.

Quick Start

Create a feature spec in a Markdown file and initiate the generate-and-review cycle to produce and validate the implementation.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I enforce spec-driven development and prevent code drift from requirements?

Spec-driven development prevents drift by enforcing a formal specification, generation, and review cycle. Code generation only occurs from a formal spec, ensuring implementation matches requirements before integration and reducing rework.

What is the generate-and-review cycle for traceable software artifacts?

The generate-and-review cycle is a workflow validating implementation against a spec. It produces mandatory traceable artifacts like spec.md, plan.md, tasks.md, and ADRs to ensure accountability across planning, design, and coding stages.

How do I start a spec-first workflow for feature development?

To start a spec-first workflow, create a feature specification in a Markdown file. Initiate the generate-and-review cycle to produce the implementation code and validate it directly against the created specification.

Can I apply manual patches during a spec-driven workflow?

Manual patches are forbidden during a spec-driven workflow. The process requires generating code directly from formal specifications to maintain a single source of truth and ensure traceability across all artifact delivery stages.

Does spec-driven development work for feature teams needing artifact-based delivery?

Spec-driven development suits feature development teams requiring traceable specs and artifact-based delivery. It mandates spec artifacts across planning, design, and coding stages, validating that code matches the spec before integration.

Why do I need mandatory spec artifacts like ADRs and tasks.md?

Mandatory spec artifacts including ADRs, spec.md, plan.md, and tasks.md ensure traceability and accountability. They provide a structured formal specification to validate generated code against, preventing requirement drift.