requirements

requirements is a command for Claude Code from tzachbon/smart-ralph. It costs 0 tokens per session (3,380 once invoked), scanned B, original, MIT.

A command that turns a project goal and approved research into software requirements. Requirements describe what the system must do and the conditions it must meet.

In plain words
What is it for?
Use it to gather context, identify important decisions, delegate requirements writing, validate the result, and finalize the requirements document.
Why use it?
It provides a reviewed, structured agreement about the work before design or implementation begins. It also checks that research has been approved.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ralph-specum plugin — 3 skills, 11 commands, 7 agents shipped together

Good fit Use it to gather context, identify important decisions, delegate requirements writing, validate the result, and finalize the requirements document.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add tzachbon/smart-ralph
Claude Code
/plugin install ralph-specum

Made for: Claude Code.

Or install ralph-specum, the plugin that ships this one along with the rest of its 3 skills, 11 commands, 7 agents.

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 requirements

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/tzachbon/smart-ralph/requirements"><img src="https://agentmods.dev/badge/commands/tzachbon/smart-ralph/requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,380 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00000 $0.03380
Opus 5.5 $0.00000 $0.01352
Sonnet 5.5 $0.00000 $0.00676
Haiku 4.5 $0.00000 $0.00338

Measured 1mo ago against content hash 0250e171084b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

requirements scanned grade B with 1 finding 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 1mo 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

allowed-tools: "*"
plugins/ralph-specum/commands/requirements.md · 254 lines

How it starts

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

Requirements Phase

Generate requirements for the active spec. Require the research artifact to have explicit approval first. You are a coordinator, not a product manager -- delegate ALL work to the product-manager subagent.

Read ${CLAUDE_PLUGIN_ROOT}/references/normal-mode-gates.md before gathering context.

Checklist

Create a task for each item and complete in order:

  1. Gather context -- resolve spec, read research and goal
  2. Interview gate -- critical frontier and approval, or authorized quick bypass
  3. Execute requirements -- dispatch product-manager via team
  4. Artifact review -- spec-reviewer validation loop (both modes)
  5. Walkthrough & approval -- display summary, get user approval
  6. Finalize -- update state, commit, stop

Step 1: Gather Context

  1. If $ARGUMENTS contains a spec name, use ralph_find_spec() to resolve it; otherwise use ralph_resolve_current(). Store the resolved spec directory as SPEC_PATH.
  2. If no active spec, error: "No active spec. Run /ralph-specum:new first."
  3. Check the resolved spec directory exists
  4. Read .ralph-state.json, reject simultaneous exact --quick and --interactive, and normalize persistent mode with phase_gate.py mode.
  5. If research.md exists and normalized quickMode is false, require its explicit artifact approval before clearing the approval flag. Exact quick mode continues with the validated file. When research.md is absent, record that there is no upstream research artifact and require no prior-artifact approval.
  6. Clear the approval flag through the locked helper while preserving every other field:
    python3 "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/locked-state.py" merge \
      --state "$SPEC_PATH/.ralph-state.json" \
      --set "awaitingApproval=false"
    
  7. Read context: research.md (if exists), .progress.md, original goal.
  8. Run skill discovery pass 1 if missing. Run pass 2 now when research.md exists and pass 2 is missing.

Read the full file on GitHub · 254 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. 1mo ago First seen · 254 lines · 0 tokens per session scan B 0250e171084b

Subscribe to this mod's changes

requirements is a command published in the GitHub repository tzachbon/smart-ralph (559 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,380 tokens. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.