spec-driven-development

Generate feature specifications, API contracts, database schemas, and ADRs.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill spec-driven-development-mralexiscord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/MrAlexisCord/chatbot-prototype/tree/main/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill spec-driven-development-mralexiscord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common software development challenge of misalignment and costly rework caused by unclear or incomplete specifications, by enforcing a "spec-first" methodology.

Core Features & Use Cases

  • Specification Writing: Guides users in creating detailed feature specifications (spec.md), API contracts (OpenAPI), database schemas, and Architecture Decision Records (ADRs).
  • Workflow Enforcement: Promotes a structured development lifecycle from feature request to living documentation.
  • Use Case: A product manager needs to define a new API endpoint. They use this Skill to generate a comprehensive OpenAPI specification, ensuring all stakeholders agree on the contract before any code is written.

Quick Start

Use the spec-driven-development skill to generate a template for a new feature specification document.

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 an OpenAPI specification before coding the API endpoints?

You can enforce spec-first development by using this Skill to generate comprehensive OpenAPI specifications. This ensures all stakeholders agree on the API contract before code is written, reducing ambiguity and preventing costly rework.

What is the best way to document architecture decisions for a new software feature?

The best way to document architecture decisions is by creating Architecture Decision Records. This Skill provides templates and guidance for generating ADRs, facilitating clear communication and testable requirements before implementation begins.

How do I start spec-driven development for a new database schema?

To start spec-driven development for a database schema, use this Skill to generate a detailed specification document. It guides you in creating structured database schemas, ensuring testable requirements are defined before any code is written.

Does spec-driven development work with test-driven and behavior-driven workflows?

Yes, spec-driven development integrates seamlessly with TDD and BDD workflows. By generating detailed feature specifications and API contracts beforehand, it establishes clear, testable requirements that drive subsequent test-driven and behavior-driven implementation.

Why should I write feature specifications before writing any code?

You should write feature specifications before coding to prevent misalignment and costly rework caused by unclear requirements. A spec-first methodology enforces a structured lifecycle, reducing ambiguity and generating testable requirements early.