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 andreaswasita/copilot-agents-dojo --skill requirements-elicitationgit clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/requirements-elicitation)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/requirements-elicitation"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/requirements-elicitation/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/andreaswasita/copilot-agents-dojo/requirements-elicitation"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/requirements-elicitation.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.00013 | $0.01847 |
| Opus 5.5 | $0.00005 | $0.00739 |
| Sonnet 5.5 | $0.00003 | $0.00369 |
| Haiku 4.5 | $0.00001 | $0.00185 |
Grade A, and why
requirements-elicitation 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 1mo 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Elicitation
Turns vague intent into precise, testable, engineer-ready requirements. This is a technique skill — not a role. Both the TPM and Architect invoke it at different stages of the requirements pipeline.
Requirements are delivery contracts, not meeting minutes. Every requirement must be testable, traceable, and unambiguous before it reaches engineering.
When to Use
- Starting a new feature, epic, or initiative
- Requirements feel vague, conflicting, or scope-creeping
- Someone asks "what does done look like?"
- Stakeholders keep changing their minds mid-sprint
- Writing PRDs, feature briefs, or story backlogs
- Assessing system impact of incoming requirements (Architect stage)
- Translating user stories into system specifications (Architect stage)
Prerequisites
- The
ask_userCopilot tool to gather clarifications without spamming prose. - The
editCopilot tool to write the resulting brief / story cards. - A target file for the artefacts (typically
requirements/<engagement>/stories.mdordocs/feature-brief.md). - Access to the primary stakeholder — no requirements loop with a phantom user.
- For the Architect stage: read access to the TPM-produced brief.
How to Run
1. DISCOVER — Ask 3–5 problem-framing questions; never accept solutions-disguised-as-requirements.
2. INTERROGATE — Drive Socratic questions across scope, edges, success, failure, dependencies, constraints.
3. STRUCTURE — Write user stories + Given/When/Then acceptance criteria + assumptions + out-of-scope.
4. VALIDATE — Read each AC back in plain language and capture written sign-off.
5. GATE — Walk the Definition of Ready checklist. If anything fails, return to step 2.
6. HAND OFF — TPM passes to Architect; Architect may return stories that are not technically achievable.
Quick Reference
| Artefact | Mandatory format |
|---|---|
| User story | As a [specific role], I want to [action], so that [measurable outcome]. |
| Acceptance criterion | Given [precondition], When [action], Then [expected result]. (≥ 3 per story) |
| Non-functional requirement | Numeric threshold + measurement method (no adjectives) |
| Assumption | Statement + owner + expiry date |
| Out of scope | Explicit boundary list (never implied) |
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.
- 1mo ago First seen · 202 lines · 13 tokens per session scan A 8cc8e6ee6da4
requirements-elicitation is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (54 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,847 once invoked, about $0.0001 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-30.
Other skills, from other repositories
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.
truth-first
A set of rules for writing technical conclusions and performing irreversible or state-changing operations. It requires evidence tied to file and line locations and restricts unsupported claims.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.