A guided process for turning a rough product idea into requirements, user flows, and a product requirements document, or PRD. A PRD is a written plan describing what a product or feature should do.

Use it to ask clarifying questions, create a specification document, map user flows, and produce a handoff-ready PRD in stages.

It helps uncover missing context and prevents a vague idea from being handed to a development team as if it were a complete specification.

idea-to-prd — Skill for Claude Code by bjorn-ingmanson

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 bjorn-ingmanson/thefroject-plugins --skill idea-to-prd

Clone the repo

git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 commands.

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/bjorn-ingmanson/thefroject-plugins/idea-to-prd/github.svg)](https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/idea-to-prd)

Your own site

<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/idea-to-prd"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/idea-to-prd/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/bjorn-ingmanson/thefroject-plugins/idea-to-prd"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/idea-to-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,294 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.00086	$0.01294
Opus 5	$0.00043	$0.00647
Sonnet 5	$0.00017	$0.00259
Haiku 4.5	$0.00009	$0.00129

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

Security

Grade A, and why

idea-to-prd 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.

customer-success/skills/idea-to-prd/SKILL.md · 158 lines

How it starts

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

Idea to PRD

Take a rough product idea and turn it into a handoff-ready PRD through four stages. Each stage is gated by a user keyword — don't skip ahead, even if the user is excited.

Gather Context First

Read context/ for product positioning and target audience
Read notes/user-insights/ (if present) for known pain points and quotes
Check plans/ for active product plans the new idea may relate to or conflict with
Identify the user's role (PM, marketer, founder, designer) — adjust depth accordingly

The Four Stages

Stage 1 — Clarifying questions (immediate)

When the user shares an idea, generate 8-10 numbered clarifying questions before doing anything else. Cover:

Who is the user this serves?
What problem does it solve, in their words?
What's the desired outcome — what does success look like?
What constraints exist (timeline, budget, tech, regulatory)?
What have they tried, observed, or ruled out?
How does this compare to alternatives or existing solutions?
What does NOT belong in scope?

Wait for the user to answer. Don't auto-fill answers.

After answers come back, repeat unanswered questions or ask 2-3 follow-ups if needed. Don't move to Stage 2 until the picture is sharp.

End with: Next: type "spec doc" to generate the spec.

Stage 2 — Spec doc (triggered by "spec doc")

Generate a product spec from the answers. Save to outputs/discovery/<feature-slug>/01-spec.md:

# [Feature name] — Spec

## Product summary
[2-3 sentences]

## Problem solved
[What pain this removes, in user-language]

## Target audience
[Specific role, stage, or segment]

## Key features and functionality
- [Feature 1] — [what it does]
- [Feature 2] — ...

## Success metrics
- Leading: [observable in days/weeks]
- Lagging: [observable in months]

## Out of scope (explicit no's)
- [What this is NOT trying to do]

## Open questions
- [Anything still unclear]

End with: Next: type "design flows" to map the user flows.

Stage 3 — Design flows (triggered by "design flows")

Read the full file on GitHub · 158 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.

10d ago First seen · 158 lines · 86 tokens per session scan A 6ec9be2990f7

Subscribe to this mod's changes

idea-to-prd is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,294 once invoked, about $0.0004 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.

Design and UX Planning

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

idea-to-prd