spec-driven-development

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

Create structured specifications before implementation begins.

Updated May 3, 2026

Search Tags:#workflow #planning #documentation #specification #requirements #implementation #review

Ready to run

npx skills add https://github.com/kevindree/geehoo-gateway --skill spec-driven-development-kevindree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/kevindree/geehoo-gateway/tree/main/.github/skills/spec-driven-development
Command: npx skills add https://github.com/kevindree/geehoo-gateway --skill spec-driven-development-kevindree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a vague idea into a clear, reviewable specification before any code is written, reducing rework and misalignment.

Core Features & Use Cases

Clarify requirements: Surfaces assumptions and asks targeted questions when goals are ambiguous.
Structure the work: Captures objective, commands, project structure, code style, testing strategy, and boundaries in one spec.
Guide delivery: Breaks work into phased planning, task creation, and implementation checkpoints for larger changes.
Use case: Start a new feature, redesign a module, or document a multi-step change that needs human approval before implementation.

Quick Start

Use the spec-driven development skill to draft a concise specification for my new feature, including assumptions, success criteria, and a phased implementation 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 turn vague feature ideas into reviewable specifications before coding?▼

To turn vague ideas into reviewable specifications, define objectives, project structure, code style, and testing strategy upfront. This process surfaces assumptions and asks targeted questions to reduce rework and misalignment.

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

Spec-driven development creates structured specifications before implementation begins. Use it for new projects, ambiguous features, multi-file changes, and architectural decisions requiring clarification and human review.

How do I structure a specification for multi-file changes and architectural decisions?▼

Structure specifications by capturing objectives, commands, project structure, code style, testing strategy, and boundaries in one document. Break work into phased planning, task creation, and implementation checkpoints for reliable delivery.

Does spec-driven development work for redesigning an existing module?▼

Yes, spec-driven development works for redesigning a module by drafting a concise specification that includes assumptions, success criteria, and a phased implementation plan to guide delivery and clarify boundaries.

What is the best way to phase implementation checkpoints for large software projects?▼

The best way to phase implementation checkpoints is by breaking work into staged planning, task creation, and implementation steps. This captures boundaries and testing strategy to ensure reliable delivery for larger changes.