spec-driven-development

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

Create structured specifications with a gated four-phase workflow.

Updated Apr 8, 2026

Search Tags:#planning #spec-driven #specification #requirements #implementation #software-development #task-breakdown

Ready to run

npx skills add https://github.com/harishgovardhandamodar/adversarialStudy --skill spec-driven-development-harishgovardhandamodar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/harishgovardhandamodar/adversarialStudy/tree/main/Distributionally-Adversarial-Attack/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/harishgovardhandamodar/adversarialStudy --skill spec-driven-development-harishgovardhandamodar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents ambiguous requirements and costly rework by producing a concrete, reviewable specification before any code is written. It surfaces assumptions, acceptance criteria, and verification checkpoints so engineers and stakeholders agree on what "done" means.

Core Features & Use Cases

Spec template covering Objective, Commands, Project Structure, Code Style, Testing Strategy, Boundaries, Success Criteria, and Open Questions.
Gated four-phase workflow (Specify → Plan → Tasks → Implement) with human review gates at each phase to avoid premature implementation.
Task decomposition and verification: Breaks plans into small, testable tasks with explicit acceptance criteria and verification steps.
Use Case: Kick off a new payment feature by creating a one-page spec, aligning product and engineering, sequencing implementation, and preventing architecture rework.

Quick Start

Draft a one-page spec that states the objective, lists executable commands, defines project structure and code style, outlines tests and boundaries, and finishes with clear success criteria and open questions.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

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

Spec-driven development creates structured specifications before coding to prevent ambiguous requirements. Use it for project starts, architectural decisions, multi-file features, and tasks expected to take more than thirty minutes to prevent costly rework.

How do I create a specification before coding a new feature?▼

To create a specification, draft a spec covering the objective, executable commands, project structure, code style, testing strategy, boundaries, success criteria, and open questions to align stakeholders before implementation begins.

How does the gated four-phase workflow work for software development tasks?▼

The gated four-phase workflow sequences tasks through Specify, Plan, Tasks, and Implement phases with human review gates at each phase to avoid premature implementation and ensure engineers agree on what done means.

How do I break down project plans into testable tasks with acceptance criteria?▼

Break down project plans by decomposing them into small, testable tasks with explicit acceptance criteria and verification steps. This task decomposition ensures each implementation piece meets defined success criteria before moving forward.

Is a specification document necessary for small code changes and bug fixes?▼

A specification document is not necessary for small code changes. This approach applies to multi-file features, architectural decisions, and tasks expected to take more than thirty minutes where ambiguous requirements could cause costly rework.