spec-driven

Enforce a spec-first development pipeline with triage and phase gates.

4|Updated May 20, 2026
One-click install
npx skills add https://github.com/valorisa/Claude-Skills --skill spec-driven-valorisa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven
Source: https://github.com/valorisa/Claude-Skills/tree/main/skills/spec-driven
Command: npx skills add https://github.com/valorisa/Claude-Skills --skill spec-driven-valorisa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of ad-hoc coding leading to scope creep, mismatched implementations, and expensive post-development rewrites by enforcing a structured, spec-first workflow that pins down requirements before any code is written.

Core Features & Use Cases

  • 3-Way Task Triage: Automatically classifies tasks into FULL (complex multi-file work), LIGHT (small scoped changes), or SHIP (hotfixes/typos) tracks to match workflow overhead to task complexity.
  • Enforced Pipeline with Hard Gates: Requires explicit user validation after the specification and planning phases, preventing skipped steps and unvalidated implementation work.
  • Token Budget Management: Caps token usage per phase to ensure the workflow itself does not become a resource drain.
  • Use Case: When building a new OAuth2 login feature that touches multiple files and adds a new dependency, the skill ensures you validate the full specification and implementation plan before writing any code, reducing the risk of building the wrong feature.

Quick Start

Activate the spec-driven skill and describe the feature or task you want to complete to start the structured spec-first development pipeline.

Frequently Asked Questions about spec-driven

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

FAQPage Schema
How do I prevent scope creep and costly rewrites during software development?

Spec-driven development prevents scope creep and costly rewrites by enforcing a structured pipeline that requires user-validated specifications before any code is written. This ensures implementation strictly conforms to agreed requirements.

What is the best way to manage token usage when enforcing a spec-first workflow?

You can manage token usage in a spec-first workflow by applying per-phase token budgets. This caps resource consumption during specification, planning, and implementation to prevent the workflow itself from becoming a resource drain.

How do I automatically triage software development tasks by complexity?

You can automatically triage development tasks into FULL, LIGHT, and SHIP tracks based on task scope and complexity. This classifies complex multi-file work, small scoped changes, and hotfixes to match workflow overhead appropriately.

Can I enforce hard phase gates for validated requirements before implementation?

Yes, you can enforce hard phase gates by requiring explicit user validation after the specification and planning phases. This prevents skipped steps and ensures no unvalidated implementation work begins on complex multi-file features.

Does spec-driven development work for simple hotfixes and typo corrections?

Spec-driven development supports simple hotfixes and typo corrections by routing them to the SHIP track. This automatic triage ensures lightweight tasks bypass the heavy overhead required for complex multi-file feature development.

How do I handle divergence signaling when code implementation mismatches the specification?

Divergence signaling handles code implementation mismatches by flagging deviations from the user-validated specification. This controlled subagent authorization ensures full traceability and conformity throughout the structured development pipeline.