Agent skill

Sparc Spec

by ruvnet in ruvnet/ruflo

Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

MITAuto-check: notesProduct & Project Management

Install Sparc Spec

skills CLI
$ npx skills add ruvnet/ruflo --skill sparc-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo sparc-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ruflo-sparc/skills/sparc-spec .claude/skills/sparc-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sparc-spec
GitHub stars
74k
Token cost
~1.1k tokens
SKILL.md length
328 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

  • Works in 11 steps: Initialize phase tracking — call… → Check for prior work — call… → Search for similar patterns — call… → …
  • Tasks that involve User stories
  • SKILL.md covers When to use, Steps and Output format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sparc Spec is an agent skill from ruvnet/ruflo. Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. It works with Model Context Protocol. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • Tasks that involve User stories

Example prompts

  • “/sparc-spec”

Requirements

  • Pre-approved tools (allowed-tools): mcp__plugin_ruflo-core_ruflo__memory_store, mcp__plugin_ruflo-core_ruflo__memory_search, mcp__plugin_ruflo-core_ruflo__memory_retrieve, mcp__plugin_ruflo-core_ruflo__task_create, mcp__plugin_ruflo-core_ruflo__task_update, mcp__plugin_ruflo-core_ruflo__task_complete, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-step, mcp__plugin_ruflo-core_ruflo__neural_predict, Bash, Read, Edit

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Initialize phase tracking — call mcpplugin_ruflo-core_ruflohooks_intelligence_trajectory-start with metadata { "phase": "specification"…
  2. Check for prior work — call mcpplugin_ruflo-core_ruflomemory_search with namespace sparc-state and query for the feature to see if a SPARC…
  3. Search for similar patterns — call mcpplugin_ruflo-core_rufloneural_predict with the feature description to find relevant past…
  4. Gather requirements — analyze the feature description and the codebase to identify
  5. Define acceptance criteria — write at least 3 concrete, testable acceptance criteria in Given/When/Then format
  6. Identify constraints — document
  7. Map edge cases — list at least 3 edge cases or failure scenarios
  8. Store specification — call mcpplugin_ruflo-core_ruflomemory_store with
  9. Update phase state — call mcpplugin_ruflo-core_ruflomemory_store with
  10. Record trajectory step — call mcpplugin_ruflo-core_ruflohooks_intelligence_trajectory-step with the specification summary
  11. Present specification — display the full specification document to the user with a summary table and suggest running /sparc advance to…

What it can do on your machine

Read from SKILL.md and the folder at commit 58e0ae7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • mcp__plugin_ruflo-core_ruflo__memory_store
    • mcp__plugin_ruflo-core_ruflo__memory_search
    • mcp__plugin_ruflo-core_ruflo__memory_retrieve
    • mcp__plugin_ruflo-core_ruflo__task_create
    • mcp__plugin_ruflo-core_ruflo__task_update
    • mcp__plugin_ruflo-core_ruflo__task_complete
    • mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start
    • mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-step
    • mcp__plugin_ruflo-core_ruflo__neural_predict
    • Bash

    …and 2 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sparc Spec loads about 1.1k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: mcp__plugin_ruflo-core_ruflo__memory_store, mcp__plugin_ruflo-core_ruflo__memory_search, mcp__plugin

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit 58e0ae7, republished under its MIT licence (© ruvnet). 328 words, ~1,088 tokens.

Download SKILL.mdSave it as .claude/skills/sparc-spec/SKILL.md (or your agent's skills folder).
name
sparc-spec
description
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
allowed-tools
mcp__plugin_ruflo-core_ruflo__memory_store, mcp__plugin_ruflo-core_ruflo__memory_search, mcp__plugin_ruflo-core_ruflo__memory_retrieve, mcp__plugin_ruflo-core_ruflo__task_create, mcp__plugin_ruflo-core_ruflo__task_update, mcp__plugin_ruflo-core_ruflo__task_complete, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-step, mcp__plugin_ruflo-core_ruflo__neural_predict, Bash, Read, Edit
argument-hint
<feature-description>

SPARC Specification Phase

Run Phase 1 of the SPARC methodology: define what must be built and how success is measured.

When to use

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.

Steps

  1. Initialize phase tracking — call mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start with metadata { "phase": "specification", "feature": "$ARGUMENTS" }

  2. Check for prior work — call mcp__plugin_ruflo-core_ruflo__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.

  3. Search for similar patterns — call mcp__plugin_ruflo-core_ruflo__neural_predict with the feature description to find relevant past specifications and learned patterns

  4. Gather requirements — analyze the feature description and the codebase to identify:

    • Functional requirements: what the feature must do (user-facing behaviors)
    • Non-functional requirements: performance targets, security constraints, scalability needs
    • Integration points: what existing systems or APIs are affected
    • Data requirements: what data is created, read, updated, or deleted
  5. 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]
  6. Identify constraints — document:

    • Performance constraints (latency, throughput, resource limits)
    • Security constraints (authentication, authorization, data sensitivity)
    • Compatibility constraints (browser support, API versions, backward compatibility)
    • Infrastructure constraints (deployment environment, dependencies)
  7. Map edge cases — list at least 3 edge cases or failure scenarios:

    • What happens with invalid input?
    • What happens under concurrent access?
    • What happens when external dependencies fail?
  8. Store specification — call mcp__plugin_ruflo-core_ruflo__memory_store with:

    • Namespace: sparc-phases
    • Key: spec-{feature-slug}
    • Value: JSON with { status: "complete", requirements, acceptanceCriteria, constraints, edgeCases, integrationPoints }
  9. Update phase state — call mcp__plugin_ruflo-core_ruflo__memory_store with:

    • Namespace: sparc-state
    • Key: current-phase-{feature-slug}
    • Value: updated state with artifacts list including the spec key
  10. Record trajectory step — call mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-step with the specification summary

  11. 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

Show full SKILL.md (2 more words)Show less

Output format

# 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.

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ruflo-sparc/skills/sparc-spec of ruvnet/ruflo.

Open the folder on GitHubat commit 58e0ae7

Compare with similar skills

Sparc Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sparc Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sparc Spec this skillruvnet/ruflo74k—~1.1kAutomated safety check: NotesMIT
Rocketmq Rust Good First Issuemxsm/rocketmq-rust1.5k—~2.3kAutomated safety check: PassApache-2.0
Cas Supervisor Checklistcodingagentsystem/cas176—~349Automated safety check: PassMIT
Harness Plan BriefChachamaru127/claude-code-harness3.2k—~2.2kAutomated safety check: NotesMIT
Chorus Task ReviewerChorus-AIDLC/Chorus1.2k—~4.2kAutomated safety check: PassAGPL-3.0
Chorus Task ReviewerChorus-AIDLC/Chorus1.2k—~6.9kAutomated safety check: PassAGPL-3.0

Similar skills

  • Help the rocketmq-rust repository owner or maintainer prepare and publish good first issues for new contributors to claim, with exact files, concrete changes, acceptance criteria, labels, and…

    1.5k GitHub stars~2.3k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Cas Supervisor Checklist

    codingagentsystem/cas

    Quick startup checklist for factory supervisors. An agent skill from codingagentsystem/cas.

    176 GitHub stars~349 tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed
  • Harness Plan Brief

    Chachamaru127/claude-code-harness

    Generate a Plan Brief HTML for non-engineer vibecoders before implementation starts.

    3.2k GitHub stars~2.2k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check: notes
  • Chorus Task Reviewer

    Chorus-AIDLC/Chorus

    Read-only Chorus task reviewer. An agent skill from Chorus-AIDLC/Chorus.

    1.2k GitHub stars~4.2k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Chorus Task Reviewer

    Chorus-AIDLC/Chorus

    Read-only Chorus task reviewer for Hermes. An agent skill from Chorus-AIDLC/Chorus.

    1.2k GitHub stars~6.9k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Dolt MCP Vcs

    jeremylongshore/tons-of-skills-marketplace

    Universal Dolt version-control workflow. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~3.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Questions about Sparc Spec

What does Sparc Spec do?

Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory. Sparc Spec is an agent skill from ruvnet/ruflo.

When should I use Sparc Spec?

Sparc Spec fits situations like: tasks that involve User stories.

How do I install Sparc Spec in Claude Code?

Run `npx skills add ruvnet/ruflo --skill sparc-spec -a claude-code`. Or copy the skill folder (plugins/ruflo-sparc/skills/sparc-spec in ruvnet/ruflo) into .claude/skills/sparc-spec in your project. Claude Code loads it when a task matches its description.

How do I install Sparc Spec in Codex?

Run `npx skills add ruvnet/ruflo --skill sparc-spec -a codex`. Or copy the skill folder (plugins/ruflo-sparc/skills/sparc-spec in ruvnet/ruflo) into .agents/skills/sparc-spec in your project. Codex loads it when a task matches its description.

Can I use Sparc Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill sparc-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sparc-spec, .gemini/skills/sparc-spec, .github/skills/sparc-spec and .opencode/skills/sparc-spec in your project.

What does Sparc Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Sparc Spec is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__plugin_ruflo-core_ruflo__memory_store, mcp__plugin_ruflo-core_ruflo__memory_search, mcp__plugin_ruflo-core_ruflo__memory_retrieve, mcp__plugin_ruflo-core_ruflo__task_create, mcp__plugin_ruflo-core_ruflo__task_update, mcp__plugin_ruflo-core_ruflo__task_complete, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start, mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-step, mcp__plugin_ruflo-core_ruflo__neural_predict, Bash, Read, Edit.

Does Sparc Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sparc Spec safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Sparc Spec use?

Sparc Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sparc Spec use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sparc Spec?

Skills that share tags, products or a category with Sparc Spec: Rocketmq Rust Good First Issue (mxsm/rocketmq-rust, 1.5k stars), Cas Supervisor Checklist (codingagentsystem/cas, 176 stars), Harness Plan Brief (Chachamaru127/claude-code-harness, 3.2k stars) and Chorus Task Reviewer (Chorus-AIDLC/Chorus, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sparc Spec?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,159 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 9, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.