spec-driven-development

Generate structured technical specification documents defining project scope, architecture, and success criteria.

22|4|Updated Feb 18, 2026

Search Tags:#planning #architecture #documentation #specification #requirements

Ready to run

npx skills add https://github.com/xiaoweidotnet/suifeng-skills --skill spec-driven-development-xiaoweidotnet

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the issue of ambiguous requirements and scope creep by forcing a structured, decision-based specification process before any code is written.

Core Features & Use Cases

Structured Specification: Automatically generates a comprehensive spec covering goals, tech stack, project structure, and testing strategies.
Decision Tracking: Maintains a clear record of all technical decisions and clarifications made during the design phase.
Use Case: When starting a new feature or project, use this skill to clarify requirements, define success criteria, and ensure all edge cases are addressed before implementation begins.

Quick Start

Ask the assistant to design a new user authentication feature using the spec-driven-development skill.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I generate technical specification documents for new feature development?▼

To generate technical specification documents, define project scope, architecture, and success criteria by applying a structured, decision-based process before coding. This clarifies ambiguous requirements and establishes a testable development plan.

What is the best way to prevent scope creep in software architecture planning?▼

Preventing scope creep in software architecture planning requires forcing a structured, decision-based specification process before any code is written. This approach defines clear goals, tech stack decisions, and testing strategies upfront.

How do I track technical decisions made during the requirements clarification phase?▼

Track technical decisions during requirements clarification by maintaining a clear record within the specification document. This ensures all design choices and edge case resolutions are documented before implementation begins.

When do I need to create a structured specification before implementation?▼

You need to create a structured specification before implementation when facing ambiguous project requirements or starting new feature development. It defines success criteria and ensures all edge cases are addressed prior to coding.

Does specification-driven development work for defining testing strategies and project structure?▼

Specification-driven development works for defining testing strategies and project structure by automatically generating a comprehensive spec. This covers goals, tech stack choices, and testing approaches to guide the implementation phase.