prd-v01-problem-framing

prd-v01-problem-framing is a skill for Claude Code from mattgierhart/PRD-driven-context-engineering. It costs 87 tokens per session (1,717 once invoked), scanned A, original, MIT.

A starting workflow for turning a vague product idea into a problem statement supported by early evidence. It records customer feedback and identifies which problems may shape the first version of the product.

In plain words
What is it for?
Use it at the beginning of product planning to document pain points, assess confidence, and define an initial scope signal.
Why use it?
It separates observed problems from guesses and shows what evidence is still missing before committing to features.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it at the beginning of product planning to document pain points, assess confidence, and define an initial scope signal.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattgierhart/prd-driven-context-engineering/prd-v01-problem-framing
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 mattgierhart/PRD-driven-context-engineering --skill prd-v01-problem-framing
Clone the repo
git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering

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.

agentmods badge for prd-v01-problem-framing

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v01-problem-framing.svg)](https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v01-problem-framing)
Your own site
<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v01-problem-framing"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v01-problem-framing.svg" alt="Measured on agentmods" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,717 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00087 $0.01717
Opus 5 $0.00044 $0.00859
Sonnet 5 $0.00017 $0.00343
Haiku 4.5 $0.00009 $0.00172

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

Security

Grade A, and why

prd-v01-problem-framing 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 8d 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.

.claude/skills/prd-v01-problem-framing/SKILL.md · 179 lines

How it starts

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

Problem Framing Skill

Transform market signals into evidence-anchored problem statements.

Consumes

This skill assumes you have zero prior research. It is the starting point.

  • No prior CFD- entries needed
  • No prior PR D required
  • Assumes: Founder/PM has observed market signals but hasn't validated them

Produces

This skill creates/updates:

  • CFD-* entries (customer feedback) — 1-5 per problem dimension, with confidence scoring (see PRINCIPLES.md)
  • PRD.md Why section — Evidence-anchored problem statement table
  • MVP scope signal — Identifies which problem dimensions will drive MVP feature scope (handed to v0.3)

All CFD- entries should include:

  • confidence: 1-3/5 (pre-product research, no usage data)
  • Evidence source (competitive analysis, interviews, workarounds, etc.)
  • Forward target: "Would move to 4/5 if we observe 10+ paying customers with this pain"

Workflow Overview

  1. Assess gaps → Identify what evidence is missing before you can confidently state a problem
  2. Anchor evidence → Create CFD- entries for each pain point dimension with confidence scoring
  3. Extract dimensions → Pull multiple distinct problems from each source
  4. Quantify costs → Add time/money/risk numbers to make pain concrete
  5. Draft statement → Populate the problem table, tied to CFD- entries

Core Output Template

Populate this table for every problem statement:

Element Definition Evidence
Who is hurting? Specific, findable, countable persona Segment size
What pain exists? Observable behavior or workflow friction CFD-ID
Cost of problem Time, money, or opportunity lost Quantified
Why now? Market trigger creating urgency Trend/event
What's impossible? Opportunity cost—what can't they do User quote

See assets/problem-statement.md for copy-paste template.

Step 1: Gap Assessment

Before drafting, create this status table:

Read the full file on GitHub · 179 lines

Files

What ships with it

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

  1. 8d ago First seen · 179 lines · 87 tokens per session scan A 1fc6abc72156

Subscribe to this mod's changes

prd-v01-problem-framing is a skill published in the GitHub repository mattgierhart/PRD-driven-context-engineering (182 stars, last pushed 7d ago), licensed MIT. It adds 87 tokens to every session and 1,717 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-30.