skills.rest
Borisserz
BorisserzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Generate a six-section software specification document before coding.

1|1|Updated Apr 11, 2026
Search Tags:#planning#documentation#specification#requirements#spec#software-development
One-click install
npx skills add https://github.com/Borisserz/FoodTracker --skill spec-driven-development-borisserz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Borisserz/FoodTracker/tree/main/.agents/skills/skills/spec-driven-development
Command: npx skills add https://github.com/Borisserz/FoodTracker --skill spec-driven-development-borisserz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.

Core Features & Use Cases

  • Establishes a six-area spec template (Objective, Commands, Project Structure, Code Style, Testing Strategy, Boundaries) to guide development.
  • Encourages surface of assumptions, risk, and acceptance criteria before implementation.
  • Provides a gated workflow (SPECIFY → PLAN → TASKS → IMPLEMENT) to ensure disciplined delivery and traceability.

Quick Start

Draft a complete spec for your next feature before you begin coding.

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 software specification document before coding?▼

A software specification document defines what you are building, why, and how completion is determined, establishing a shared source of truth between engineers and stakeholders to prevent guessing during implementation.

How do I create clear requirements for a new feature when requirements are evolving?▼

To create clear requirements for evolving features, surface assumptions, risks, and acceptance criteria within a specification document before implementation begins, ensuring all stakeholders share a single source of truth.

What is the best way to structure a specification for an architectural change?▼

The best way to structure a specification for an architectural change is using a six-area template that defines Objectives, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries before any code is written.

Can I use a gated workflow to manage software development from specification to implementation?▼

Yes, you can use a gated workflow moving through Specify, Plan, Tasks, and Implement phases to ensure disciplined delivery and maintain traceability from the original specification document through final coding.

When do I need to generate a specification document for software development?▼

You need to generate a specification document whenever starting a new project, building a new feature, or planning an architectural change where requirements are unclear or actively evolving across the engineering team.

Related Skills

Explore More Software Engineering Skills→
ulises-jeremiasulises-jeremias
2

dots-workstation-epic

Create and review epics using a structured template with objectives and success criteria.

Community
Intermediate
AetherCore-DevAetherCore-Dev
9

writing-plans

Generate detailed implementation plans with file paths and TDD steps.

Official
Advanced
koukokouko
6

using-domain-teams

Routes domain-specific tasks to the correct team based on intent and required deliverables.

Community
Intermediate
dariopalminiodariopalminio
1

release-generate-stories

Generate one story file per feature from a release's Features section.

Community
Advanced