spec-driven-development

Create structured specifications covering objectives, commands, testing strategy, and acceptance criteria.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/logo-solutions/NAS-logo --skill spec-driven-development-logo-solutions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/logo-solutions/NAS-logo/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/logo-solutions/NAS-logo --skill spec-driven-development-logo-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects and features often start with vague requirements that lead to wasted effort, incorrect implementations, and repeated rework; this Skill enforces writing a clear, testable specification before any code is written to align expectations and reduce risk.

Core Features & Use Cases

  • Assumption Surfacing: Force explicit listing of assumptions so ambiguities are addressed up front.
  • Structured Spec Template: Produce a complete spec covering objective, tech stack, commands, project structure, code style, testing strategy, boundaries, and success criteria.
  • Gated Workflow & Tasks: Guide a four-phase gated workflow (Specify → Plan → Tasks → Implement) with human review checkpoints and task templates for incremental implementation.
  • Use Case: Start a new feature that touches multiple modules or requires architectural decisions and generate a reviewable spec and task breakdown that can be committed to the repo.

Quick Start

Draft a complete specification for a new feature by answering clarifying questions and producing the spec template with objectives, commands, project structure, code style, testing strategy, boundaries, 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 software requirements into a structured specification before coding?▼

Spec-driven development prevents incorrect implementations by enforcing a clear, testable specification covering objectives, boundaries, and acceptance criteria before any code is written, eliminating ambiguity and reducing repeated rework.

What is the best way to break down a new feature that touches multiple modules into tasks?▼

The best way to break down feature development is using a gated workflow with four phases: Specify, Plan, Tasks, and Implement, which generates a task breakdown with human review checkpoints for incremental implementation.

How do I create a testing strategy and acceptance criteria for architectural decisions?▼

Creating a testing strategy and acceptance criteria involves producing a complete spec template that explicitly defines project structure, code style, testing boundaries, and review checkpoints to align stakeholder expectations.

When should I use a spec-driven workflow for my software engineering project?▼

You should use a spec-driven workflow when starting a new project, designing a feature that touches multiple modules, or making architectural decisions that require stakeholder alignment and reviewable documentation.

How to stop wasted effort and rework caused by ambiguous feature requirements?▼

To stop wasted effort and rework from ambiguous requirements, force explicit listing of assumptions and generate a structured spec with executable commands and success criteria to align expectations before implementation begins.