spec-driven-dev

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

Coordinate feature development through SPEC, PLAN, and REVIEW templates.

Updated Jan 22, 2026

Search Tags:#workflow #planning #templates #documentation #collaboration #specification #review

Ready to run

npx skills add https://github.com/BryceEWatson/bryce-labs-toolkit --skill spec-driven-dev-bryceewatson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/BryceEWatson/bryce-labs-toolkit/tree/main/plugins/spec-workflow/skills/spec-driven-dev
Command: npx skills add https://github.com/BryceEWatson/bryce-labs-toolkit --skill spec-driven-dev-bryceewatson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development enforces a disciplined, reproducible workflow that transforms high-level ideas into actionable steps by using standardized SPEC, PLAN, and REVIEW templates.

Core Features & Use Cases

Provides a repeatable SPEC → PLAN → IMPLEMENT → REVIEW workflow to align cross-functional teams.
Supplies templates and guidance for drafting SPEC.md, PLAN.md, and REVIEW.md to accelerate planning and approvals.
Includes examples and guidelines for teams to adopt spec-driven development in product and software engineering projects.

Quick Start

Create the initial SPEC.md for your feature to start the workflow.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema

What is a spec-driven development workflow and how does it align cross-functional teams?▼

A spec-driven development workflow coordinates feature development through a strictly enforced SPEC, PLAN, IMPLEMENT, and REVIEW cycle to align cross-functional teams. It uses standardized templates to transform high-level ideas into actionable steps and reproducible outcomes.

How do I create implementation plans from feature specifications?▼

You create implementation plans by drafting an initial SPEC.md for your feature, then generating a PLAN.md file from that specification. This workflow uses a standard docs/specs/docs/plans structure to guide the planning process and accelerate approvals.

Do I need specific templates to start spec-driven feature planning?▼

Yes, spec-driven development requires templates for SPEC.md, PLAN.md, and REVIEW.md. You must create the initial SPEC.md for your feature to start the workflow and maintain a standard docs/specs/docs/plans directory structure for guidance.

What's the best way to structure project documentation for cross-functional collaboration?▼

The best way to structure project documentation for cross-functional collaboration is using a standard docs/specs/docs/plans directory. This structure supports standardized SPEC.md, PLAN.md, and REVIEW.md templates to guide the entire feature development lifecycle.

Can I use specification templates for PR-based code reviews?▼

Yes, the workflow explicitly supports PR-based reviews by using a REVIEW.md template. After drafting specifications and generating implementation plans, teams perform PR-based reviews to complete the end-to-end feature development cycle.