spec-driven-development

Coordinate spec-driven development stages with TDD and subagent roles.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill spec-driven-development-avatarganymede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill spec-driven-development-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires architect, implementer, test-engineer, qa, security-auditor, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures a standardized development workflow that includes spec creation, task decomposition, testing, and integration for efficient and bug-free software delivery.

Core Features & Use Cases

  • Spec-Driven Implementation: Offers a complete framework for implementing features and fixes.
  • Task Decomposition: Breaks down tasks into manageable parts.
  • Subagent Coordination: Manages multiple agents for different aspects of the development process.
  • Test-Driven Development (TDD): Supports development with a strong focus on testing.

Quick Start

Begin by using 'spec-driven-development' to start the process and clarify intent, then follow with the 'architect', 'implementer', 'test-engineer', and 'qa' subagents for their respective roles in the development cycle.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
What is spec-driven development and how does it standardize software workflows?

Spec-driven development establishes a standardized workflow by coordinating feature implementation across specification, task decomposition, implementation, testing, and quality assurance stages to ensure efficient, bug-free software delivery.

How do I implement TDD with subagent coordination for feature development?

You can implement TDD by using the spec-driven-development workflow to clarify intent, then delegating roles to the architect, implementer, test-engineer, and qa subagents for their respective stages in the development cycle.

Does spec-driven development require architecture and security auditor support?

Yes, spec-driven development requires architecture and security auditor support, utilizing the architect and security-auditor dependencies to validate structural design and security compliance throughout the feature implementation process.

What is the best way to decompose tasks for test-driven bug fixes?

The best way to decompose tasks for bug fixes is using the spec-driven-development framework, which breaks down complex bugs into manageable parts and coordinates the test-engineer and qa subagents to enforce test-driven validation.

Can I use this development workflow without the qa and test-engineer dependencies?

No, this workflow is designed to require the qa and test-engineer dependencies to execute its test-driven development stages, ensuring that both implementation and quality assurance are fully integrated into the delivery cycle.

Why should I use a spec-driven workflow over standard test-driven development?

A spec-driven workflow extends standard TDD by adding upfront specification creation and multi-agent coordination, ensuring that architecture, implementation, testing, and security auditing are systematically aligned before and during coding.