ideate

Generate structured idea candidates with EXPLORE, PARK, and DROP verdicts.

8|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/duthaho/skillhub --skill ideate-duthaho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideate
Source: https://github.com/duthaho/skillhub/tree/main/.claude/skills/ideate
Command: npx skills add https://github.com/duthaho/skillhub --skill ideate-duthaho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid premature convergence when brainstorming by forcing deliberate divergence first, so you do not stop at the first plausible idea. It is useful when you need fresh directions for a project, a product, or an open-ended problem and want a short list that is both imaginative and judged.

Core Features & Use Cases

  • Structured divergence: Uses named lenses to generate ideas from different angles instead of variations of the same thought.
  • Clustering and verdicts: Groups similar ideas, keeps the sharpest version, and labels each one as EXPLORE, PARK, or DROP.
  • Persistent memory: Writes results to a tracker so repeat runs can start from what changed since the last session.
  • Use case: A team can use it to brainstorm product directions for a repo, then narrow them into a few concrete next steps with clear rationale.

Quick Start

Ask for a structured idea session for your repository or topic, and let the skill generate, cluster, and judge the options.

Frequently Asked Questions about ideate

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

FAQPage Schema
How do I prevent premature convergence during product brainstorming sessions?

To prevent premature convergence during product brainstorming, you need structured divergence first. This approach forces you to generate ideas from multiple named lenses instead of stopping at the first plausible thought, ensuring broader exploration before narrowing down options.

What is the best way to structure idea generation for an open-ended problem?

The best way to structure idea generation for an open-ended problem is to apply multiple analytical lenses, cluster similar ideas together, and label each one with a clear verdict like EXPLORE, PARK, or DROP to maintain a judged short list of directions.

Can I use repository analysis to generate product strategy directions?

Yes, you can use repository analysis to generate product strategy directions. By reading your repository context, the brainstorming process can propose fresh project directions specifically tailored to your codebase and current constraints.

How do I track brainstorming outcomes across multiple ideation sessions?

You can track brainstorming outcomes across multiple ideation sessions by persisting results to a tracker. This persistent memory records EXPLORE, PARK, and DROP decisions, allowing repeat runs to start from what changed since the last session.

Does structured ideation work for narrowing down variations of the same thought?

Structured ideation prevents narrowing down mere variations of the same thought. By using named lenses to generate ideas from different angles, it forces genuine divergence and clusters similar ideas to keep only the sharpest version before judging them.