Prd V04 Persona Definition

What it does

When your agent uses it

• Requests to define personas
• Create user profiles
• Identify target users
• User asks who are our users?

Example prompts

• “who are our users?”
• “define personas”
• “user profiles”
• “/prd-v04-persona-definition”

Requirements

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

Workflow steps

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

1. 1Pull USER TYPE from v0.1 Problem Framing (CFD-)
2. 2Pull SEGMENTS from v0.2 Market Definition (CFD-, BR-)
3. 3Pull TARGETING RULES from v0.3 Moat Definition (BR-)
4. 4Synthesize behavioral patterns from all CFD- evidence
5. 5Map FEA- features to each persona
6. 6Create PER- entries with full traceability

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

  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 V04 Persona Definition loads about 2.4k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 711 words of instructions outside code blocks.

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

~143

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

~2.4k

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

~3.1k

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). 711 words, ~2,432 tokens.

name

prd-v04-persona-definition

description

Synthesize behavioral personas from prior stage evidence for journey mapping and marketing during PRD v0.4 User Journeys. Triggers on requests to define personas, create user profiles, identify target users, or when user asks "who are our users?", "define personas", "user profiles", "target users", "persona creation", "who uses this product?". Consumes CFD- (v0.1-v0.3), BR- (targeting from v0.3 Moat), FEA- (v0.3 Feature Value Planning). Outputs PER- entries with behavioral profiles and feature relationships. Feeds v0.4 User Journey Mapping.

allowed-tools

Read, Write, Edit, Glob, Grep

context

fork

PER-001: The Overwhelmed Ops Manager
Source IDs: CFD-003 (pain: manual tracking), CFD-012 (value: automation), BR-041 (targeting: switchers at renewal)
Type: Primary
Confidence: 3/5 (source: 4-customer-interviews-jan-2026 + competitive-landscape confirms segment underserved)
Segment: SMB SaaS companies (10-50 employees)

Demographics:
  Role: Operations Manager / Head of Ops
  Context: Growing startup, wearing multiple hats, no dedicated tools budget
  Technical Level: Intermediate (comfortable with SaaS, not a developer)

Behavioral Profile:
  Goals: Reduce time spent on manual reporting (CFD-012)
  Frustrations: Current tools require too much setup (CFD-003)
  Decision Factors: Ease of use > feature count, must show ROI to CEO (CFD-025)
  Current Workflow: Spreadsheets + manual data entry + weekly report compilation

Product Relationship:
  Primary Value: CFD-012 ("Save 5 hours/week on reporting")
  Key Features: FEA-001 (auto-sync), FEA-003 (one-click reports), FEA-007 (dashboard) — all in MVP-SCOPE
  Pricing Sensitivity: BR-030 (SMB tier ≤$50/mo)
  Acquisition Channel: BR-041 (target at contract renewal of competing tools)

Marketing Hook: "Stop building reports. Start using them."
Next Target: "Would move to 4/5 if 5+ actual SMB ops managers validate this behavior in paid usage"

PER-XXX: [Persona Name]
Source IDs: [CFD-XXX, CFD-YYY, BR-ZZZ that inform this persona]
Type: [Primary | Secondary | Negative | Aspirational]
Segment: [From v0.2 market segment]

Demographics:
  Role: [Job title / function]
  Context: [Company size, industry, team structure]
  Technical Level: [Novice | Intermediate | Expert]

Behavioral Profile:
  Goals: [What they're trying to achieve — link to CFD- value]
  Frustrations: [Current pain points — link to CFD- pain]
  Decision Factors: [What influences their choices — link to CFD- research]
  Current Workflow: [How they solve this today]

Product Relationship:
  Primary Value: [CFD- value hypothesis they care about most]
  Key Features: [FEA-XXX, FEA-YYY most relevant to them]
  Pricing Sensitivity: [From BR- pricing rules]
  Acquisition Channel: [How they'll find us — from BR- targeting]

Marketing Hook: [One-sentence pitch for this persona]

PER-001: The Overwhelmed Ops Manager
Source IDs: CFD-003 (pain: manual tracking), CFD-012 (value: automation), BR-041 (target: switchers at renewal)
Type: Primary
Segment: SMB SaaS companies (10-50 employees)

Demographics:
  Role: Operations Manager / Head of Ops
  Context: Growing startup, wearing multiple hats, no dedicated tools budget
  Technical Level: Intermediate (comfortable with SaaS, not a developer)

Behavioral Profile:
  Goals: Reduce time spent on manual reporting (CFD-012)
  Frustrations: Current tools require too much setup (CFD-003)
  Decision Factors: Ease of use > feature count, must show ROI to CEO (CFD-025)
  Current Workflow: Spreadsheets + manual data entry + weekly report compilation

Product Relationship:
  Primary Value: CFD-012 ("Save 5 hours/week on reporting")
  Key Features: FEA-001 (auto-sync), FEA-003 (one-click reports), FEA-007 (dashboard)
  Pricing Sensitivity: BR-030 (SMB tier ≤$50/mo)
  Acquisition Channel: BR-041 (target at contract renewal of competing tools)

Marketing Hook: "Stop building reports. Start using them."

© 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 2 other files (references, assets) in .claude/skills/prd-v04-persona-definition of mattgierhart/PRD-driven-context-engineering.

• SKILL.md
• assets/per.md
• references/examples.md

Open the folder on GitHubat commit 30ed1b0