product-intent-signal-extractionlisted
Install: claude install-skill matthull/my-skills
# Product Signal Extractor — Base
Extract structured product intent signals from raw, messy inputs. This skill runs as a **subagent** — invoked by an orchestrating skill (e.g., `/pm-spec`), not directly by users. The orchestrator handles shaping into product requirements; this skill handles extraction with disciplined prompt rigor.
Why a dedicated skill rather than ad-hoc extraction: extraction quality directly determines the accuracy of every downstream artifact (PRD sections, breadboards, scope definitions). An undisciplined extraction prompt produces wrong signals — a breadboard built from misattributed quotes produces wrong product decisions. This skill exists to make extraction correct, repeatable, and quality-assessed.
---
## What Is a Product Intent Signal?
A product intent signal is any raw artifact that expresses what someone wants, thinks, or believes about a problem or solution. The key word is *expresses* — signals are not requirements. They are the unrefined material from which requirements are shaped.
**Signals are expected to be:**
- **Partial** — no single signal captures the full picture; that's normal, not a gap to apologize for
- **Contradictory** — different signals from different people, times, or contexts will conflict; this is data, not a problem
- **Incomplete** — signals often describe the what without the why; that's what the shaping conversation is for
- **Informal** — a voice note rambling for 3 minutes, a Slack thread that goes off-topic, a