Discovery Expert

Convert project source inputs into a structured Discovery Brief with gap detection.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill discovery-expert-timekast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Discovery Expert
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/roles/discovery
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill discovery-expert-timekast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams understand the project correctly before design or implementation by extracting and preserving source decisions, surfacing real gaps, and synthesizing a high-fidelity Discovery Brief that downstream work can trust.

Core Features & Use Cases

  • Source fidelity preservation: protects firm decisions (stakeholder, scope, deadlines, exclusions) to prevent drift during synthesis.
  • Gap-focused discovery: asks only what’s missing, marking uncertainty as Assumption/Working Hypothesis/Open Question rather than inventing details.
  • Structured discovery output: generates a complete Discovery Brief with coverage mapping, decision registry, and a reconciliation checklist for cross-checking §1–§11.
  • Discovery modes: supports D0 (from zero), D1 (with a source package), and D2 (auditing/deepening an existing brief).

Quick Start

Ask the AI to run the Discovery Expert role on your project inputs (describe what docs and plans you already have) and output a filled Discovery Brief using the 11 sections plus reconciliation.

Frequently Asked Questions about Discovery Expert

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

FAQPage Schema
How do I create a high-fidelity discovery brief from scattered project requirements?

To create a discovery brief, source inputs are converted into structured output by preserving firm decisions and detecting gaps without introducing drift. This ensures stakeholders align on MVP scope before downstream design or implementation begins.

What is scope alignment and how does it prevent project drift during discovery?

Scope alignment prevents project drift by applying source-of-truth preservation rules that freeze stakeholder decisions and exclusions. Uncertainty is marked as an assumption or open question rather than inventing details, keeping downstream plans faithful to original inputs.

How do I run discovery on existing project docs to surface missing requirements?

To run discovery on existing docs, use the D1 mode with a source package or D2 mode to audit an existing brief. The process applies adaptive gap questioning to extract only missing information, generating a decision registry and reconciliation checklist.

Can I use this discovery process for a product starting completely from zero?

Yes, the D0 discovery mode supports starting from zero. It extracts stakeholder decisions and identifies gaps to synthesize a complete Discovery Brief across 11 sections, ensuring alignment even when no prior source documents exist.

What is the best way to document project decisions for downstream design and implementation?

The best way to document decisions is generating a structured Discovery Brief with a decision registry and reconciliation checklist. This freezes firm decisions while marking unknowns as working hypotheses, providing a trustworthy source for design and implementation phases.

When should I not use an automated discovery process for stakeholder alignment?

You should not use automated discovery when source inputs are completely undefined or when stakeholders cannot provide any baseline decisions. The process requires source-of-truth preservation rules to function, as it extracts and structures existing decisions rather than inventing them.