Srs — Testing skill for Claude Code
Use when writing the requirements a team will be held to — an SRS, requirements spec, or a requirements document for an implementation team or vendor (IEEE 830, with traceability and acceptance criter.
How to install Srs
Installs to ~/.claude/skills/tercel-spec-forge-srs/SKILL.md
mkdir -p ~/.claude/skills/tercel-spec-forge-srs && curl -fsSL https://raw.githubusercontent.com/tercel/spec-forge/HEAD/commands/srs.md -o ~/.claude/skills/tercel-spec-forge-srs/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Srs does
allowed-tools: Read, Glob, Grep, Write, AskUserQuestion, Task description: "Use when writing the requirements a team will be held to — an SRS, requirements spec, or a requirements document for an implementation team or vendor (IEEE 830, with traceability and acceptance criteria)" argument-hint:
You are a senior requirements engineer with deep expertise in writing formal Software Requirements Specifications, following IEEE 830 (SRS), ISO/IEC/IEEE 29148, and Amazon technica
Alternatives in Testing
- Claude Code Spec Workflow — Automated Kiro-style Spec workflow for Claude Code 3.6k ★
- Cc Sdd — Spec-driven development (SDD) for your team's workflow 3.1k ★
- Spawn Fs Team — Boot a 5-agent full-stack Flotion team as a new workspace in the cmux window (reuse the open window; only crea 107 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Feature Spec
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, an
Component Spec
Define component API, states, variants, and ARIA requirements before writing any implementation code
Spec
Define what to build — explores codebase and recalls LTM before writing acceptance criteria.
Verify Spec
Verify that a generated spec document preserves all upstream requirements and has no structural quality issues
Sap Doc
Trigger structured SAP document generation — invoked when a functional spec, technical spec, user guide, or tr
Spec Writer
Specification writer that turns vague intent into precise, buildable specs with acceptance criteria and GitHub
Related Agents
Daw Module Verifier
Spawn it in VERIFY, on an implementation it did not write, to cross-check a module against the PRD, the spec a
QA Requirements Risk Analyst
Analyzes requirements, ambiguity, risk, lifecycle impact, acceptance criteria, and traceability gaps without e
Team Spec Reviewer
Spec compliance reviewer. Verifies implementation matches requirements — nothing more, nothing less. Runs BEFO