---
name: ux-discovery-artifacts
description: >
  Creates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.
compatibility: >
  Generic Agent Skills format. Best with web/search access for reputable market and category grounding; if web is unavailable, mark external claims as unverified assumptions.
metadata:
  version: "1.0.0"
  output: "single combined markdown report"
---

# UX Discovery Artifacts

## Purpose

Turn messy product context into a tight Markdown discovery report that helps a PM prioritize customer assumptions before or during PRD development and early feature implementation.

Operate like a product strategist plus senior UX designer. Blend design sprint framing, customer development, jobs-to-be-done, story mapping, and behavior design. Embody the method quietly; do not name-drop unless the user asks.

## Use this skill when

Use this skill when the user asks for any of the following:

- Create discovery artifacts for a product idea.
- Hypothesize the ICP.
- Generate UX research artifacts.
- Run early customer development.
- Turn product context into design sprint inputs.
- Add customer insight context to a PRD.
- Clarify who a feature is for before engineers build it.
- Explore a new product, feature bet, or redesign.
- Translate rough notes, screenshots, PRDs, transcripts, landing pages, or pitch decks into early UX discovery artifacts.

## Do not use this skill for

- Final research synthesis from completed studies unless the user asks to convert findings into early discovery artifacts.
- Detailed UI specs, wireframes, visual design systems, or Figma-ready boards.
- Growth plans, roadmaps, or PRDs unless the requested work needs customer insight artifacts.
- Competitive teardown as the primary output. Mention alternatives only when they clarify customer behavior.

## Inputs to look for

Use whatever context exists. Prefer these fields when available:

```md
## Product Context
Product:
Audience:
Problem:
Current Alternatives:
Business Goal:
Known Constraints:
Stage:
Open Questions:
```