product-discovery

Installation
SKILL.md

Product Discovery

The entry ramp to the pipeline for anyone starting from an idea rather than a written spec. The pipeline's first input is a Markdown table of user stories, acceptance criteria, and a sprint breakdown; this skill produces that table by interviewing the user and synthesizing their answers. It is optional: skip it if the user already has stories and AC.

Two phases: interview to elicit the product, then synthesize the requirements table.

Phase 1: Interview

Elicit the product the way grill-me interviews a plan: one question at a time, recommend an answer for each, walk down each branch until it resolves, and do not move on until the user confirms. The goal is to extract enough to write real stories, not to design the solution. Cover, adapting to the idea:

  • Problem and outcome. What problem does this solve, for whom, and what does success look like? What happens today without it?
  • Users and roles. Who uses it? Name the distinct personas/roles and what separates them (permissions, goals). Roles drive both stories and later RBAC.
  • Core jobs. For each persona, the concrete jobs they need to do, start to finish. These become user stories. Push for the real workflow, including the unhappy paths.
  • Key entities and lifecycle. The main things the system tracks and the states they move through. A state machine here becomes acceptance criteria later.
  • Scope. What is explicitly in for the first release and what is deferred. Pin a Phase 1 boundary so the stories do not sprawl.
  • Constraints. Hard requirements: integrations, compliance, volume, languages/locales, deadlines.

Surface contradictions and gaps as you go. When the picture is complete, summarize it back and confirm before writing.

Installs
32
GitHub Stars
9
First Seen
Jun 24, 2026