agentmods.dev

create-requirements

create-requirements is a skill for Claude Code from tomzx/agents. It costs 22 tokens per session (1,326 once invoked), scanned A, original, MIT.

A requirements document created from a feature brief, user story, or issue, including what the feature must do and how it will be accepted.

In plain words
What is it for?
It defines functional and non-functional requirements, such as behavior, performance, security, availability, compatibility, and acceptance criteria.
Why use it?
It turns a short or informal request into clear, testable expectations and records important constraints.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; positional $N argument.

not rated 13repo +1 changed 18d ago A scan 22 tokens original MIT

Good fit It defines functional and non-functional requirements, such as behavior, performance, security, availability, compatibility, and acceptance criteria.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/create-requirements
View source ↗ tomzx/agents tomzx.github.io
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 tomzx/agents --skill create-requirements
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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.

agentmods badge for create-requirements

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/create-requirements/github.svg)](https://agentmods.dev/skills/tomzx/agents/create-requirements)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/create-requirements"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-requirements/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.

agentmods 80×15 button for create-requirements

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/create-requirements"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,326 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01326
Opus 5.5 $0.00009 $0.00530
Sonnet 5.5 $0.00004 $0.00265
Haiku 4.5 $0.00002 $0.00133

Measured 18d ago against content hash df725ba9540e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-requirements 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 18d 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.

skills/create-requirements/SKILL.md · 96 lines

How it starts

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

Create Requirements

Drafts a structured requirements document from a feature brief, user story, or GitHub issue, capturing functional requirements, non-functional requirements, constraints, and acceptance criteria. When the feature has a CLI surface, it delegates to /create-cli-design so the commands and options are designed alongside the requirements they serve.

Prerequisites

  • Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
  • If no argument is provided, use $ISSUE_TITLE and $ISSUE_BODY as the feature brief (and $ISSUE_NUMBER to link the feature).
  • A feature brief, user story, or issue description provided in context or as $1
  • Stakeholder goals and constraints, if known

Steps

  1. Read and understand the input (feature brief, issue, or user story).
  2. Identify the goal: what problem is being solved and for whom.
  3. List functional requirements: behaviors the system must show.
  4. List non-functional requirements: quality attributes (performance, security, availability, etc.).
  5. Identify constraints: technology choices, regulatory requirements, compatibility needs.
  6. Write acceptance criteria: testable conditions that confirm each requirement is met.
  7. Flag any open questions where requirements are unclear or missing.
  8. Derive the feature directory name N-<slug> following the Feature Directory Naming convention in skills/sdlc/references/shared.md: use the issue number as N when one is available, otherwise a p-prefixed sequence number (p1, p2, ...) marking the feature as pending a placeholder issue. Record the related issue number in the frontmatter issue field only when an issue exists.
  9. Write the output to .sdlc/features/N-<slug>/requirements.md, creating the directory if it does not exist.
  10. Detect a CLI surface: when the feature adds or changes CLI commands or options, load the create-cli-design skill with the skill tool and run it to design the interface from the requirements just drafted, producing .sdlc/features/N-<slug>/cli-design.md.

Read the full file on GitHub · 96 lines

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.

  1. 18d ago Changed · +2 lines df725ba9540e
  2. 22d ago Changed 41c55be9412f
  3. 24d ago Changed ffa2d34360c6
  4. 27d ago Changed 52924e2fc174
  5. 2mo ago First seen · 94 lines · 22 tokens per session scan A d734098a3394

Subscribe to this mod's changes

create-requirements is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,326 once invoked, about $0.0001 per session on Opus 5.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-31.

PlanningWriting and docs
Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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