spec-driven-workflow

Name: spec-driven-workflow
Availability: InStock
Author: patasse97

Generate RFC-compliant spec templates and extract executable tests from acceptance criteria.

Updated Apr 9, 2026

Search Tags:#automation #workflow #testing #specification #requirements #validation

Ready to run

npx skills add https://github.com/Patasse97/claude-skills --skill spec-driven-workflow-patasse97

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-workflow
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering/spec-driven-workflow
Command: npx skills add https://github.com/Patasse97/claude-skills --skill spec-driven-workflow-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Spec-driven workflow enforces writing a formal spec before coding, ensuring a single source of truth and a contract that guides implementation, reduces ambiguity, and speeds up delivery by aligning teams on requirements and tests.

Core Features & Use Cases

RFC-compliant spec templates generation, validation, and test extraction to drive development.
Integrated workflow from requirements gathering through acceptance criteria to test stubs.
Reusable references and templates enable consistent spec quality across projects.

Quick Start

Provide a feature name and a brief description to produce a complete spec skeleton and test stubs ready for review.

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 requirements into executable test stubs?▼

Spec-driven workflow generates a formal specification skeleton from your feature description and extracts executable test stubs directly from the resulting acceptance criteria.

What is a spec-first workflow and how does it reduce ambiguity?▼

A spec-first workflow enforces writing a formal specification before coding to establish a single source of truth. This contract guides implementation, reduces ambiguity, and aligns teams on requirements.

How do I validate specification documents using RFC 2119 keywords?▼

You validate specifications by checking for mandatory sections and standardized RFC 2119 keywords. The workflow provides integrated tooling to generate and validate specs to ensure consistent quality across projects.

Does this spec-driven workflow require any external dependencies?▼

No, the spec-driven workflow operates without external dependencies. It relies on built-in scripts and reusable references to standardize spec structure and maintain traceability from requirements to tests.

Can I use this for automated test generation from acceptance criteria?▼

Yes, you can automate test generation by providing a feature name and description. The workflow produces a complete spec skeleton and extracts test stubs from the acceptance criteria ready for review.