discovery-agent

Orchestrate product discovery from idea intake to dev-ready handoff deliverables.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/ThanabordeeN/gemini-productivity-skills --skill discovery-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-agent
Source: https://github.com/ThanabordeeN/gemini-productivity-skills/tree/main/discovery-agent
Command: npx skills add https://github.com/ThanabordeeN/gemini-productivity-skills --skill discovery-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as an orchestrator for the Discovery Phase, reducing manual coordination and ensuring a complete discovery package is produced and handed off automatically to the backlog agent.

Core Features & Use Cases

  • Automates input collection and structured interviews via a question bank to produce a discovery package.
  • Generates Deliverables: problem statement, competitive analysis, BRD draft, feasibility study, and a handoff-ready requirements summary.
  • Orchestrates data flow to product-backlog-agent for sprint planning and backlog creation.

Quick Start

Provide an initial idea or problem statement to the skill and let it generate a complete discovery package ready for handoff.

Frequently Asked Questions about discovery-agent

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

FAQPage Schema
How do I automate product discovery and requirements gathering for a dev-ready handoff?

Product discovery and requirements gathering can be automated by orchestrating idea intake, problem framing, and stakeholder interviewing to generate a complete discovery package. This produces structured deliverables like BRD drafts and feasibility studies for immediate handoff.

What deliverables are needed for a complete product discovery package?

A complete product discovery package requires a problem statement, competitive analysis, BRD draft, feasibility study, and a requirements summary. These structured documents ensure cross-document coordination and provide a dev-ready handoff for sprint planning.

How do I draft a BRD and feasibility study from an initial product idea?

Drafting a BRD and feasibility study from an initial idea involves automated input collection and structured stakeholder interviews. The process frames the core problem and packages the analysis into brd-requirements.docx and feasibility-study.docx files.

Can I trigger automatic backlog creation after completing product discovery?

Automatic backlog creation can be triggered after product discovery by passing the generated requirements summary to a product-backlog-agent. This orchestrates the data flow directly from discovery analysis into sprint planning.

What is the best way to coordinate cross-document requirements during discovery?

The best way to coordinate cross-document requirements is to use an orchestrator that manages data flow from idea intake to final handoff. This ensures the problem statement, competitive analysis, and BRD are aligned and packaged together automatically.