skills.rest
apexradius
apexradiusOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-driven-dev

Guide creation of detailed specs, design documents, and task breakdowns for software features.

Updated Jun 21, 2026
Search Tags:#spec-driven#verification#task breakdown#requirements management#structured development
One-click install
npx skills add https://github.com/apexradius/agentic-os --skill spec-driven-dev-apexradius
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/apexradius/agentic-os/tree/main/skills/spec-driven-dev
Command: npx skills add https://github.com/apexradius/agentic-os --skill spec-driven-dev-apexradius

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers adopt a spec-driven development approach, ensuring that requirements are clearly defined before implementation, leading to more efficient and error-free development cycles.

Core Features & Use Cases

  • Structured Requirements: Encourages the creation of detailed requirements and design specs before coding.
  • Task Breakdown: Provides a systematic approach to breaking down tasks into manageable steps.
  • Verification: Ensures that the final implementation meets all specified requirements.
  • Use Case: Ideal for new projects or when starting a new feature, ensuring that all aspects of the feature are planned and documented upfront.

Quick Start

To begin spec-driven development, create a new feature spec in the 'specs/' directory with a name like 'feature-name.specs.md'.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema
How do I start spec-driven development for a new software feature?▼

To start spec-driven development, manually create a feature specification file in the 'specs/' directory using a format like 'feature-name.specs.md' to define requirements upfront before coding begins.

What is the best way to break down software requirements into manageable tasks?▼

The best way to break down software requirements is using a structured spec-driven approach that guides the creation of detailed design documents and systematically translates them into manageable, verifiable task steps.

How does structured requirements management improve the software development cycle?▼

Structured requirements management improves the development cycle by ensuring clear specs are defined before implementation, which minimizes errors and streamlines the verification of the final code against documented needs.

Do I need any specific frameworks to implement structured development and verification?▼

No specific frameworks are required to implement structured development and verification; the process relies on manually creating spec files and adhering to the defined task breakdown and verification steps.

When should I use a spec-driven approach over directly writing code?▼

Use a spec-driven approach over directly writing code when starting a new project or feature, ensuring all aspects are planned, documented, and verified upfront to prevent errors and inefficient development cycles.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
jrmatherlyjrmatherly

openspec-verify-change

Verify implementation against openspec change artifacts and generate prioritized reports.

Community
Advanced
jayteealaojayteealao

documentation-sync

Synchronize version numbers across project files and documentation references.

Community
Advanced
DocaariDocaari
1

test-writer

Generate executable tests from project specs and architecture diagrams.

Community
Advanced