sparc-specification

SPARC Specification phase specialist for requirements analysis, constraint identification, use case definition, and acceptance criteria creation

5 stars

byvamseeachanta

View on GitHub Installation ↓

Best use case

sparc-specification is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

SPARC Specification phase specialist for requirements analysis, constraint identification, use case definition, and acceptance criteria creation

Teams using sparc-specification should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/sparc-specification/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/development/sparc/sparc-specification/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/sparc-specification/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How sparc-specification Compares

Feature / Agent	sparc-specification	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

SPARC Specification phase specialist for requirements analysis, constraint identification, use case definition, and acceptance criteria creation

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Sparc Specification

## Quick Start

```bash
# 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](https://cucumber.io/docs/gherkin/)
- [IEEE 830 SRS Standard](https://standards.ieee.org/)

## Version History

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

## Sub-Skills

- [Execution Checklist](execution-checklist/SKILL.md)
- [Best Practices](best-practices/SKILL.md)
- [Error Handling](error-handling/SKILL.md)

## Sub-Skills

- [SPARC Specification Phase (+1)](sparc-specification-phase/SKILL.md)
- [Requirements Document Structure (+3)](requirements-document-structure/SKILL.md)
- [Configuration](configuration/SKILL.md)
- [Example 1: API Requirements](example-1-api-requirements/SKILL.md)
- [1.1 Purpose (+2)](11-purpose/SKILL.md)
- [2.1 Authentication (+1)](21-authentication/SKILL.md)
- [3.1 Performance (+2)](31-performance/SKILL.md)
- [Metrics & Success Criteria](metrics-success-criteria/SKILL.md)
- [MCP Tools (+2)](mcp-tools/SKILL.md)