skills.rest
ruskicoder
ruskicoderCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven

Generates requirements, design, and task documents through three gated specification phases.

3|Updated Jun 29, 2026
Search Tags:#requirements#design document#task planning#spec-driven development#approval gates#kiro#ears format
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill spec-driven-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/spec-driven
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill spec-driven-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns rough feature ideas into structured, approved specifications before any code is written, preventing unclear requirements and uncontrolled autonomous implementation. ## Core Features & Use Cases - Three-Phase Workflow: Produces requirements.md with EARS-format acceptance criteria, design.md with architecture and data models, and tasks.md with a phased implementation checklist. - Explicit Approval Gates: Blocks progression between phases until the user explicitly approves each document, with feedback-revision cycles. - Controlled Task Execution: Executes one task at a time with status tracking and stop-and-review after each task. - Use Case: A developer describes a new user authentication feature; the agent writes EARS requirements, a technical design with Mermaid diagrams, and a traceable task list, then implements tasks one by one under user review. ## Quick Start Ask the agent to run the spec-driven workflow for your feature, for example: create a spec for a password reset flow.

Frequently Asked Questions about spec-driven

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

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

Invoke the workflow with a feature name or scope. The agent generates requirements.md with EARS acceptance criteria first, then design.md, then tasks.md, requesting your explicit approval before moving between each phase.

What is the EARS format for acceptance criteria?▼

EARS (Easy Approach to Requirements Syntax) uses structured patterns like WHEN/THEN for events, IF/THEN for conditions, and WHILE/THEN for continuous states. Each criterion follows the form: WHEN [event] THEN [system] SHALL [response].

When should I use spec-driven development vs direct implementation?▼

Use spec-driven development for complex features with multiple components, unclear requirements, or multi-session work. Use direct implementation for simple, well-understood changes like single-file edits where documentation overhead adds no value.

Where are the specification documents stored?▼

All three documents are stored in .kiro/specs/{feature_name}/ as requirements.md, design.md, and tasks.md. The agent reads all three files before executing any implementation task.

Can the agent execute multiple tasks automatically in sequence?▼

No. The workflow enforces a one-task-at-a-time rule: after completing each task, the agent updates its status, summarizes the work, and stops until you explicitly request the next task.

Related Skills

Explore More Software Engineering Skills→
shakhovskiya-createshakhovskiya-create

interview

Guide a structured interview to produce a discovery brief at docs/specs/<feature-slug>/brief.md.

Community
Advanced
shimaMatzshimaMatz

kiro-impl

Implement approved tasks from tasks.md using autonomous sub-agent dispatch or manual execution.

Community
Advanced
notta50notta50

kiro-steering-custom

Generate domain-specific steering documents with .kiro/steering files.

Community
Advanced
burgebjburgebj

octopus-quick

Execute small software changes with atomic commits and state tracking.

Community
Intermediate