Skill

specify

Generates canonical specifications from feature requests or user stories using EARS notation, acceptance criteria, INVEST scores, and validation. Saves to .specs/{feature}/spec.md as phase 1 of spec-driven workflow.

Markdown

documentation

npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-development

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepWriteEditSkillTask

Preview

Generate a canonical specification from a feature request, user story, or requirements description.

SKILL.md

Similar Skills

spec-writing

275

Creates clear, testable specifications from feature descriptions with user stories, acceptance criteria, and measurable success metrics.

3 files

spec-kit

spec-management

Central hub for specification-driven development workflows. Navigates to specialized skills for EARS, Gherkin, Kiro, Spec Kit; supports format conversions, quality checks, and 5-phase Spec Kit workflow.

3 files4 tools

spec-driven-development

create-spec

Creates or updates SPEC.md documents from requirements, notes, or interview output, structuring into sections for goals, design, edge cases, security, testing, and success criteria. Use for feature specs.

1 file

amplify

Stats

Parent Repo Stars63

Parent Repo Forks9

Last CommitFeb 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Generate Specification

Generate a canonical specification from a feature request, user story, or requirements description.

Workflow

Parse Input
- If argument is a file path, read the file content
- If argument is inline text, use as feature description
- If no argument, prompt for feature description
Load Context
- Invoke spec-management skill for workflow guidance
- Invoke canonical-spec-format skill for schema reference
- Invoke ears-authoring skill for EARS patterns
Generate Specification
- Spawn spec-processor generate agent with the feature description
- Agent produces canonical specification with:
  - Problem statement and motivation
  - Scope (in-scope and out-of-scope)
  - EARS-formatted functional requirements
  - Non-functional requirements
  - Given/When/Then acceptance criteria
  - Dependencies and assumptions
Validate Output
- Spawn spec-reviewer validate agent to check schema compliance
- Verify all requirements have EARS format
- Verify all requirements have acceptance criteria
- Calculate INVEST scores
Save Specification
- Create .specs/ directory if needed
- Save specification to .specs/{feature-name}/spec.md
- Report generation summary with:
  - Number of requirements generated
  - INVEST scores
  - Validation status

Arguments

$ARGUMENTS - Feature description or path to requirements file

Examples

# From inline description
/spec-driven-development:specify "User authentication with email and password"

# From file
/spec-driven-development:specify requirements/auth-feature.md

# Interactive (no argument)
/spec-driven-development:specify

Output Location

Specifications are saved to:

.specs/{feature-name}/
  ├── spec.md           # Canonical specification
  └── (created by later phases)
      ├── design.md     # Phase 2: Implementation design
      └── tasks.md      # Phase 3: Task breakdown

Related Commands

/spec-driven-development:plan - Generate implementation design (Phase 2)
/spec-driven-development:tasks - Generate task breakdown (Phase 3)
/spec-driven-development:validate - Validate specification
/spec-driven-development:refine - AI-assisted refinement