Borrowing it
Nothing to install: this file belongs to getappz/agentflare. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getappz/agentflare/master/.claude/skills/requirements-specification/SKILL.mdgit clone --depth 1 https://github.com/getappz/agentflareWrote 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.
[](https://agentmods.dev/skills/getappz/agentflare/requirements-specification)<a href="https://agentmods.dev/skills/getappz/agentflare/requirements-specification"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/requirements-specification/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.
<a href="https://agentmods.dev/skills/getappz/agentflare/requirements-specification"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/requirements-specification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00096 | $0.01016 |
| Opus 5.5 | $0.00038 | $0.00406 |
| Sonnet 5.5 | $0.00019 | $0.00203 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
requirements-specification 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Specification
Write requirements precisely enough that two different people implementing from the same spec would build the same thing. A vague spec doesn't save time — it just moves the ambiguity (and the rework) later.
When to use
- The ask is underspecified: "add notifications," "make search better," "support teams" — before any architecture or code, pin down what these actually mean.
- Multiple stakeholders (or a stakeholder and an implementer) could reasonably disagree about scope.
- Skip when the change is small and unambiguous (a one-line bug fix, a well-scoped refactor) — writing a formal spec for those is pure overhead.
Process
1. Requirements gathering
Split every requirement into functional (what the system does) and non-functional (how well it does it — latency, availability, security). Each one needs an id, a priority, and criteria specific enough to fail a "is this actually done?" test:
FR-001: System shall authenticate users via OAuth2
priority: high
acceptance:
- Users can log in with Google/GitHub
- Session persists for 24 hours
- Refresh tokens auto-renew
NFR-001 (performance): API p95 latency <200ms
NFR-002 (security): All data encrypted in transit and at rest
"Fast" and "user-friendly" are not requirements — they're not testable. Replace them with a number and a measurement method.
2. Constraint analysis
Separate constraints by kind, since each kind trades off differently:
- Technical — must use existing DB, must run on current infra, language/ framework version floors.
- Business — deadline, budget, team size.
- Regulatory — compliance regimes (GDPR, SOC2), accessibility (WCAG).
3. Use cases
For anything with a nontrivial flow, write the actor, preconditions, the numbered step-by-step flow, postconditions, and — critically — the exceptions (what happens when a step fails). Most spec gaps live in the exceptions nobody wrote down.
4. Acceptance criteria (Gherkin)
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 · 112 lines · 96 tokens per session scan A f21122cf2ab0
requirements-specification is a skill published in the GitHub repository getappz/agentflare (2 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 1,016 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-08-31.
Other skills, from other repositories
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
audit
Fast quality gate — detects stack, runs static analysis, checks cross-layer consistency, fixes issues. Run between every pipeline phase, before every commit push, after every feature batch. Lighter than /analyze but catches the same critical issues.
logic-lens
AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…