# specification

SPARC specification subagent for requirements analysis. Gathers acceptance criteria, outlines project scope, and learns from previous patterns via claude-flow.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/agentic-flow/.claude/agents/sparc/specification.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/ruvnet-specification

## What it does

This analyst subagent covers the Specification phase of the SPARC framework. It breaks down raw task inputs into project scope, acceptance criteria, and technical constraints. Before processing, it queries the ReasoningBank memory to identify matching patterns from previous tasks.

Execution hooks rely on `npx claude-flow@alpha`. The `pre` hook searches past records with a minimum reward score of 0.8 and records the session start. Once done, the `post` hook logs token counts, latency, and quality scores, then triggers neural pattern training for 50 epochs on successful runs.

Hooks will fail silently or throw errors if Node.js and the `claude-flow` CLI are missing from your environment.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/specification.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/specification.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/specification.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/agentic-flow/.claude/agents/sparc/specification.md

## When to use it
- extract functional requirements and project scope from raw task descriptions
- structure acceptance criteria before writing code
- retrieve proven specification patterns from previous runs
- track requirement quality metrics and latency across sessions

## Example prompts
- Draft the specification and acceptance criteria for user authentication.
- Analyze project constraints and scope for our new billing service.

## Similar
- [sparc-spec](https://affpapa.org/en/nevibecode/skills/sparc-spec.md) — skill · 733 installs
- [technical-specification](https://affpapa.org/en/nevibecode/skills/technical-specification.md) — skill · 816 installs
- [create-specification](https://affpapa.org/en/nevibecode/skills/create-specification.md) — skill · 13537 installs
- [create-github-action-workflow-specification](https://affpapa.org/en/nevibecode/skills/create-github-action-workflow-specification.md) — skill · 10745 installs
- [pptx-slide-specification](https://affpapa.org/en/nevibecode/skills/pptx-slide-specification.md) — skill · 2600 installs
- [specification-writing](https://affpapa.org/en/nevibecode/skills/specification-writing.md) — skill · 515 installs

## Other versions with the same name
- [Specification · github](https://affpapa.org/en/nevibecode/agents/specification.md) — 298 installs

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
