spec-driven-development

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

Guide software development through design, proposal, and task documents.

Updated Aug 23, 2026

Search Tags:#design #software development #task breakdown #spec-driven development #proposal #requirement gathering

Ready to run

npx skills add https://github.com/kazuho39/kzo-document --skill spec-driven-development-kazuho39

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically organize development requirements, moving from a vague idea to concrete design, proposals, and actionable tasks, ensuring clarity and alignment before implementation.

Core Features & Use Cases

Requirement Clarification: Transforms ambiguous requests into well-defined specifications.
Phased Deliverables: Generates design, proposal, and tasks documents sequentially.
Use Case: A stakeholder provides a high-level feature request. You use this Skill to guide them through defining the scope, functional requirements, non-functional requirements, and finally break it down into development tasks.

Quick Start

Use the spec-driven-development skill to organize the requirement for a new user authentication feature.

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 a vague software idea into actionable development tasks?▼

You can turn a vague idea into actionable development tasks by sequentially generating design, proposal, and task documents. This structured approach clarifies scope and defines functional and non-functional requirements before implementation begins.

What is spec-driven development and when do I need it for software projects?▼

Spec-driven development is a structured approach ensuring development efforts are based on well-defined specifications and actionable plans. You need it when transforming ambiguous stakeholder requests into clear requirement definitions and phased planning for alignment.

How do I structure requirement gathering for a new software feature?▼

Structure requirement gathering by guiding stakeholders through defining scope, functional requirements, and non-functional requirements. This systematic organization moves from a high-level request to concrete design and proposal documents, ensuring clarity.

Can I use this approach to break down a large software proposal into smaller tasks?▼

Yes, you can use this approach to break down a large software proposal into smaller tasks. It generates a dedicated tasks document as a final phased deliverable, ensuring all development efforts are actionable and well-defined.

What documents are needed for phased planning in software development?▼

Documents needed for phased planning are design, proposal, and tasks documents. Generating these sequentially ensures that requirement definition and scope management are addressed systematically before implementation starts.