A requirements-document generator that turns raw client messages or product requirements into an IEEE 830 software requirements specification. An SRS is a structured document describing what a system must do and the constraints it must meet.

It helps gather project context, extract requirements, check for gaps, ask clarification questions, and produce sections covering scope, features, constraints, and quality requirements.

It helps turn incomplete, scattered requirements into a consistent document while finding missing information before development begins.

cl:srs — Skill for Claude Code by skillmds/skillmd

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add skillmds/skillmd --skill cl-srs

Clone the repo

git clone --depth 1 https://github.com/skillmds/skillmd

Made for: Claude Code.

Or install create-prd-from-idea, the plugin that ships this one along with the rest of its 11 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/skillmds/skillmd/cl-srs/github.svg)](https://agentmods.dev/skills/skillmds/skillmd/cl-srs)

Your own site

<a href="https://agentmods.dev/skills/skillmds/skillmd/cl-srs"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/cl-srs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/skillmds/skillmd/cl-srs"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/cl-srs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,671 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.01671
Opus 5.5	$0.00022	$0.00668
Sonnet 5	$0.00011	$0.00334
Haiku 4.5	$0.00005	$0.00167

Measured 4d ago against content hash 5ec65e6a77a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-23, from the pricing page.

Security

Grade A, and why

cl:srs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to cl:srs — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/create-prd-from-idea/skills/cl-srs/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cl:srs — IEEE 830 SRS from Raw Requirements

Pipeline: Brainstorm → Receive → Extract → Gap Scan → Clarify (P1 → P2 → P3) → Generate → Review Gate → Save

Reference files (load before starting):

.claude/skills/srs-generator/references/srs-template.md
.claude/skills/srs-generator/references/gap-detection-guide.md

Context files (load if present — created by .claude/scripts/init_project.py):

projects/{name}/_context/vision.md → pre-fills §1.2 Scope and §2.1
projects/{name}/_context/features.md → pre-fills §2.2 and IN/OUT table
projects/{name}/_context/tech_stack.md → pre-fills §3.5 Design Constraints
projects/{name}/_context/glossary.md → pre-fills Appendix A
projects/{name}/_context/quality_standards.md → pre-fills §3.3–§3.6 NFR

If context files exist: skip Brainstorm Gate questions already answered there.

Brainstorm Gate — Understand Context First

Do NOT ask for raw requirements yet. First understand project context.

Ask these 3 questions in one AskUserQuestion batch:

System type: Web app / Mobile app / API / Internal tool / SaaS / Desktop / Other?
Primary users: Who will use this system? (end customers, internal staff, admins, B2B clients…)
Core problem: What problem does this system solve? (1–2 sentences)

Wait for answers. Use responses to seed §2.1 Product Perspective, §2.3 User Characteristics, and §1.2 Scope.

After receiving answers, prompt:

Context noted. Now paste your raw requirements — any format works:
client email, bullet list, chat transcript, PRD draft.

Wait for raw input, then proceed to Step 0.

Step 0 — Receive Input

Read full input silently. Emit:

Input received: ~{N} words | type: [email prose | bullet list | partial PRD | mixed]

Step 1 — Extract & Classify

Output structured block:

Actors — named and implied stakeholders. Tag undefined: [GLOSSARY-GAP: {actor}]
Features — FR-01, FR-02… in "Subject can do X" form. Note strategy: prose / bullets / PRD
Constraints — verbatim fragments only (tech stack, deadline, compliance, budget)
Out-of-Scope signals — explicit exclusions. If absent: [CONTEXT-GAP: no out-of-scope boundary stated]

Read the full file on GitHub · 180 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 180 lines · 54 tokens per session scan A 5ec65e6a77a6

Subscribe to this mod's changes

cl:srs is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,671 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cl:srs, differing in 1 line, and is treated as a copy.

Lint Project management Writing and docs agent-skills ai-agents claude cli mcp

quality

Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

google-gemini/gemini-cli · 24 tokens

follow-up-after-call

Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…

XiaomiMiMo/MiMo-Code · 69 tokens

cl:srs