Agent skill · magnus919
product-discovery
Discover product requirements from human stakeholders — map who to talk to, ask questions that surface hidden assumptions, detect gaps in real time, resolve conflicts, and translate conversations into structured SDD specs. Phase 0 upstream of Spec-Driven Development.
What it needs
About 4k tokens when loaded.
What this skill does
Product Discovery — Stakeholder Map Pre-discovery work begins before any conversation. Load this reference first when planning discovery: Reference Load when File ----------- ----------- ------ Stakeholder Mapping & Sequencing You need to decide who to interview and in what order references/stakeholder-mapping.md Interview Protocol Design You're designing a question stack for a specific stakeholder type references/question-patterns.md Gap Detection Techniques You're preparing to recognize what stakeholders don't say references/gap-detection.md Pipeline: Phase 0 — Discovery Load the reference for the phase you're entering. Core principles - Closed questions confirm what you already think; open questions discover what you didn't know to ask. If the answer can be "yes" or "no," you're validating, not discovering. - Knowledge holders come first; authority holders validate — they don't originate. The person who knows the problem is not the same person who approves the budget. - Conflicts are almost never about what they appear to be. Surface disagreements are proxies for unstated differences in assumptions, risk tolerance, or incentives. - Every weasel word represents a gap. "Probably," "ideally," "eventually" — each is a known issue the stakeholder hasn't committed to addressing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/product-discovery