ot-discover

Runs interactive product discovery sessions that produce an evidence-tagged product-brief.md.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-discover-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-discover
Source: https://github.com/triage-software/skills/tree/main/skills/ot-discover
Command: npx skills add https://github.com/triage-software/skills --skill ot-discover-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often start building on unverified assumptions, invented personas, and vague problem statements. This Skill runs a structured discovery and define session that gathers real material first, tags every claim with its evidence tier, and writes a product brief that downstream planning, spec-writing, and review skills can rely on. ## Core Features & Use Cases - Evidence-first brief generation: Writes product-brief.md with one claim per line, each tagged by evidence tier (interview, data, document, product, benchmark, synthetic, assumption) plus a coverage line. - Three discovery modes: Adapts question ladders, mandatory sections, and sign-off rules for existing products, client ideas, or the team's own ideas. - Quality and skeptic gates: Scores the draft against a quality gate and dispatches a fresh-context skeptic subagent whose findings return as plain interview questions. - Use Case: A founder with a new product idea runs the skill, answers two rounds of concrete questions, and receives a product brief with riskiest assumptions, kill criteria, and a collection plan for missing evidence. ## Quick Start Ask the agent to run ot-discover on your product idea, for example: run a discovery session for our new billing feature and write the product brief.

Frequently Asked Questions about ot-discover

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

FAQPage Schema
How do I run a product discovery session with an AI agent?▼

Invoke the skill with an optional topic and mode flag, then answer its interview rounds of at most eight concrete questions each. It synthesizes your answers and existing research material into a product-brief.md with evidence tags and a coverage line.

What is a product brief and what sections does it contain?▼

The brief is a fixed-structure markdown file covering vision, target group, problems with evidence, goals, scope, business rules, non-goals, decisions, riskiest assumptions, and open questions. Every claim carries an evidence tag and a source pointer.

Can I use this without a configured agent pipeline?▼

Yes, the config file is optional. Without .ai/agentic.config.json the skill writes to .ai/specs by default and continues normally; it never auto-runs setup or asks where the brief should land.

What happens when there is no research material for a section?▼

The section is not written from nothing. It goes on a collection plan naming who to ask, what to ask, and which capture template to use, and the brief's coverage line reports how many entries are waiting for material.

What are the limitations of the quick pass mode?▼

Quick mode runs one round of at most eight questions, replaces the skeptic subagent with an inline checklist, and scores only critical quality-gate items. A quick brief does not satisfy missing readiness evidence and the report states what a full run would add.