A procedure for adding a new numbered requirement to an Assured project's requirements specification. It assigns the requirement to a module and formats the entry consistently.

Finding the right specification, choosing the next requirement ID, adding the requirement text, reviewing the change, and identifying the next design and test links to create.

It removes manual numbering and formatting work while keeping new requirements connected to the correct feature or module.

req-add — Skill for Claude Code by SteveGJones

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 SteveGJones/ai-first-sdlc-practices --skill req-add

Clone the repo

git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practices

Made for: Claude Code.

Or install sdlc-assured, the plugin that ships this one along with the rest of its 8 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/stevegjones/ai-first-sdlc-practices/req-add/github.svg)](https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/req-add)

Your own site

<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/req-add"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/req-add/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/stevegjones/ai-first-sdlc-practices/req-add"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/req-add.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 374 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found 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.00028	$0.00374
Opus 5	$0.00014	$0.00187
Sonnet 5	$0.00006	$0.00075
Haiku 4.5	$0.00003	$0.00037

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

Security

Grade A, and why

req-add 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 9d 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.

plugins/sdlc-assured/skills/req-add/SKILL.md · 45 lines

What it actually says

Skill: req-add

Use this skill when adding a new requirement to an existing requirements-spec under the Assured bundle. Computes the next sequential ID for the feature and module, prompts for the requirement text, and appends a properly-formatted ### REQ-... section.

Inputs

<feature-id> (or <module-id> for positional projects): which spec to append to
The requirement text (single declarative sentence)

Steps

Locate the requirements-spec. Read docs/specs/<feature-id>/requirements-spec.md. If the project uses positional decomposition, read the spec for the matching module.
Compute the next REQ number. Scan existing ### REQ-... headings. New ID is the max + 1, zero-padded to 3 digits.
Prompt for the requirement text. Ask: "Single declarative sentence describing the new requirement?"

Append the section.

### REQ-<feature-id>-<NNN>

<text>

**Module:** <module-id>

Confirm. Show the diff to the user before saving.
Save. Write the file.
Remind. "Next steps: add a corresponding DES in design-spec.md (use req-link), then a TEST in test-spec.md."

Done criteria

New REQ section appended with correct ID, no renumbering of existing IDs.
Module assignment present.
File saved; no other changes.

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.

9d ago First seen · 45 lines · 28 tokens per session scan A f38c8b2a171b

Subscribe to this mod's changes

req-add is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 374 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens