Help us improve
Share bugs, ideas, or general feedback.
From hyrex-sparc
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
npx claudepluginhub akhilyad/deployy --plugin hyrex-sparcHow this skill is triggered — by the user, by Claude, or both
Slash command
/hyrex-sparc:sparc-spec <feature-description><feature-description>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run Phase 1 of the SPARC methodology: define what must be built and how success is measured.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Run Phase 1 of the SPARC methodology: define what must be built and how success is measured.
When starting a new feature or project that needs structured requirements gathering before any code is written. This phase produces the foundational specification that all subsequent phases (Pseudocode, Architecture, Refinement, Completion) build upon.
Initialize phase tracking — call mcp__hyrex__hooks_intelligence_trajectory-start with metadata { "phase": "specification", "feature": "$ARGUMENTS" }
Check for prior work — call mcp__hyrex__memory_search with namespace sparc-state and query for the feature to see if a SPARC workflow already exists. If it does, retrieve existing artifacts. If not, initialize state with phase 1.
Search for similar patterns — call mcp__hyrex__neural_predict with the feature description to find relevant past specifications and learned patterns
Gather requirements — analyze the feature description and the codebase to identify:
Define acceptance criteria — write at least 3 concrete, testable acceptance criteria in Given/When/Then format:
AC-1: Given [precondition], when [action], then [expected result]
AC-2: Given [precondition], when [action], then [expected result]
AC-3: Given [precondition], when [action], then [expected result]
Identify constraints — document:
Map edge cases — list at least 3 edge cases or failure scenarios:
Store specification — call mcp__hyrex__memory_store with:
sparc-phasesspec-{feature-slug}{ status: "complete", requirements, acceptanceCriteria, constraints, edgeCases, integrationPoints }Update phase state — call mcp__hyrex__memory_store with:
sparc-statecurrent-phase-{feature-slug}Record trajectory step — call mcp__hyrex__hooks_intelligence_trajectory-step with the specification summary
Present specification — display the full specification document to the user with a summary table and suggest running /sparc advance to pass the gate and move to the Pseudocode phase
# Specification: {Feature Name}
## Requirements
### Functional
- FR-1: ...
- FR-2: ...
### Non-Functional
- NFR-1: ...
## Acceptance Criteria
- AC-1: Given ..., when ..., then ...
- AC-2: Given ..., when ..., then ...
- AC-3: Given ..., when ..., then ...
## Constraints
- Performance: ...
- Security: ...
- Compatibility: ...
## Edge Cases
- EC-1: ...
- EC-2: ...
- EC-3: ...
## Integration Points
- IP-1: ...
---
Phase 1 complete. Run `/sparc advance` to pass the gate check.