spec-driven-development

Manage, enforce, and rescue structured product specifications with YAML and Markdown.

25|5|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/nikolanovoselec/codeflare --skill spec-driven-development-nikolanovoselec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/nikolanovoselec/codeflare/tree/main/preseed/agents/claude/skills/spec-driven-development
Command: npx skills add https://github.com/nikolanovoselec/codeflare --skill spec-driven-development-nikolanovoselec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining consistent, disciplined, and automated product specifications, reducing manual oversight and errors.

Core Features & Use Cases

  • Specification Enforcement: Defines, reviews, and enforces product specs through command-driven workflows.
  • Workflow Automation: Supports project bootstrap, spec rescue, and mode switching to ensure specification discipline.
  • Use Case: A product team can initialize a new spec or rescue a broken one automatically, ensuring compliance with structured requirements and traceability.

Quick Start

Request the Skill to initialize a new product spec, and it will generate scaffolding, templates, and guiding documents for a comprehensive project setup.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I automate product specification enforcement for a new project?

Product specification enforcement is automated by initializing a new spec, which generates scaffolding, templates, and guiding documents to ensure structured requirements and traceability are maintained from the start.

What is the best way to rescue a broken or inconsistent product specification?

Rescuing a broken product specification involves executing a spec rescue workflow that automatically restores compliance with structured requirements, reducing manual oversight and correcting documentation errors.

Do I need YAML and Markdown parsing libraries to manage structured product specifications?

YAML and Markdown parsing libraries are required to manage structured product specifications, as the system relies on these formats for parsing spec files and generating project templates.

How does workflow automation handle mode switching in specification-driven project setup?

Workflow automation handles mode switching by enforcing specification discipline through command-driven workflows, ensuring that project bootstrap and ongoing requirements management remain consistent.

Can I use this specification enforcement approach for quality assurance and process automation?

Specification enforcement is applicable for quality assurance and process automation scenarios, enabling teams to define clear requirements, workflows, and documentation to reduce manual errors.

When should I not use automated product specification workflows?

Automated product specification workflows may not suit projects lacking defined requirements or those not using YAML and Markdown, as the enforcement and rescue mechanisms depend on structured file formats.