skills.rest
Coldaine
ColdaineCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-development

Create formal project specifications covering objectives, commands, structure, and testing.

Updated Aug 23, 2026
Search Tags:#workflow#planning#documentation#specification#software-engineering#acceptance-criteria
One-click install
npx skills add https://github.com/Coldaine/agent-skills-vscode --skill spec-driven-development-coldaine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Coldaine/agent-skills-vscode/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/Coldaine/agent-skills-vscode --skill spec-driven-development-coldaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams align on software requirements by forcing a written specification before coding.

Core Features & Use Cases

  • Establish a clear objective and acceptance criteria before implementation.
  • Provide a structured template covering objective, commands, project structure, code style, testing strategy, and boundaries.
  • Use when starting new projects, dealing with ambiguous requirements, or making architectural decisions.

Quick Start

Start by outlining the project goal and constraints, then generate a formal spec that guides subsequent work.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I create a formal software specification before coding?▼

Writing a project specification is needed when starting with unclear or ambiguous requirements and when multiple teams or stakeholders must align on scope before implementation begins.

What should be included in project structure and code style guidelines?▼

Use software specification when starting new projects, dealing with ambiguous requirements, or making architectural decisions to establish a clear objective and acceptance criteria before implementation.

How do I unify goals and acceptance criteria for a new feature?▼

Start by outlining the project goal and constraints, then generate a formal spec that guides subsequent work to unify goals and acceptance criteria across multiple teams.

Does software specification work for ambiguous requirements and architectural decisions?▼

Software specification is needed when dealing with ambiguous requirements or making architectural decisions, as it forces a written specification to align teams on scope and acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
b566776b566776

bmad-market-research

Define market research scope, methodology, and data sources with web-verified evidence.

Community
Advanced
soloamentesoloamente

spec-driven-development

Creates detailed software specifications with four-phase workflow: Specify, Plan, Tasks, Implement.

Community
Advanced
addyosmaniaddyosmani
84.9k

spec-driven-development

Enforce a four-phase specification workflow before code implementation.

Community
Advanced
SSiertsemaSSiertsema

scope-statement-writing

Generate a complete project scope statement with boundaries and change protocol.

Community
Intermediate