spec-driven-dev

Convert vague feature ideas into testable specifications before coding.

13|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/mauromedda/agent-toolkit --skill spec-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/mauromedda/agent-toolkit/tree/main/skills/spec-driven-dev
Command: npx skills add https://github.com/mauromedda/agent-toolkit --skill spec-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development framework that converts vague feature ideas into explicit, testable specifications before any code is written, reducing risk and rework.

Core Features & Use Cases

  • Iterative specification workflow: Guides teams through /spec.plan, /spec.refine, /spec.clarify, /spec.tasks, and /spec.run to produce a clear execution plan.
  • Open Questions governance: Captures ambiguities and edge cases, ensuring all questions are resolved before execution.
  • Task-based delivery: Produces high-level tasks with acceptance criteria to structure implementation into manageable phases.
  • Cross-skill orchestration: Coordinates language-specific skills (e.g., Python, Go) and architectural patterns for coherent designs.
  • Use Case: A product team drafts a feature spec that becomes a runnable plan with verifiable criteria.

Quick Start

To begin, run /spec.plan with your feature intent, review the generated questions, then use /spec.clarify or /spec.refine to progress toward a ready-to-run spec.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema
How do I convert a vague feature idea into a testable specification before coding?

Converting a vague feature idea into a testable specification requires an iterative workflow that captures intent, resolves open questions, and breaks down tasks into verifiable acceptance criteria before coding begins, reducing rework.

What is the best way to break down feature specs into manageable implementation tasks?

Breaking down feature specs into manageable implementation tasks involves generating a structured execution plan with high-level tasks and verifiable acceptance criteria, ensuring all ambiguities and edge cases are resolved before execution begins.

How do I capture and resolve open questions during feature planning?

Capturing and resolving open questions during feature planning requires a governance process that identifies ambiguities and edge cases, enforcing that all questions are clarified and decisions are traceable before moving to the task execution phase.

Can I orchestrate language-specific skills like Python or Go within a spec-driven workflow?

You can orchestrate language-specific skills like Python or Go within a spec-driven workflow by using cross-skill coordination to align explicit specifications and architectural patterns, ensuring coherent designs and reliable, auditable delivery.

When should I not use a spec-driven development approach for feature delivery?

You should not use a spec-driven development approach when rapid prototyping is required without explicit acceptance criteria, as this framework enforces resolving all open questions and producing testable specifications before any coding begins.