skills.rest
luminos-accessibility
luminos-accessibilityOFFICIAL
Explore all skills by this author →
GitHub

spec-driven-development

Decompose epics into planning and specification artifacts with YAML frontmatter.

2|Updated Mar 14, 2026
Search Tags:#design#planning#specification#sdd#subtasks#stories#epic-decomposition
One-click install
npx skills add https://github.com/luminos-accessibility/luminos --skill spec-driven-development-luminos-accessibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/luminos-accessibility/luminos/tree/main/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/luminos-accessibility/luminos --skill spec-driven-development-luminos-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Spec-driven development provides a disciplined, contract-first approach to planning Epics, decompose them into stories, and define design and validation artifacts before implementation.

Core Features & Use Cases

  • Decompose epics into HIGH_LEVEL_PLAN.md, STORY.md, DESIGN.md, and SUBTASKS.md to enable parallel workstreams.
  • Capture explicit acceptance criteria, test plans, and architectural decisions to align product, engineering, and AI agents.
  • Generate shared context and artifact templates that guide cross-story coordination and TDD execution.

Quick Start

Provide a HIGH_LEVEL_PLAN.md for Epic E01 and create a matching STORY.md, DESIGN.md, and SUBTASKS.md to enable TDD-driven development.

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 for epic decomposition?▼

Decompose epics by generating a HIGH_LEVEL_PLAN.md and creating matching STORY.md, DESIGN.md, and SUBTASKS.md files to define design and validation artifacts that enable parallel workstreams and TDD-driven development.

Do I need YAML frontmatter metadata for specification files?▼

Yes, the skill enforces YAML frontmatter metadata in specification files to provide shared context, guide cross-story coordination across artifacts, and ensure AI agents correctly process architectural decisions and explicit acceptance criteria.

How does spec-driven development handle remediation workflows?▼

The approach provides a remediation workflow that guides AI agents from planning through design and task execution, ensuring validation artifacts, architectural decisions, and testing strategies are enforced during implementation.

Can I use spec-driven development for test-driven development planning?▼

Yes, it generates artifact templates that guide cross-story coordination and TDD execution by capturing explicit test plans, acceptance criteria, and architectural decisions within STORY.md, DESIGN.md, and SUBTASKS.md files.

What's the best way to align AI agents with product specification artifacts?▼

Decompose epics into HIGH_LEVEL_PLAN.md, STORY.md, DESIGN.md, and SUBTASKS.md files with explicit acceptance criteria and testing strategies, providing shared context and templates that align product, engineering, and AI agents for parallel workstreams.

Related Skills

Explore More Product & Management Skills→
lluppesmslluppesms

breakdown-epic-pm

Generate a structured Markdown Epic PRD from epic idea and target user input.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

atdd-assistant

Guide Acceptance Test-Driven Development workflows for defining and validating user stories.

Community
Intermediate
chrono-metachrono-meta
7

context-bridge-dispatch

Coordinate parallel AI coding agents with context injection and task boundaries.

Community
Intermediate
OzeroHAXOzeroHAX
32

project-standart-epic

Decompose product requirements and architecture into prioritized epics with dependency mapping and acceptance criteria.

Community
Intermediate