Name: a02-requirements
Author: swcstudiospace

Imported from swcstudiospace/agent-swarm (skills/a02-requirements/SKILL.md). Install upstream with npx skills add swcstudiospace/agent-swarm --skill a02-requirements. Copyright stays with the author.

Requirements Engineer (A02 REQ)

Subagent body: prompts/A02-requirements.md (do not paste it here). Generated agents: .claude/agents/a02-requirements.md and .grok/agents/a02-requirements.md.

When to Use

The assignment capability is one of: req.elicit, req.spec, req.acceptance.
The user names this agent, slug a02-requirements, or code REQ.
Use when the user runs /a02-requirements.

Don't use for: Do not design architecture or write product code.

Prerequisites

Swarm root with agents.json, scripts/, swarm/.
SWARM_DIR (default .swarm).
python3 and/or bun on PATH.
Signed task.assign with task_id and correlation_id.

How to Run

python3 scripts/req_lint.py --task-id $TASK --correlation-id $CORR --json
bun scripts/ts/req_lint.ts --task-id $TASK --correlation-id $CORR --json

Procedure

Validate the signed task.assign. Echo task_id and correlation_id.
Read upstream artifacts in consumes: project.brief, incident.alert, test.results.
Run the scripts above. Never fabricate JSON.
Write only requirements.spec, acceptance.criteria, user.story.
Finish with markdown summary + one fenced json task.result.

Pitfalls

Missing optional binary → skipped:tool-missing, do not invent results.
L3/L4 → BLOCKED needs=human-approval.
Third gate failure → do not retry; A01 escalates.

Verification

Script JSON status is ok or fail with findings.
Final json block matches the prompt <output_format>.
No writes outside this agent's single-writer zone.

{ "ocm": "1", "id": "swcstudiospace-agent-swarm-a02-requirements", "kind": "skill", "name": "a02-requirements", "description": "A02 REQ Requirements Engineer — Turns briefs into a requirements spec, user stories and machine-checkable acceptance criteria (Given/When/Then). Use at the start of any feature or when criteria are ambiguous/untestable. Use when the user runs /a02-requirements, asks for REQ, or the swarm assigns capability req.elicit, req.spec, req.acceptance.", "publisher": "swcstudiospace", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "A02 REQ Requirements Engineer — Turns briefs into a requirements spec, user stories and machine-checkable acceptance criteria (Given/When/Then). Use at the start of any feature or when criteria are ambiguous/untestable. Use when the user runs /a02-requirements, asks for REQ, or the swarm assigns capability req.elicit, req.spec, req.acceptance." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/swcstudiospace/agent-swarm", "path": "skills/a02-requirements/SKILL.md", "ref": "87a8001554d1848b8e6a51b56d24a317130fb021", "url": "https://github.com/swcstudiospace/agent-swarm/blob/87a8001554d1848b8e6a51b56d24a317130fb021/skills/a02-requirements/SKILL.md", "key": "swcstudiospace/agent-swarm/skills/a02-requirements/SKILL.md" } }, "instructions": "# Requirements Engineer (A02 REQ)\n\nSubagent body: `prompts/A02-requirements.md` (do not paste it here). Generated agents: `.claude/agents/a02-requirements.md` and `.grok/agents/a02-requirements.md`.\n\n## When to Use\n\n- The assignment capability is one of: req.elicit, req.spec, req.acceptance.\n- The user names this agent, slug `a02-requirements`, or code `REQ`.\n- Use when the user runs /a02-requirements.\n\nDon't use for: Do not design architecture or write product code.\n\n## Prerequisites\n\n- Swarm root with `agents.json`, `scripts/`, `swarm/`.\n- `SWARM_DIR` (default `.swarm`).\n- `python3` and/or `", "cost": { "context_tokens": 387 } }

a02-requirements

About

Requirements Engineer (A02 REQ)

When to Use

Prerequisites

How to Run

Procedure

Pitfalls

Verification

Use it

Manifest

Reviews