requirement-intake

requirement-intake is a skill for Claude Code, Codex from Leo-maomao/pm-copilot. It costs 28 tokens per session (637 once invoked), scanned A, original, MIT.

A requirement-gathering workflow for turning an unclear product request into a usable brief before writing a product requirements document, or PRD. It identifies users, goals, scenarios, limits, assumptions, and missing information.

In plain words
What is it for?
Use it to review existing product context, separate confirmed facts from assumptions, and ask only questions that could change scope, success measures, design, or launch risk.
Why use it?
It prevents important business or engineering decisions from being guessed when the original request is vague.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review existing product context, separate confirmed facts from assumptions, and ask only questions that could change scope, success measures, design, or launch risk.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leo-maomao/pm-copilot/requirement-intake
Install

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.

Any agent
npx skills add Leo-maomao/pm-copilot --skill requirement-intake
Clone the repo
git clone --depth 1 https://github.com/Leo-maomao/pm-copilot

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for requirement-intake

README.md
[![agentmods](https://agentmods.dev/badge/skills/leo-maomao/pm-copilot/requirement-intake/github.svg)](https://agentmods.dev/skills/leo-maomao/pm-copilot/requirement-intake)
Your own site
<a href="https://agentmods.dev/skills/leo-maomao/pm-copilot/requirement-intake"><img src="https://agentmods.dev/badge/skills/leo-maomao/pm-copilot/requirement-intake/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.

agentmods 80×15 button for requirement-intake

Your own site · 80×15
<a href="https://agentmods.dev/skills/leo-maomao/pm-copilot/requirement-intake"><img src="https://agentmods.dev/badge/skills/leo-maomao/pm-copilot/requirement-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 637 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00637
Opus 5 $0.00014 $0.00318
Sonnet 5 $0.00006 $0.00127
Haiku 4.5 $0.00003 $0.00064

Measured 10d ago against content hash ded5f83c0aa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

requirement-intake 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 10d 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.

skills/requirement-intake/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Requirement Intake

Goal

Convert a vague product request into a usable brief without inventing business-critical facts.

Workflow

  1. Restate the request in one sentence.
  2. Load relevant current-state product context from the best available source: host repository, historical PRDs, specs, product docs, screenshots, analytics exports, support tickets, meeting notes, or direct user answers.
  3. Identify the target user, problem, desired outcome, platform, affected product area, and business goal.
  4. Summarize source quality: confirmed context, inferred context, stale or missing context.
  5. Ask only high-impact clarification questions that materially change scope, metrics, solution direction, compliance, or release risk.
  6. Split unknowns into must answer before generation, can draft with stated assumption, and must confirm before development or launch.
  7. Stop before PRD generation if any must answer before generation question is unanswered.
  8. Stop before a Ready for engineering PRD/UI delivery if any engineering-blocking must confirm before development or launch item is unanswered.
  9. If the user explicitly asks for iterative evaluation or says to choose recommended options automatically, select conservative defaults instead of stopping, record each default and rationale, and keep unresolved risk visible in readiness.
  10. Write explicit assumptions only after the user says to proceed with a draft or the unknown is low-impact.
  11. Do not put the same unknown in more than one bucket.
  12. If enough evidence exists to draft safely, proceed with assumptions instead of asking low-value questions.
  13. For a consequential unresolved decision, run a focused decision interview: ask one branch-changing question at a time, summarize the answer and trade-off, then ask the next question only when it changes the recommendation.
  14. Record a durable decision only after the user confirms it. Store the decision, alternatives, rationale, owner, and reopen condition in the run artifact; do not create or update a project-wide glossary, ADR, ticket, or host document automatically.

Read the full file on GitHub · 54 lines

Changes

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.

  1. 10d ago First seen · 54 lines · 28 tokens per session scan A ded5f83c0aa3

Subscribe to this mod's changes

requirement-intake is a skill published in the GitHub repository Leo-maomao/pm-copilot (4 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 637 once invoked, about $0.0001 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-31.