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.
npx skills add axiomantic/spellbook --skill gathering-requirementsgit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/gathering-requirements)<a href="https://agentmods.dev/skills/axiomantic/spellbook/gathering-requirements"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/gathering-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.
<a href="https://agentmods.dev/skills/axiomantic/spellbook/gathering-requirements"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/gathering-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01372 |
| Opus 5 | $0.00041 | $0.00686 |
| Sonnet 5 | $0.00016 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
gathering-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 6d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Gathering
Reasoning Schema
Before elicitation: feature being defined, user inputs available, context from project, known constraints.
After elicitation: all four archetypes consulted, requirements structured, assumptions explicit, validation criteria defined.
Invariant Principles
- Four Perspectives Are Mandatory: Every requirement set must address Queen, Emperor, Hermit, and Priestess.
- Ambiguity Is Debt: Vague requirements become bugs. Demand specificity.
- Explicit Over Implicit: Unstated assumptions are hidden requirements. Surface them.
- User Value Anchors Everything: Features without clear user value are scope creep.
- Constraints Shape Solutions: Understanding limits early prevents wasted design.
Inputs / Outputs
| Input | Required | Description |
|---|---|---|
feature_description |
Yes | Natural language description of what to build |
feedback_to_address |
No | Feedback from roundtable requiring revision |
| Output | Type | Description |
|---|---|---|
requirements_document |
File | At ~/.local/spellbook/docs/<project>/forged/<feature>/requirements.md |
open_questions |
Inline | Questions requiring user input |
The Four Perspectives
Queen: User Needs
Primary users, problem being solved, success criteria. User stories: "As a [type], I want [capability] so that [benefit]."
Emperor: Constraints
Technical constraints (stack, platform), resource constraints (time, team), integration requirements, performance targets (latency, throughput).
Hermit: Security Surface
Sensitive data handled, auth required, attack vectors, compliance requirements, impact if compromised.
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.
- 6d ago First seen · 148 lines · 82 tokens per session scan A 36d751e26578
gathering-requirements is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,372 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
intent-verify
Verify current requirements against implementation and actual results across a product or change scope, including completed features. Run permissible existing checks and report findings without fixes.
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
k-roadmap
A planning skill for discovering, breaking down, and delivering large requirements as a shared, gradual feature map.
k-onboard
A guide for creating a repository’s first verified project map and agent collaboration agreement. A project map explains the codebase, while the agreement records how agents should work in it.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.