spec-driven

Plan, define, and implement features through EARS-based spec-driven SDLC phases.

15|6|Updated Jan 20, 2026

Search Tags:#workflow #spec-driven #requirements #gates #sdlc #ears

Ready to run

npx skills add https://github.com/Snowflake-Labs/coco-skills --skill spec-driven-snowflake-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven
Source: https://github.com/Snowflake-Labs/coco-skills/tree/main/skills/spec-driven
Command: npx skills add https://github.com/Snowflake-Labs/coco-skills --skill spec-driven-snowflake-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Spec-Driven Development enforces a structured SDLC that requires clear, testable requirements defined in EARS notation before any code is written, reducing misalignment and regressions.

Core Features & Use Cases

EARS Requirement Workflow: Standardized specification format that is easy to validate and reuse across teams.
Mandatory Stopping Points: Explicit approval gates prevent proceeding until the user confirms each phase.
Phase-by-Phase Execution: Supports clarify, specify, validate, and implement stages with audit trails.
Spec Evolution & Drift Handling: Tracks changes, amends existing specs (without deleting history), and implements delta changes only.
Resumable Sessions: Session resume logic reads spec status to continue where left off.

Quick Start

Describe a feature you want to implement and the system will guide you through the phased spec-driven workflow.

Frequently Asked Questions about spec-driven

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

FAQPage Schema

How do I enforce EARS-based requirements before writing any code?▼

You can enforce EARS-based requirements by using a spec-driven SDLC workflow that mandates clarifying, specifying, and validating features through explicit approval gates before implementation begins. This prevents misalignment and regressions by requiring testable specifications upfront.

What is the best way to track requirement changes during software development?▼

Tracking requirement changes during software development is handled through spec evolution and drift management, which amends existing specifications without deleting history. This allows you to implement only delta changes while maintaining full traceability from requirement to delivery.

How do I implement a gated approval workflow for feature specifications?▼

Implementing a gated approval workflow involves executing phase-by-phase progression through clarify, specify, validate, and implement stages. Mandatory stopping points prevent proceeding to the next phase until explicit user confirmation is provided, ensuring structured validation.

Can I resume a paused feature specification session without losing progress?▼

Resuming a paused feature specification session is supported through session resume logic that reads your spec status. This allows you to continue exactly where you left off in the SDLC workflow without losing your prior clarifications, validations, or approval gate progress.

Why use EARS notation for software requirement specifications?▼

Using EARS notation for software requirement specifications provides a standardized format that is easy to validate and reuse across teams. It reduces misalignment by ensuring requirements are clear and testable before the implementation phase of the SDLC begins.

Does spec-driven development work for modifying existing feature requirements?▼

Spec-driven development works for modifying existing features by tracking spec evolution and handling drift. It amends existing requirements without deleting history, ensuring delta changes are implemented only after passing through mandatory validation and approval gates.