sd-discover

Validates service-design claims against real discourse evidence and produces a schema-valid Discovery document.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/runlegion/legion --skill sd-discover-runlegion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sd-discover
Source: https://github.com/runlegion/legion/tree/main/plugin/skills/sd-discover
Command: npx skills add https://github.com/runlegion/legion --skill sd-discover-runlegion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams assert claims about user needs without checking whether real people actually say those things. This Skill tests each claim from a research agenda against a corpus of real discourse, producing an evidence-backed Discovery document where every claim earns a verdict: supported, bounded, contradicted, blocked, or saturated-unevidenced. ## Core Features & Use Cases - Evidence-based claim scoring: Probes a discourse corpus through the eavesdrop CLI, judges each claim against a same-lens null control, and scores insights on five axes (frequency, intensity, friction, urgency, fit) with structured evidence citations. - Inverse pass falsification: Attacks its own supported insights with counter-probes at the authoritative pass, so an all-supported result is treated as unfalsified rather than confirmed. - Park-and-resume workflow: Parks as a draft when the corpus is missing or a question is open, arms a deferred wake via legion, and resumes scoring once the crawl accumulates. - Prediction instrumentation: Emits confidence-scored predictions per verdict and witnesses the intent review's claim predictions, building a calibration track record. - Use Case: After sd-intent-review produces a research agenda for a new auth product, invoke this Skill to test each claim against Reddit and forum discourse, surface emergent pain points the intent missed, and land a Discovery document with contradicted claims routed to the operator for rulings. ## Quick Start Invoke the sd-discover skill after sd-intent-review to test the agenda's claims against the eavesdrop corpus and land a Discovery document.

Frequently Asked Questions about sd-discover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate product claims against real user discourse?

Run each claim's probe against an eavesdrop corpus alongside a null-control query on the same lens, then rerank both candidate sets in one call. Claims whose hits outrank the control are supported; the separation is reported as G = 2*AUC - 1 with its standard error, never as a fixed cutoff.

What does sd-discover do when the discourse corpus is missing?

It treats an empty query result as a missing corpus, not disconfirmation. It starts an eavesdrop crawl for the lens, signals the eavesdrop agent to keep the lens warm, parks the Discovery as a draft with blocked themes, and arms a deferred wake to resume scoring later.

Can sd-discover cut or rewrite a contradicted claim?

No. A contradicted claim is a finding, never a cut. The Discovery lands at review status listing each contradicted or saturated-unevidenced insight with a recommended ruling, and only the operator rules while the intent's owner makes any edits.

Why does sd-discover require an inverse pass before landing?

Probes written by a theme's author score their own topic on-topic, so an all-supported Discovery is unfalsified rather than confirmed. The inverse pass runs counter-probes against every supported insight at the authoritative pass, moving bounded insights to bounded status with counter-tagged evidence rows.

What are the limitations of eavesdrop scores for claim verdicts?

No eavesdrop score has a meaningful fixed cutoff: cosine similarity and rerank logits are only comparable within one call. Verdicts must come from claim-versus-control ranking differences, and absence claims require a census count with every spelling variant listed.