Prd V01 User Value Articulation

What it does

When your agent uses it

• Completing problem framing
• Defining user outcomes
• Articulating value propositions
• Requests like what value do users get

Example prompts

• “what value do users get”
• “define outcomes”
• “articulate the benefit”
• “/prd-v01-user-value-articulation”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch, WebFetch

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Receive pain points → Read CFD-IDs from Problem Framing
2. 2Identify value unit → Time / Money / Risk / Capability
3. 3Transform pain → value → Apply transformation pattern
4. 4Anchor to evidence → What proof users want this outcome?
5. 5Create CFD entry → Tag as value hypothesis with tier

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • WebSearch
  • WebFetch

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V01 User Value Articulation loads about 1.6k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 556 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~118

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 556 words, ~1,566 tokens.

name

prd-v01-user-value-articulation

description

Transform validated pain points into articulated user value statements for PRD v0.1 Spark. Triggers on completing problem framing, defining user outcomes, articulating value propositions, or requests like "what value do users get", "define outcomes", "articulate the benefit", "finish v0.1", "pain to value", "what do they gain". Outputs CFD- entries tagged as value hypotheses with evidence tiers. Follows Problem Framing skill in workflow.

allowed-tools

Read, Write, Edit, Glob, Grep, WebSearch, WebFetch

context

fork

Problem Framing → User Value Articulation → v0.2 Market Definition
     (pain)              (value)                  (who cares most)

CFD-015: Value Hypothesis — Eliminate manual reconciliation workflow

Source Pain: CFD-001 (sales teams waste 5+ hours/week)
Evidence Tier: 2-3 (workaround + quantified cost)
Confidence: 3/5 (source: 3-customer-interviews-jan-2026)
Value Statement: "Reclaim 5 hours/week for strategic pipeline management"
Transformation: [5 hours wasted] → [5 hours available for growth]
Framing Type: Negative Removal (acute quantified loss)
Quantification: 5 hours/week = ~250 hours/year = $12,500 (at $50/hr)
Next Target: "Would move to 4/5 if we observe beta cohort using this feature"

CFD-###: Value Hypothesis — [Title]
Type: Value Hypothesis
Source Pain: CFD-###
Evidence Tier: [1-5]

Value Statement: "[User gains X measured in Y]"
Transformation: [Pain] → [Value]
Framing Type: [Type]
Quantification: [Number with unit]

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references, assets) in .claude/skills/prd-v01-user-value-articulation of mattgierhart/PRD-driven-context-engineering.

• SKILL.md
• assets/value-statement.md
• references/research-prompts.md
• references/transformation-examples.md

Open the folder on GitHubat commit 30ed1b0