spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: TinNguyen

Create structured specifications with six core sections before coding.

1|Updated Jan 26, 2026

Search Tags:#planning #testing #documentation #specification #software-development #project-setup

Ready to run

npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill spec-driven-development-asktinnguyen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/spec-driven-development
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill spec-driven-development-asktinnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, written specifications before coding to prevent guesswork, miscommunication, and costly rework.

Core Features & Use Cases

Structured six-section spec template (Objective, Commands, Project Structure, Code Style, Testing Strategy, Boundaries) to guide the build.
Phase-driven workflow (Specify, Plan, Tasks, Implement) to align human and AI collaborators.
Living documentation with change tracking and references to related SKILLs for reuse.

Quick Start

Draft an initial project spec by listing assumptions and writing the six-section plan.

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 before coding to prevent guesswork?▼

To write a software specification before coding, draft a structured plan using a six-section template covering Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries to guide development and prevent guesswork.

What is spec-driven development and when should I use it for my project?▼

Spec-driven development is the practice of creating a written specification before coding to align collaborators. Use it when starting new projects, features, or architectural decisions where requirements are unclear or evolving.

How do I structure a project specification for both human and AI collaborators?▼

Structure a project specification using a four-phase workflow: Specify, Plan, Tasks, and Implement. This enforces structured content across six core sections to align both human and AI collaborators throughout the process.

Can I use specification-driven workflows for evolving project requirements?▼

Yes, you can use specification-driven workflows for evolving requirements because the approach supports living documentation that updates with decisions, ensuring the project plan remains accurate as assumptions change.

What's the best way to document architectural decisions during software planning?▼

The best way to document architectural decisions during software planning is to maintain living documentation within your specification, tracking changes and referencing related SKILLs to reuse established decisions.

What should I include in a testing strategy section for a new software feature?▼

A testing strategy section for a new software feature should outline the testing approach within the broader project specification, defining boundaries and expectations to guide both implementation and validation phases.