spec-driven-dev

Name: spec-driven-dev
Availability: InStock
Author: vivekmano27

Enforce a four-phase spec-driven workflow from requirements to implementation.

Updated Mar 14, 2026

Search Tags:#design #planning #spec-driven #requirements #tasks #code-review #phase-gates

Ready to run

npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill spec-driven-dev-vivekmano27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/spec-driven-dev
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill spec-driven-dev-vivekmano27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce a structured, plan-first development workflow that reduces ambiguity and rework by requiring clear specs, design validation, and task-driven implementation.

Core Features & Use Cases

Four-phase workflow (Requirements, Design, Tasks, Implementation) with gates and approvals.
Artifact outputs per phase (requirements.md, design.md, tasks.md) and controlled, atomic code changes via PRs.
Suitable for complex features and cross-functional teams that need explicit planning before coding.

Quick Start

Create a four-phase spec-driven plan for a feature named spec-driven-dev, detailing requirements, design, tasks, and implementation steps.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema

What is spec-driven development and how does it enforce a plan-first workflow?▼

Spec-driven development is a structured workflow that enforces plan-first coding by requiring clear specs, design validation, and task-driven implementation. It reduces ambiguity and rework through a four-phase process with mandatory phase gates and approvals.

How do I enforce design review before coding starts on complex features?▼

To enforce design review before coding, implement a four-phase workflow with phase gates that block implementation until a formal design review is approved. This ensures no coding begins before design artifacts are validated and signed off.

How to sequence implementation tasks for a complex software feature?▼

To sequence implementation tasks, generate a tasks.md artifact after design approval that breaks down work into atomic commits. Ensure each task has a specific verification command before implementation begins to maintain controlled progression.

Can I use phase gates for cross-functional product and engineering teams?▼

Yes, phase gates are suitable for cross-functional teams that need explicit planning before coding. The workflow spans product, design, and engineering roles by requiring approved requirements and design artifacts before implementation begins.

When should I not use spec-driven development for my project?▼

Spec-driven development should not be used for simple tasks that skip the need for formal specs, design artifacts, and task sequencing. It is designed specifically for complex features requiring controlled PR-based implementation and cross-functional alignment.

Why does spec-driven development require verification commands for each task?▼

Spec-driven development requires verification commands for each task to ensure atomic commits are validated before progression. This controlled PR-based implementation step guarantees that every sequenced task meets its specific acceptance criteria.