idea-exploration

Clarify rough product ideas into structured IdeaBriefs for evaluation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill idea-exploration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-exploration
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/idea-exploration
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill idea-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams and individuals turn vague or early-stage ideas into a concise, structured IdeaBrief so stakeholders can evaluate viability and next steps without jumping prematurely to specification or implementation.

Core Features & Use Cases

  • Structured output: Produces an IdeaBrief capturing the core idea, target users, key use cases, open questions, risks, alternatives, and a recommendation.
  • Exploratory focus: Emphasizes surfacing unknowns, exploring plausible directions, and stress-testing assumptions before committing to planning.
  • Use Cases: Early product discovery sessions, triaging multiple proposed directions, preparing concepts for stakeholder review, and deciding whether to proceed to mapping or spec.
  • Template-driven: Aligns output to the repository template templates/workflows/IDEA_BRIEF.md to ensure consistent artifacts.

Quick Start

Create an IdeaBrief that summarizes the core idea in one sentence, identifies the primary user, lists 3–5 key use cases, enumerates open questions and risks, explores alternative directions, and ends with a clear recommendation.

Frequently Asked Questions about idea-exploration

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

FAQPage Schema
How do I turn rough product ideas into a structured brief for stakeholder review?

Turn rough product ideas into a structured IdeaBrief by summarizing the core concept, identifying primary users, listing key use cases, and surfacing risks. This structured brief helps stakeholders evaluate viability and next steps without prematurely jumping to implementation.

What is the best way to triage multiple feature concepts during product discovery?

Triage multiple feature concepts during product discovery by generating an IdeaBrief for each direction. This process stress-tests assumptions, explores plausible directions, and provides a clear recommendation aligned to the IDEA_BRIEF template for consistent artifact comparison.

How do I scope an early-stage brainstorming idea to decide if we should proceed to spec?

Scope an early-stage brainstorming idea by clarifying it into an IdeaBrief that enumerates open questions, risks, and alternatives. This exploratory focus ensures you validate assumptions and define plausible directions before committing to mapping or specification.

Does this idea exploration approach work for evaluating individual feature proposals?

Yes, idea exploration works for evaluating individual feature proposals by capturing the core idea, target users, and user value in a concise format. It emphasizes surfacing unknowns and exploring plausible directions to determine if the feature warrants further planning.

When should I not use a template-driven IdeaBrief for ideation?

Avoid using a template-driven IdeaBrief when a concept requires immediate, detailed technical specification rather than exploratory triage. This approach focuses on high-level viability, open questions, and stakeholder evaluation, not on generating comprehensive implementation requirements.