discovery-analyst

To turn messy user interviews and feedback into traceable requirements, ingest raw discovery data to systematically extract Observations, Insights, Hypotheses, and Assumptions. This generates candidate requirements with full provenance lineage for gate 0 review.

A discovery log is a structured artifact that preserves discovery provenance by tracking observations, insights, hypotheses, and assumptions. You need it for gate 0 review to provide an auditable workflow before handing off candidate requirements.

To generate candidate requirements from raw research tickets, input the ticket data to extract structured hypotheses and assumptions. The process outputs EXPERIMENTS.md and CANDIDATE-XXXX entries that maintain full discovery lineage for approval.

Yes, you can use discovery-analyst to structure assumptions and hypotheses from research. It applies a systematic extraction process to subjective discovery inputs, converting them into structured artifacts with traceable lineage for downstream handoff.

Yes, discovery-analyst works with requirement-architect by producing DISCOVERY_LOG.md, EXPERIMENTS.md, and CANDIDATE-XXXX entries. These structured artifacts preserve discovery provenance specifically for seamless handoff to requirement-architect.

The best way to document discovery provenance for auditable workflows is to systematically extract observations and insights from raw data into structured files. This produces traceable artifacts like DISCOVERY_LOG.md that record full lineage for gate 0 approval.