spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: ankurjain1121

Generate a specs directory with design, API contracts, modules, implementation order, and constraints.

1|Updated Jan 15, 2026

Search Tags:#planning #handoff #specs #orchestrate #design-doc #api-contracts

Ready to run

npx skills add https://github.com/Ankurjain1121/dev-workflow-skills --skill spec-driven-development-ankurjain1121

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Ankurjain1121/dev-workflow-skills/tree/main/plugins/framework-dev/skills/spec-driven-development
Command: npx skills add https://github.com/Ankurjain1121/dev-workflow-skills --skill spec-driven-development-ankurjain1121

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After Phase 3 (Planning) produces API contracts and coding sequences, this Skill generates a specs/ directory compatible with /orchestrate and /implement workflows, enabling a smooth handoff to execution teams.

Core Features & Use Cases

Spec generation: Produce specs/[project-name]/ including design.md, api-contracts.md, modules.md, implementation-order.md, and constraints.md.
Handoff-ready documentation: Aligns engineering teams and external partners with a single source of truth for architecture, modules, and execution sequence.
Workflow compatibility: Ensures outputs are consumable by /orchestrate and /implement pipelines for deterministic execution.

Quick Start

Invoke spec-driven-development after Phase 3 to generate the specs folder for your project, e.g., specs/my-project/ with the required files.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I generate handoff-ready specs for orchestrate and implement workflows?▼

To generate handoff-ready specs, invoke this Skill after Phase 3 planning approval to create a specs/[project-name]/ directory containing design.md, api-contracts.md, modules.md, implementation-order.md, and constraints.md aligned with orchestrate and implement pipelines.

What is a specs directory and when do I need one for project handoff?▼

A specs directory is a structured documentation folder providing a single source of truth for architecture, modules, and execution sequence. You need one after Phase 3 planning to align engineering teams and external partners before implementation begins.

How do I create API contracts and design docs for developer handoff?▼

You create API contracts and design docs by running this Skill post-Phase 3, which automatically outputs structured files like api-contracts.md and design.md into the specs/[project-name]/ folder for external teams and developers.

Can I use these generated specs with orchestrate and implement pipelines?▼

Yes, the generated specs are fully compatible with orchestrate and implement workflows. The Skill ensures outputs like implementation-order.md and constraints.md are consumable by these pipelines for deterministic execution.

Do I need Phase 3 planning approval before generating design docs and module specifications?▼

Yes, Phase 3 planning approval is required because the Skill applies afterward to transform approved API contracts and coding sequences into structured documentation for execution teams.

What files are included in a generated specs folder for orchestration handoff?▼

The generated specs folder includes design.md, api-contracts.md, modules.md, implementation-order.md, and constraints.md, providing comprehensive documentation for architecture, modules, and execution sequence alignment.