What is 031-architecture-adr-functional-requirements?

A guided conversation for documenting decisions and requirements for command-line tools, web APIs, or both. It produces an Architectural Decision Record, a document explaining important technical choices.

Use it to define how a CLI or REST/HTTP API should work, including its workflows, inputs, errors, data, testing, and operations.

It helps turn an unclear idea into agreed requirements and recorded architecture decisions before implementation.

031-architecture-adr-functional-requirements

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 jabrena/cursor-rules-examples --skill 031-architecture-adr-functional-requirements

Clone the repo

git clone --depth 1 https://github.com/jabrena/cursor-rules-examples

Made for: Claude Code, Codex.

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/jabrena/cursor-rules-examples/031-architecture-adr-functional-requirements/github.svg)](https://agentmods.dev/skills/jabrena/cursor-rules-examples/031-architecture-adr-functional-requirements)

Your own site

<a href="https://agentmods.dev/skills/jabrena/cursor-rules-examples/031-architecture-adr-functional-requirements"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/031-architecture-adr-functional-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jabrena/cursor-rules-examples/031-architecture-adr-functional-requirements"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/031-architecture-adr-functional-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 535 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.

Model	Per session	Once invoked
Fable 5.1	$0.00079	$0.00535
Opus 5.5	$0.00032	$0.00214
Sonnet 5.5	$0.00016	$0.00107
Haiku 4.5	$0.00008	$0.00053

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

Security

Grade A, and why

031-architecture-adr-functional-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 2mo 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.

.agents/skills/031-architecture-adr-functional-requirements/SKILL.md · 42 lines

What it actually says

Create ADRs for Functional Requirements (CLI and/or REST API)

Guide stakeholders through a structured conversation to uncover and document technical decisions and functional requirements for command-line tools, REST/HTTP APIs, or combined surfaces. This is an interactive SKILL. The ADR is the documentation of that conversation, not the conversation itself. Infer CLI vs API from project context when possible; ask a short clarifying question when unclear.

What is covered in this Skill?

Surface discovery: CLI, REST/HTTP API, or both (inference + confirmation)
Initial context: purpose, users/consumers, constraints, timeline, load (API when relevant)
Functional requirements: surface-specific workflows, I/O, resources, errors
Technical decisions: language/framework; REST blocks (API design, auth, data, infra, testing/monitoring) and/or CLI blocks (architecture, data/integration, testing/distribution)
Decision synthesis and validation before ADR creation
ADR document generation and next steps

Constraints

Use conversational discovery—ask 1-2 questions at a time, build on answers, validate before proceeding. Only create ADR after thorough conversation and user confirmation.

MANDATORY: Run date before starting to get accurate timestamps for the ADR
MUST: Read the reference template fresh—do not use cached questions
MUST: Ask one or two questions at a time; never all at once
MUST: Validate summary with user ("Does this accurately capture your requirements?") before proposing ADR creation
MUST: Wait for user to confirm "proceed" before generating the ADR

When to use this skill

Document CLI or REST architecture
Create ADR for functional requirements
ADR for command-line tool or HTTP API
Functional requirements ADR

Reference

For detailed guidance, examples, and constraints, see references/031-architecture-adr-functional-requirements.md.

Files

What ships with it

1 file 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.

references/031-architecture-adr-functional-requirements.md 12 KB

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.

2mo ago First seen · 42 lines · 79 tokens per session scan A 3ebcdb47f48e

Subscribe to this mod's changes

031-architecture-adr-functional-requirements is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 535 once invoked, about $0.0003 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.

Planning Writing and docs cursor cursor-rules examples

parallel-feature-development

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…

wshobson/agents · 105 tokens

nft-standards

Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.

wshobson/agents · 48 tokens

cost-optimization

Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.