sparc-specification

name	sparc-specification
description	SPARC Specification phase specialist for requirements analysis, constraint identification, use case definition, and acceptance criteria creation
version	1.0.0
category	development
type	hybrid
capabilities	["requirements_gathering","constraint_analysis","acceptance_criteria","scope_definition","stakeholder_analysis"]
tools	["Read","Write","Edit","Grep","Glob"]
related_skills	["sparc-pseudocode","sparc-architecture","sparc-refinement"]
hooks	{"pre":"echo \"SPARC Specification phase initiated\"\nmemory_store \"sparc_phase\" \"specification\"\nmemory_store \"spec_start_$(date +%s)\" \"Task: $TASK\"\n","post":"echo \"Specification phase complete\"\nmemory_store \"spec_complete_$(date +%s)\" \"Specification documented\"\n"}
requires	[]
tags	[]

Sparc Specification

Quick Start

# Invoke SPARC Specification phase

# Or directly in Codex
# "Use SPARC specification to define requirements for user authentication"

When to Use

• Starting a new feature or project that needs clear requirements
• Translating stakeholder needs into technical specifications
• Creating acceptance criteria for user stories
• Documenting constraints (technical, business, regulatory)
• Defining use cases with preconditions and postconditions

Prerequisites

• Clear understanding of project goals
• Access to stakeholders for requirements validation
• Knowledge of existing system constraints
• Understanding of compliance requirements (if applicable)

References

• Gherkin Syntax
• IEEE 830 SRS Standard

Version History

• 1.0.0 (2026-01-02): Initial release - converted from agent to skill format

Sub-Skills

• Execution Checklist
• Best Practices
• Error Handling

Sub-Skills

• SPARC Specification Phase (+1)
• Requirements Document Structure (+3)
• Configuration
• Example 1: API Requirements
• 1.1 Purpose (+2)
• 2.1 Authentication (+1)
• 3.1 Performance (+2)
• Metrics & Success Criteria
• MCP Tools (+2)