A workflow for challenging a product brief and writing a product requirements document that engineers can implement. It examines the job, users, assumptions, boundaries, and non-goals instead of merely expanding an outline.

Use it to turn notes or an outline into a candidate PRD, challenge its product assumptions, and prepare it for detailed specification work.

It reduces guesswork by testing whether the proposed product solves a real problem and by exposing weak assumptions early. It keeps architecture and code decisions out of the requirements discussion.

prd-think — Skill for Claude Code by drivestream-lab

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 drivestream-lab/prayog-skills --skill prd-think

Clone the repo

git clone --depth 1 https://github.com/drivestream-lab/prayog-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-think/github.svg)](https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-think)

Your own site

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-think"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-think/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-think"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-think.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,208 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.

Model	Per session	Once invoked
Fable 5.1	$0.00139	$0.02208
Opus 5	$0.00069	$0.01104
Sonnet 5	$0.00028	$0.00442
Haiku 4.5	$0.00014	$0.00221

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

Security

Grade A, and why

prd-think 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 4d 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/requirements/prd-think/SKILL.md · 205 lines

How it starts

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

PRD think

Write a PRD that /spec-draft can implement without guessing.

The brief (outline, notes, or spoken ask) is a hypothesis. Expanding its headings is a failed run. Architecture, routes, payloads, frameworks, and module names are a failed run — park those for engineering.

This skill authors. It does not score. After one or more candidates exist, run /prd-quality and pass the files.

Pin contracts (read, do not fork):

Ids: prayog-skills/references/id-conventions.md
Paths / overwrite: prayog-skills/references/artifact-write-contract.md

If the pin mount is missing, say so and still follow those rules from a harness skill copy if present. Do not invent a second id vocabulary.

This skill does not unlock Gate 1. Typical next: /prd-quality on two candidates, then user authorizes promote of one file to prd/{INIT}.md, then /validate-requirements.

Inputs (resolve, do not assume an INIT)

Brief — (REQUIRED) outline file, pasted ask, or conversation. Prefer prd/INIT-*-outline.md or prd/*-outline.md if the user points at one.
Initiative id — INIT-*. Ask if missing. Do not invent a programme prefix.
Existing PRD — (OPTIONAL) prd/{INIT}.md. Context only. Never input for T1. Never edit unless promote is authorized.
Product context — (OPTIONAL) whatever exists: planning/, config/service-catalog*.yaml, sibling prd/INIT-*.md, ADRs. Absence is not a blocker — record as skipped.
Layout — reports_dir from .harness/profile.yaml (meta default prd/reports/ per artifact-write-contract). prd_root default prd/.

Outputs

Live PRD filename is prd/{INIT}.md. Mark conductor output with suffix -prd-think so it cannot be mistaken for KEEP product.

Series (do not overwrite a previous think candidate):

First free path	Role
`{reports_dir}/{INIT}-prd-think.md`	Run 1
`{reports_dir}/{INIT}-prd-think-2.md`	Run 2
`{reports_dir}/{INIT}-prd-think-N.md`	Run N

Read the full file on GitHub · 205 lines

Files

What ships with it

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

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.

4d ago Changed · +4 lines 15ed8e66d129
8d ago First seen · 201 lines · 139 tokens per session scan A 0c9ca84e5be1

Subscribe to this mod's changes

prd-think is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 139 tokens to every session and 2,208 once invoked, about $0.0007 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-09-04.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens