skills.rest
authrain-cloud-abdullahformuli
authrain-cloud-abdullahformuliCOMMUNITY
Explore all skills by this author →
𝕏@abdullahformuliGitHub

spec-driven-development

Creates structured specifications with gated review phases before writing code.

Updated Sep 17, 2026
Search Tags:#workflow#planning#specification#requirements#spec-driven development#prd#capability map
One-click install
npx skills add https://github.com/authrain-cloud-abdullahformuli/agent-skills --skill spec-driven-development-authrain-cloud-abdullahformuli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/authrain-cloud-abdullahformuli/agent-skills/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/authrain-cloud-abdullahformuli/agent-skills --skill spec-driven-development-authrain-cloud-abdullahformuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written without a specification leads to rework, misunderstood requirements, and undocumented architectural decisions. This Skill enforces a gated Specify → Plan → Tasks → Implement workflow so requirements are clarified and approved before any code exists. ## Core Features & Use Cases - Gated Four-Phase Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Capability Map Decomposition: Detects when one requirement bundles several independently testable capabilities and proposes a module map with dependency direction and build order before any spec is written. - Structured Spec Template: Covers six core areas — objective, commands, project structure, code style, testing strategy, and three-tier boundaries (Always / Ask First / Never). - Use Case: When asked to build a new billing feature with vague requirements, the Skill surfaces assumptions, reframes them into testable success criteria, writes a spec document, and only then plans and implements tasks. ## Quick Start Ask the agent to write a specification for your new feature before any code is written, and approve each phase as it is produced.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I write a specification before coding a new feature?▼

Start with a high-level vision, ask clarifying questions, and surface assumptions explicitly. Then write a spec covering objective, commands, project structure, code style, testing strategy, and boundaries, and get human approval before planning or implementing.

What is spec-driven development in software engineering?▼

Spec-driven development is a workflow where a written specification is the shared source of truth before code exists. It progresses through gated phases — Specify, Plan, Tasks, Implement — with human review required before advancing to the next phase.

When should I decompose a requirement into a capability map?▼

Decompose when one requirement bundles several independently testable capabilities, such as identity, billing, and notifications. Propose a small module table with dependency direction and build order, get it approved, then run the full workflow per module.

When should I skip writing a spec?▼

Skip the full spec for single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. Simple tasks still benefit from a two-line spec with acceptance criteria rather than no spec at all.

Can I use this workflow with OpenSpec or other spec tools?▼

Yes, the workflow is format-agnostic. If a project already uses OpenSpec or another specification system, keep that tool's artifact format and storage conventions while this workflow owns the clarification, content, and approval gates.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
19

dev-swarm-stage-init-ideas

Transform raw ideas into structured business requirements with problem, solution, and target users.

Official
Intermediate
22Teikk22Teikk

planning-and-task-breakdown

Decomposes specs into ordered, testable tasks with acceptance criteria and dependency-aware execution waves.

Community
Advanced
hashintelhashintel
7

ln-design

Generates and compares alternative module shapes and API boundary designs.

Official
Intermediate
rmansrmans

scaffold-new-prototype

Create prototype documents with unique PROTO-### IDs and index registration.

Community
Intermediate