agentmods.dev

requirement-elicitation

requirement-elicitation is a skill for Claude Code from britt/agent-skills. It costs 63 tokens per session (1,355 once invoked), scanned A, original, MIT.

A guided questionnaire for defining what a software project must do and the limits it must follow.

In plain words
What is it for?
Use it to plan web apps, APIs, command-line tools, mobile apps, or data pipelines and save the answers as a requirements document.
Why use it?
It helps uncover missing requirements, technical constraints, and unusual cases before development begins.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agent-skills plugin — 28 skills shipped together

not rated 5repo 7d ago A scan 63 tokens original MIT

Good fit Use it to plan web apps, APIs, command-line tools, mobile apps, or data pipelines and save the answers as a requirements document.

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

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 28 skills.

Its marketplace also offers this one on its own, as the plugin requirement-elicitation — /plugin install requirement-elicitation after adding the marketplace above.

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 requirement-elicitation

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/britt/agent-skills/requirement-elicitation"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/requirement-elicitation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,355 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.00063 $0.01355
Opus 5 $0.00032 $0.00678
Sonnet 5 $0.00013 $0.00271
Haiku 4.5 $0.00006 $0.00136

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

Security

Grade A, and why

requirement-elicitation 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.

skills/requirement-elicitation/SKILL.md · 162 lines

How it starts

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

Requirement Elicitation Wizard

You are guiding the user through a comprehensive requirement elicitation process. Your goal is to capture all functional, nonfunctional, and edge-case requirements before they start building.

How This Works

  1. Start: User says something like "Let's define requirements" or "Help me figure out what to build"
  2. Domain Selection: Ask what type of project they're building
  3. Guided Questions: Walk through each section, asking questions one at a time
  4. Adaptive Flow: Branch based on answers (e.g., if they mention integrations, ask which ones)
  5. Refinement: Allow revisiting any section
  6. Output: Generate a comprehensive requirements document saved as requirements-<project>.md in the working directory

Conversation Flow

Starting the Session

When the user wants to define requirements:

  1. Ask the user what type of project they're building
  2. Explain what you'll cover: Overview, Functional, Nonfunctional, Constraints, Edge Cases
  3. Ask the first question

Sections to Cover

Walk through these five sections in order:

  1. Project Overview - Name, purpose, target users, success criteria
  2. Functional Requirements - Features, endpoints, integrations, user workflows
  3. Nonfunctional Requirements - Performance, security, reliability, scalability
  4. Constraints - Timeline, budget, technical requirements, team size
  5. Edge Cases & Risks - Error handling, failure modes, boundary conditions

Asking Questions

For each question:

  1. Ask clearly and conversationally (not robotically)
  2. Include context explaining why you're asking
  3. Indicate if it's required or optional
  4. After the user answers, mentally note the response and continue

Section Transitions

When a section is complete:

  1. Summarize what was captured: "Great, for the overview I captured: [summary]"
  2. Ask if they want to add anything else to this section
  3. Append the completed section to requirements-<project>.md in the working directory
  4. Introduce the next section briefly

Read the full file on GitHub · 162 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. 9d ago First seen · 162 lines · 63 tokens per session scan A 96ed999fb151

Subscribe to this mod's changes

requirement-elicitation is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 1,355 once invoked, about $0.0003 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-31.

PlanningProject management
Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens