Individual skill

spec-workflow

This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase", "design phase", or "tasks phase". Provides structured 3-phase workflow for feature development.

plugins/Habib0x0/spec-driven-plugin/skills/spec-workflow/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,531
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-coding Repository topic
awesome Repository topic
awesome-list Repository topic
codex Repository topic
codex-plugins Repository topic
openai Repository topic
codex-skill Repository topic
codex-skills Repository topic
marketplace Repository topic
codex-marketplace Repository topic
design Derived category
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 8,512 bytes
SKILL.mdcore · 8,512 bytes
SKILL.mdcore · 8,512 bytes
references/design-patterns.mddoc · 10,408 bytes
references/ears-notation.mddoc · 6,107 bytes
references/task-breakdown.mddoc · 11,447 bytes

Read excerpt


# Spec-Driven Development Workflow

A structured approach to feature development through four phases: Brainstorm, Requirements, Design, and Tasks. This methodology prevents ad-hoc coding by ensuring proper planning before implementation.

## Overview

Spec-driven development transforms vague feature ideas into formal, traceable specifications:

```
Feature Idea → Brainstorm (Conversation) → Requirements (EARS) → Design (Architecture) → Tasks (Trackable)
```

## Phase 0: Brainstorm