spec-driven-workflow

Convert informal requirements into EARS-compliant acceptance criteria.

3|1|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/iButters/ClaudeCodePlugins --skill spec-driven-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-workflow
Source: https://github.com/iButters/ClaudeCodePlugins/tree/main/plugins/spec-driven-workflow/skills/spec-driven-workflow
Command: npx skills add https://github.com/iButters/ClaudeCodePlugins --skill spec-driven-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, unstructured chaos of software development, transforming high-level ideas into production-ready software through a structured, multi-agent orchestrated workflow. It ensures consistency, reduces errors, and accelerates delivery.

Core Features & Use Cases

  • Structured SDLC: Guides you through IDEA → REQUIREMENTS → DESIGN → TASKS → EXECUTE → REVIEW, ensuring no step is missed.
  • Multi-Agent Orchestration: Leverages specialized subagents (backend, frontend, database, test, docs executors, plus reviewers) for parallel task execution and automated quality checks.
  • EARS Requirements: Utilizes an Easy Approach to Requirements Syntax for clear, unambiguous specification generation.
  • Use Case: You have a new product idea and need to quickly generate detailed requirements, architectural designs, and implementation tasks, then execute them with automated development and review cycles.

Quick Start

Start a new software project called 'my-new-app' and help me generate initial requirements.

Frequently Asked Questions about spec-driven-workflow

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

FAQPage Schema
How do I convert informal requirements into testable acceptance criteria?

Convert requirements using EARS (Easy Approach to Requirements Syntax), which structures them into six patterns: Ubiquitous, Event-Driven, State-Driven, Optional Feature, Error Handling, and Complex. This produces uppercase-keyword compliant, SHALL-based criteria that automated validators can verify.

Can I automate the entire software development workflow from idea to code?

Yes. The workflow orchestrates multiple specialized agents through IDEA → REQUIREMENTS → DESIGN → TASKS → EXECUTE → REVIEW stages, with parallel task execution across backend, frontend, database, and test components, plus automated quality reviews.

What's the best way to ensure requirements are clear and unambiguous across web, mobile, and API systems?

Apply EARS-compliant requirements that enforce structured syntax with uppercase keywords and SHALL usage. This eliminates ambiguity and produces rigorous, testable criteria verifiable by automated tools like ears-validator across all system types.

Do I need to manually write design documents and implementation tasks, or can they be generated?

Tasks and designs are generated automatically from requirements through multi-agent orchestration. Specialized subagents create architectural designs and implementation tasks in parallel, eliminating manual specification work.

How does this reduce errors and accelerate delivery in software development?

Structured SDLC prevents missed steps, EARS requirements eliminate ambiguity at the source, and multi-agent parallel execution compresses timelines. Automated reviewers catch errors before implementation, reducing rework cycles.

Can this approach work if I'm starting with just a high-level product idea?

Yes. The workflow transforms high-level ideas into production-ready software by systematically converting informal concepts through requirements, design, and task stages, ensuring consistency at every step.