skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Convert ambiguous requirements into validated specifications before writing code.

1|1|Updated Apr 20, 2026
Search Tags:#planning#specification#requirements#task breakdown#testing strategy#software architecture#human review gates
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill spec-driven-development-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/svssdeva/agentic-skills/tree/main/engineering/spec-driven-development
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill spec-driven-development-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents “code-first guessing” by guiding you to convert unclear or missing requirements into a validated, implementation-ready specification.

Core Features & Use Cases

  • Gated workflow: Forces a structured flow from Specify → Plan → Tasks → Implement with explicit human review gates at each phase.
  • Assumption surfacing: Requires listing assumptions up front so misunderstandings are caught before writing specs or code.
  • Success-criteria reframing: Translates vague goals into concrete, testable outcomes so progress is measurable.
  • Practical spec template: Produces a spec that includes objectives, full commands, project structure, code style, testing strategy, boundaries, and success criteria.
  • Use cases: Starting a new feature, refactoring an ambiguous module, coordinating multi-file changes, or planning any change that touches architecture, testing, or CI.

Quick Start

Ask the human clarifying questions, write a Spec covering objective, commands, project structure, code style, testing strategy, and boundaries, then proceed only after the human validates the spec and success criteria.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I turn vague requirements into a build-ready specification?▼

To turn vague requirements into a build-ready specification, you must surface assumptions, reframe goals into measurable success criteria, and define boundaries across specify, plan, tasks, and implement phases.

What is the best way to plan a multi-module software architecture refactor?▼

Planning a multi-module software architecture refactor requires a gated workflow that forces explicit human review gates, ensuring scope and testing strategy are validated before any implementation begins.

How do I write testable success criteria for new software features?▼

Writing testable success criteria involves translating ambiguous goals into concrete outcomes and documenting them within a practical spec template alongside objectives, project structure, and testing strategy.

When should I use a specification-driven workflow for software development?▼

A specification-driven workflow should be used for new projects, refactors, or architectural decisions where scope spans multiple modules, success criteria must be testable, and code-first guessing needs prevention.

How do I prevent code-first guessing when starting a new project?▼

Preventing code-first guessing requires converting unclear requirements into a validated specification by asking clarifying questions and enforcing explicit human review gates before writing code.

What should a practical spec template include for coordinating multi-file changes?▼

A practical spec template for multi-file changes should include objectives, full commands, project structure, code style, testing strategy, boundaries, and testable success criteria validated by human review.

Related Skills

Explore More Software Engineering Skills→
konglong87konglong87
46

pm-clarify

Clarify vague product requirements into structured testable specifications.

Community
Advanced
osovvosovv
11

vv-plan

Generate structured implementation plans from approved spec.xml files.

Community
Advanced
richardgillrichardgill
37

implementing-plans

Execute plan phases sequentially with automated verification and human checkpoints.

Community
Advanced
mnthemnthe

plan

Convert vague automation requirements into structured Markdown implementation plans.

Community
Basic