spec-driven-development

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

Convert ambiguous requirements into a structured spec with scope and success criteria.

Updated Apr 27, 2026

Search Tags:#acceptance criteria #assumptions #spec #scope #requirements clarification #project-definition #planning readiness

Ready to run

npx skills add https://github.com/Handy369/passto-pi-frame --skill spec-driven-development-handy369

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Handy369/passto-pi-frame/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/Handy369/passto-pi-frame --skill spec-driven-development-handy369

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a request is missing boundaries, assumptions, or measurable success criteria, implementation starts with guesswork and leads to rework.

Core Features & Use Cases

Scope and non-goals crystallization: Converts ambiguous intent into an explicit what/what-not scope.
Acceptance criteria and success criteria: Rewrites success conditions into verifiable criteria to guide delivery.
Assumptions, open questions, and boundaries: Surfaces uncertainties early so planning and implementation can proceed safely.

Quick Start

Ask the agent to adopt spec-driven-development to convert your current partial requirements into a structured spec with scope, non-goals, assumptions, open questions, and testable 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 fuzzy project requirements into clear specs with measurable success criteria?▼

To turn fuzzy requirements into clear specs, convert ambiguous intent into a structured project definition featuring explicit scope, non-goals, assumptions, open questions, and verifiable acceptance criteria. This structured spec skeleton ensures planning and implementation proceed safely without guesswork.

What is requirements clarification and when do I need to define project scope and non-goals?▼

Requirements clarification is the process of converging incomplete boundaries into a structured spec. You need to define project scope and non-goals when a request lacks measurable success criteria, ensuring work is ready for specification convergence rather than direct coding or task breakdown.

How do I write verifiable acceptance criteria from ambiguous project requests?▼

To write verifiable acceptance criteria, rewrite ambiguous success conditions into explicit, testable standards that guide delivery. This process surfaces assumptions and open questions early, converting partial requirements into a structured spec skeleton suitable for downstream planning.

Can I use spec-driven development for task breakdown and direct coding?▼

No, you cannot use spec-driven development for task breakdown and direct coding. It enforces exclusions for discovery, research, and implementation, strictly producing a clear spec skeleton suitable for downstream planning when boundaries or acceptance conditions are incomplete.

What's the best way to surface assumptions and open questions before starting implementation?▼

The best way to surface assumptions and open questions is to apply specification convergence to partial requirements. This crystallizes boundaries and non-goals early, producing a structured spec skeleton that ensures planning and implementation can proceed safely without rework.