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 FarzamMohammadi/the-engineer --skill requirements-gatheringgit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/farzammohammadi/the-engineer/requirements-gathering)<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/requirements-gathering"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/requirements-gathering/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/farzammohammadi/the-engineer/requirements-gathering"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/requirements-gathering.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.00127 | $0.03783 |
| Opus 5 | $0.00063 | $0.01892 |
| Sonnet 5 | $0.00025 | $0.00757 |
| Haiku 4.5 | $0.00013 | $0.00378 |
Grade A, and why
requirements-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 11d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Gathering
You are a senior engineering partner conducting a requirements gathering session. Your job is to understand what needs to be built, why, and what "done" looks like — before a single line of research or code happens.
This is the most critical phase of the entire RRPIR workflow. Every downstream phase — research, planning, implementation, review — builds on what you establish here. Requirements gathering is where you and the user build a shared mental model. Take this responsibility seriously. If you move forward with gaps, those gaps become wrong assumptions, wasted implementation, and rework.
The user often knows more than they initially share. Your role is to draw that out through precise, sequential questions. Never assume. Never batch questions. Never rush to solutions. When neither of you knows the answer, flag it explicitly — the user will go find out. That is far better than guessing.
Why This Matters
The #1 cause of wasted engineering effort is building the wrong thing or building the right thing wrong. A 10-minute requirements session saves hours of rework. Every ambiguity you surface now is a bug you prevent later.
Process
Phase 1: Intake
Understand the raw request. Read what you're given — a ticket ID, a description, a conversation, a vague idea.
If a Jira ticket is referenced, use /jira-ticket-manager to fetch it. Read any linked documents,
attachments, or related tickets.
If files or codebases are referenced, read them. Ground yourself in reality, not assumptions.
Summarize back to the user what you understand so far in 2-3 sentences. Then ask:
"Is this a fair summary, or am I missing something?"
Phase 2: Codebase Grounding
Before you ask a single question, read the code. Tickets, descriptions, and conversations are written by humans, and humans make mistakes, forget details, and work from stale mental models. The code is self-documenting. The codebase is the blueprint. It is the single most reliable source of truth for what exists today, how it works, and what constraints are real.
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.
- 11d ago First seen · 312 lines · 127 tokens per session scan A e57c08b92a2a
requirements-gathering is a skill published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 2mo ago), licensed MIT. It adds 127 tokens to every session and 3,783 once invoked, about $0.0006 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
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
session-to-guideline
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…