spec-workflow

Name: spec-workflow
Availability: InStock
Author: sn005

Enforce specification-driven workflows with acceptance criteria and TDD cycles.

1|Updated Dec 31, 2025

Search Tags:#tdd #branch #epic #pull-request #ac #subtask #spec-workflow

Ready to run

npx skills add https://github.com/Sn005/recommend-scp --skill spec-workflow-sn005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/Sn005/recommend-scp/tree/main/.claude/skills/spec-workflow
Command: npx skills add https://github.com/Sn005/recommend-scp --skill spec-workflow-sn005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specification-driven development workflows enforce disciplined planning and validation, preventing scope creep by automatically ensuring AC checks, TDD cycles, and completion verification during implementation.

Core Features & Use Cases

Automatic activation of the spec-driven workflow when starting Subtasks, with mandatory AC review and user confirmation.
End-to-end coordination across Phase → Epic/Story → Subtask, integrating test planning, code reviews, and status updates.
Use Case: When implementing a new feature, start a Subtask and let the system enforce AC adherence, tests, and proper handoffs to upstream tasks.

Quick Start

Start the spec-workflow for a Subtask to automatically validate ACs, run the TDD cycle, and verify completion.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema

How do I enforce acceptance criteria verification during subtask implementation?▼

Specification-driven development enforces acceptance criteria (AC) verification by automatically validating AC adherence before allowing subtask progression. This mechanism ensures mandatory AC review and user confirmation at task start, preventing scope creep during implementation.

What is specification-driven development and how does it prevent scope creep?▼

Specification-driven development is a process that reads specifications, parses acceptance criteria, and validates scope before implementation. It prevents scope creep by automatically enforcing AC checks, TDD cycles, and completion verification across Epic and Subtask phases.

How do I automate TDD cycles and code reviews across Epic and Subtask phases?▼

You can automate TDD cycles and code reviews by applying a spec-driven workflow to Epic and Subtask progression. The system coordinates end-to-end across phases, automatically validating test planning, code reviews, and status updates before allowing upstream task handoffs.

How to validate completion checks for specifications before pulling a request?▼

To validate completion checks for specifications, apply a spec-workflow that verifies implementation phases against parsed acceptance criteria. The system reads specs from the specs/ directory and validates scope completion before allowing pull-request progression.

Does spec-workflow require specific folder structures for reading acceptance criteria?▼

Yes, specification-driven workflow reads specifications directly from the specs/ directory to parse acceptance criteria. This folder structure is required to automatically validate scope and enforce TDD cycles during subtask implementation.

When should I use automated specification enforcement over manual code reviews?▼

Automated specification enforcement is ideal when implementing new features across multiple phases where scope creep is a risk. Use it over manual reviews when you need mandatory AC adherence, automated TDD cycle validation, and structured handoffs between Epic and Subtask.