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 jeremylongworth-source/AgentSkills --skill guided-requirements-interviewgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/guided-requirements-interview)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/guided-requirements-interview"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/guided-requirements-interview/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/jeremylongworth-source/agentskills/guided-requirements-interview"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/guided-requirements-interview.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.00101 | $0.00827 |
| Opus 5.5 | $0.00040 | $0.00331 |
| Sonnet 5.5 | $0.00020 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
guided-requirements-interview 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guided Requirements Interview
Core Workflow
- Identify the target artifact: BRD, PRD, feature spec, implementation brief, decision memo, project plan, research plan, or another structured output.
- Start with a compact working draft from what is already known.
- Ask one to three focused questions at a time, ordered by decision value: outcome, users/stakeholders, scope, current state, future state, constraints, success metrics, risks, approvals, and handoff needs.
- After each answer, update the working draft silently or with a short delta summary when alignment matters.
- Separate confirmed facts, assumptions, options, open questions, and decisions still needed.
- Stop questioning when the next question would not materially improve the artifact, then provide the completed draft plus remaining gaps.
Interview Style
- Be direct, specific, and low-friction. Prefer practical questions over generic discovery prompts.
- Keep the user aligned by showing short checkpoints: what is known, what was decided, what remains uncertain, and what the next question will unlock.
- Use progressive disclosure. Ask broad framing questions first, then drill into details only when the answer changes requirements, scope, acceptance criteria, risk, or approval needs.
- Avoid interrogating the user with a long questionnaire. If many gaps exist, group them into short rounds and explain the purpose of each round.
- Offer reasonable defaults when the user is unsure, but label them as defaults or assumptions.
- Preserve user language for goals, pain points, and stakeholder concerns when it may affect alignment.
Question Ladder
Use the smallest useful subset:
- Outcome: What business or user outcome should this create?
- Audience: Who is affected, who decides, and who approves?
- Problem: What is broken, costly, slow, risky, unclear, or missing today?
- Scope: What must be included, excluded, or deferred?
- Current state: How does the workflow, system, or decision happen now?
- Future state: What should be different when this is successful?
- Requirements: What must be true for the result to work?
- Constraints: What limits budget, timing, tools, data, policy, compliance, or staffing?
- Success: How will success be measured or accepted?
- Risks: What could fail, be misunderstood, or create rework?
- Handoff: Who needs the artifact next, and what decision should it support?
What ships with it
2 files 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.
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 · 83 lines · 101 tokens per session scan A 414ff6594a13
guided-requirements-interview is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 101 tokens to every session and 827 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-09-03.
Other skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
analiz-task-spec
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over.
answer-workspace-questions
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval.
call-prep
Create or review call prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for call prep planning or analysis.
wicked-garden-product
Product domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance"…
wicked-garden-swarm
Parallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove…