Central authority for specification-driven development. Use when working with requirements, specifications, acceptance criteria, or any spec-driven workflow. Provides navigation to specialized skills and delegates to docs-management for official documentation.
Central hub for specification-driven development. Use when starting spec workflows, converting formats, or navigating to specialized authoring skills like EARS, Gherkin, or Spec Kit.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install spec-driven-development@melodic-softwareThis skill is limited to using the following tools:
references/canonical-format.mdreferences/provider-matrix.mdreferences/workflow-phases.mdCentral hub for specification-driven development workflows. This skill provides navigation to specialized skills for different specification formats and workflows.
Keywords: specifications, requirements, acceptance criteria, spec-driven development, SDD, EARS, Gherkin, Kiro, Spec Kit, BDD, user stories, feature specifications, canonical spec
Use this skill when:
What do you want to do?
/spec:speckit:run or see speckit-workflow skill/spec:specify command/spec:convert commandThe canonical specification model (ADR-115) supports multiple providers:
| Provider | Format | Best For |
|---|---|---|
| ears | EARS syntax | Precise, unambiguous requirements |
| gherkin | .feature files | BDD tests with Reqnroll |
| kiro | AWS Kiro | IDE integration with steering files |
| speckit | GitHub Spec Kit | AI agent prompts, 5-phase workflow |
| adr | MADR format | Architecture decisions |
| userstory | Agile format | Product backlog items |
| canonical | YAML/JSON | Direct canonical format |
The GitHub Spec Kit workflow guides feature development:
| Phase | Artifact | Purpose |
|---|---|---|
| 0 | .constitution.md | Project principles and constraints |
| 1 | feature.md | Specification from requirements |
| 2 | design.md | Implementation approach |
| 3 | tasks.md | Task breakdown |
| 4 | Code | Guided implementation |
Full workflow: Use /spec:speckit:run or invoke the speckit-workflow skill.
All providers transform to/from the canonical model:
id: "SPEC-001"
title: "Feature Title"
type: feature | bug | chore | spike | tech-debt
context:
problem: "Description of the problem"
motivation: "Business value"
requirements:
- id: "REQ-001"
text: "EARS-formatted requirement"
priority: must | should | could | wont
ears_type: ubiquitous | state-driven | event-driven | unwanted | complex | optional
acceptance_criteria:
- id: "AC-001"
given: "Precondition"
when: "Action"
then: "Expected outcome"
traceability:
adr_refs: ["ADR-115"]
requirement_refs: ["FR-001"]
metadata:
status: draft
created: "YYYY-MM-DD"
provider: canonical
bounded_context: "WorkManagement"
Full schema: See canonical-spec-format skill or schemas/canonical-spec.schema.json
| Command | Purpose |
|---|---|
/spec:specify | Phase 1: Generate specification from requirements |
/spec:plan | Phase 2: Generate implementation plan |
/spec:tasks | Phase 3: Generate task breakdown |
/spec:implement | Phase 4: Guide implementation |
/spec:validate | Validate specification against schema |
/spec:refine | AI-assisted specification refinement |
/spec:audit | Audit specification quality |
/spec:convert | Convert between formats |
| Command | Purpose |
|---|---|
/spec:ears:author | Interactive EARS pattern authoring |
/spec:ears:convert | Convert to/from EARS format |
/spec:gherkin:author | Interactive Gherkin scenario authoring |
/spec:gherkin:convert | Convert to/from .feature files |
/spec:kiro:sync | Sync with AWS Kiro specifications |
/spec:speckit:run | Execute full Spec Kit 5-phase workflow |
/spec:adr:create | Create ADR from specification context |
/spec:userstory:author | Author user stories with acceptance criteria |
/spec:constitution | Create or update project constitution |
/spec:status | Show specification status dashboard |
This skill delegates to specialized skills for detailed guidance:
| Topic | Delegate To |
|---|---|
| EARS patterns | ears-authoring skill |
| Gherkin/BDD | gherkin-authoring skill |
| AWS Kiro | kiro-integration skill |
| Spec Kit workflow | speckit-workflow skill |
| Quality criteria | requirements-quality skill |
| Canonical format | canonical-spec-format skill |
| Official Claude Code docs | docs-management skill |
This plugin integrates with project infrastructure:
| Resource | Purpose |
|---|---|
schemas/canonical-spec.schema.json | Canonical specification JSON Schema |
prompts/specify.prompt.md | Generation template for Phase 1 |
templates/EARS-REQUIREMENT-TEMPLATE.md | EARS pattern reference |
docs/adr/ADR-115-* | Specification Provider Abstraction |
Detailed Documentation:
Last Updated: 2025-12-24
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.