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 agentmods add skills/tesslio/spec-driven-development-tile/requirement-gatheringnpx skills add tesslio/spec-driven-development-tile --skill requirement-gatheringgit clone --depth 1 https://github.com/tesslio/spec-driven-development-tileWrote 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/tesslio/spec-driven-development-tile/requirement-gathering)<a href="https://agentmods.dev/skills/tesslio/spec-driven-development-tile/requirement-gathering"><img src="https://agentmods.dev/badge/skills/tesslio/spec-driven-development-tile/requirement-gathering.svg" alt="Measured on agentmods" 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.00083 | $0.00618 |
| Opus 5 | $0.00042 | $0.00309 |
| Sonnet 5 | $0.00017 | $0.00124 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
requirement-gathering 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Gathering
Structured interview process that turns vague requests into clear, actionable requirements.
When to use
- A new task arrives from a stakeholder (feature, bugfix, refactor)
- The request has ambiguous or missing acceptance criteria
- Existing specs don't cover the requested change
- Before running
spec-writerto create or update specs
Rules
- Ask ONE question at a time (see
one-question-at-a-timerule) - Never begin implementation until requirements are confirmed
- Base questions on gaps found in existing specs, not assumptions
Inputs
- The stakeholder's initial request
- Existing specs in the project's
specs/folder (if any)
Steps
-
Review existing specs. Scan the
specs/directory for any specs related to the request. Note what's already documented and what's missing. -
Identify gaps. List the ambiguous or underspecified areas:
- Unclear scope boundaries (what's in vs. out)
- Missing edge cases or error handling expectations
- Unspecified behavior for boundary conditions
- Unclear integration points with existing functionality
- Missing non-functional requirements (performance, security)
-
Interview the stakeholder. Ask ONE question at a time. Wait for the answer before asking the next question. Prioritize questions by impact — ask about scope and core behavior first, edge cases second.
Good questions are specific and bounded:
- "Should the API return a 404 or an empty list when no results match?"
- "Is this endpoint authenticated, and if so, which roles have access?"
Bad questions are open-ended or bundled:
- "What should the API do?" (too vague)
- "What about errors, pagination, auth, and rate limits?" (too many at once)
-
Summarize requirements. After all questions are answered, present a concise summary of the clarified requirements back to the stakeholder for confirmation.
-
Get explicit approval. Do not proceed until the stakeholder confirms the summary is accurate. If they correct anything, update the summary and re-confirm.
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 · 71 lines · 83 tokens per session scan A 8d6aaf57eb12
requirement-gathering is a skill published in the GitHub repository tesslio/spec-driven-development-tile (53 stars, last pushed 5mo ago), licensed MIT. It adds 83 tokens to every session and 618 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…