agentmods.dev

capturing-business-requirements

capturing-business-requirements is a skill for Claude Code from richfrem/agent-plugins-skills. It costs 107 tokens per session (807 once invoked), scanned A, original, MIT.

A document-generation process for recording business knowledge. It produces requirements documents, user stories with acceptance checks, workflow diagrams, and notes from prototype observations.

In plain words
What is it for?
Use it to capture a business requirements document, user stories, process diagrams, or structured notes about an existing prototype.
Why use it?
It keeps requirements tied to their sources and clearly marks assumptions or decisions that still need confirmation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is python3 ../running-exploration-cycle/scripts/check_gaps.py --files exploration/captures/*.md --threshold 3.

Part of the agent-exploration-cycle plugin — 5 skills, 4 agents shipped together

not rated 7repo yesterday A scan 107 tokens original MIT

Good fit Use it to capture a business requirements document, user stories, process diagrams, or structured notes about an existing prototype.

Compare 6 skills from other repositories ↓
View source ↗ richfrem/agent-plugins-skills
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/richfrem/agent-plugins-skills
agentmods
npx agentmods add skills/richfrem/agent-plugins-skills/capturing-business-requirements

Made for: Claude Code.

Or install agent-exploration-cycle, the plugin that ships this one along with the rest of its 5 skills, 4 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 capturing-business-requirements

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/capturing-business-requirements"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/capturing-business-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 807 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.00107 $0.00807
Opus 5.5 $0.00043 $0.00323
Sonnet 5.5 $0.00021 $0.00161
Haiku 4.5 $0.00011 $0.00081

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

Security

Grade A, and why

capturing-business-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 2d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/business_requirements_capture_execute.py, scripts/generate_workflow.py, scripts/user_story_capture_execute.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/agent-exploration-cycle/.apm/skills/capturing-business-requirements/SKILL.md · 60 lines

How it starts

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

Capturing Business Requirements

Capture loop shown in capture-loop.mmd. It runs inside Phase 1, after a prototype walkthrough, and as the Phase 4 scribe.

Contents

Constraints

  • Never invent. Only record what the captures or the SME state; mark inferences [UNCONFIRMED] and explicit statements [CONFIRMED]. Do not promote without SME sign-off.
  • Gap marker: the exact string [NEEDS HUMAN INPUT] (reason in parentheses after it). check_gaps.py counts it; any variation is missed. It must not appear in the final handoff.
  • Track each open decision once under ## Consolidated Gaps; treat Decision Pre-fills in the brief as confirmed.
  • One capture mode per invocation; cite the source file for every story and rule.
  • prototype-notes.md has a single writer: the observation extraction in prototype-companion-agent.md.
  • Cheap multi-pass work goes through the cli-agent skill using the prompt templates here; never name models.

Quick start

From this skill's folder:

python3 scripts/business_requirements_capture_execute.py --input <capture.md> --mode brd --output exploration/captures/brd-draft.md
python3 scripts/user_story_capture_execute.py --input <brd-draft.md> --format gherkin --output exploration/captures/user-stories-draft.md
python3 scripts/generate_workflow.py --input <brd-draft.md> --output exploration/captures/workflow-map.md --type flowchart

Workflow

  1. Ingest the brief and approved plan; pick the mode (problem framing, BRD, stories, issues and opportunities, workflow, prototype observations).
  2. Draft with markers and a Consolidated Gaps section; run check_gaps (more than 3 gaps in a capture sends the session back to the brief).
  3. Reader test: predict the questions the consumer will ask and resolve them inline.
  4. Hand the captures back to running-exploration-cycle.

Read the full file on GitHub · 60 lines

Files

What ships with it

11 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.

  1. 2d ago First seen · 60 lines · 107 tokens per session scan A e687dc50cb9b

Subscribe to this mod's changes

capturing-business-requirements is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 807 once invoked, about $0.0004 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-10-24.

Project managementWriting and docsagent-evaluationagent-orchestrationagentic-control-planeagentic-osagentic-workflowsai-agent-governance
Related

Other skills, from other repositories

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

factory-handoff

Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.

watt-mind/factory · 47 tokens

ticket-spec

Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.

watt-mind/factory · 45 tokens

mindforge-session-report

Generate a session report with token usage estimates, work summary, and outcomes.

sairam0424/MindForge · 19 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

systematic-debugging

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

obra/superpowers · 21 tokens