spec-driven-dev

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

Execute end-to-end Spec-Driven Development planning with traceable proposals, reviews, and verifications.

5|1|Updated Jan 14, 2026

Search Tags:#workflow #planning #specification #spec #sdd #proposal #design-doc

Ready to run

npx skills add https://github.com/ValorVie/custom-skills --skill spec-driven-dev-valorvie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/ValorVie/custom-skills/tree/main/skills/spec-driven-dev
Command: npx skills add https://github.com/ValorVie/custom-skills --skill spec-driven-dev-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating changes across teams is often chaotic without a formal spec-driven process. This guide provides a repeatable workflow to create proposals, secure approvals, implement changes, verify outcomes, and archive artifacts with clear traceability.

Core Features & Use Cases

Structured proposal and review process for features, design changes, and architectural updates.
Bidirectional sync between specs, code reviews, and documentation to ensure alignment.
Suitable for product and engineering teams coordinating across multiple tools and repositories.

Quick Start

Create a spec proposal in specs/ and route it through OpenSpec-style tools to obtain approval before implementation.

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 formalize software changes?▼

Spec-driven development is a workflow that formalizes software changes through structured proposal, review, implementation, verification, and archive stages. It creates traceable proposals and design documents to coordinate changes across teams before implementation begins.

How do I create a spec proposal for a new feature?▼

To create a spec proposal, define your feature requirements and route them through a structured review process. This involves placing the proposal in a designated specs directory and obtaining approval before implementation to ensure traceable outcomes.

Does spec-driven development work for project-wide architectural updates?▼

Yes, spec-driven development applies to project-wide specs, feature proposals, design documentation, and architectural change requests. It enables bidirectional sync between specs, code reviews, and documentation across software projects and repositories.

Why use a spec-driven workflow instead of informal change coordination?▼

A spec-driven workflow replaces chaotic informal coordination with a repeatable process to secure approvals, implement changes, verify outcomes, and archive artifacts. This ensures clear traceability and alignment across product and engineering teams.

What is the best way to maintain alignment between specs and code reviews?▼

The best way to maintain alignment is using a spec-driven workflow with bidirectional sync between specifications, code reviews, and documentation. This structured process ensures that implementation matches the approved proposal and verification outcomes.

When do I need a formal specification process for my engineering team?▼

You need a formal specification process when planning and coordinating changes across multiple teams, tools, or repositories becomes too complex. It provides the structured proposal and review stages necessary to secure approvals and ensure verifiable implementation.