spec

Name: spec
Availability: InStock
Author: sn005

Convert natural language requirements into structured EPIC/Story/Subtask spec files.

1|Updated Dec 31, 2025

Search Tags:#workflow #specification #requirements #story #ears #epic #subtask

Ready to run

npx skills add https://github.com/Sn005/recommend-scp --skill spec-sn005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/Sn005/recommend-scp/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/Sn005/recommend-scp --skill spec-sn005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning natural language requirements into structured SD specifications (EPIC/Story/Subtask) to streamline up-front design and ensure traceability from ideas to implementation.

Core Features & Use Cases

Phase-driven workflow: Requirements → Design → Tasks, enabling gradual refinement with user confirmations.
EARS-based acceptance criteria: Generates unambiguous WHEN/GIVEN/THEN style AC.
End-to-end spec generation: Produces EPIC/Story/Subtask files and cross-links, plus branch/PR automation.

Quick Start

Provide a natural language requirement and the skill will generate EPIC/Story/Subtask specs through Requirements, Design, and Tasks phases.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I turn natural language requirements into structured software specifications?▼

To turn natural language requirements into structured software specifications, provide your text to automate transformation into hierarchical EPIC, Story, and Subtask files through a phased Requirements, Design, and Tasks workflow.

What are EARS-style acceptance criteria and how are they generated?▼

EARS-style acceptance criteria use unambiguous WHEN/GIVEN/THEN syntax to define software behavior. This workflow automatically generates EARS-based AC during the Design phase to ensure clear, testable requirements.

How do I break down an EPIC into stories and subtasks for implementation?▼

Breaking down an EPIC into stories and subtasks involves a phase-driven workflow moving from Requirements to Design to Tasks. The process generates hierarchical spec files with cross-links, requiring user confirmation before progressing.

Can I automate branch and PR creation from generated specification files?▼

Yes, you can automate branch and PR creation directly from generated specification files. The workflow includes review automation using /branch and /pr commands to link end-to-end design with downstream implementation.

Do I need to manually review specifications between the Requirements, Design, and Tasks phases?▼

You need to manually review specifications between phases because the workflow enforces user confirmation before phase progression and file generation. This ensures gradual refinement and traceability from ideas to implementation.

What is the best way to ensure traceability from initial ideas to implementation tasks?▼

The best way to ensure traceability from ideas to implementation tasks is generating cross-linked EPIC, Story, and Subtask spec files. This end-to-end transformation maintains structure from initial requirements through downstream implementation.