brainstorm

Generate a structured brainstorming artifact from an initial idea.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Honigbart/honeyflow --skill brainstorm-honigbart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/Honigbart/honeyflow/tree/main/brainstorm
Command: npx skills add https://github.com/Honigbart/honeyflow --skill brainstorm-honigbart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes an early idea into a structured brainstorming artifact that can feed critique and planning stages.

Core Features & Use Cases

  • Structured idea capture for new products, features, refactors, or workflow changes.
  • Generates a plan-oriented artifact ready for downstream critique and evolution.
  • Anchors work to a unique plan slug and the .ai planning workspace for traceability.

Quick Start

Provide a brief idea and confirm a plan slug to generate the claude_brainstorm.md artifact.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I create a structured brainstorming artifact for a new product feature?

To create a structured brainstorming artifact, provide a brief idea and confirm a plan slug to generate a claude_brainstorm.md file. This artifact organizes your initial idea to guide critique and planning.

What is the best way to organize early ideas for refactoring or workflow changes?

Organizing early ideas involves generating a structured brainstorming artifact anchored to a plan slug within a namespaced system. This creates a traceable file ready for downstream critique and planning.

Can I use structured ideation to plan changes without prior technical setup?

Structured ideation requires no external dependencies but needs a plan slug and the .ai planning workspace. You provide an idea and confirm the slug to generate the artifact successfully.

How does a structured brainstorming artifact feed into downstream planning?

A structured brainstorming artifact feeds into planning by capturing the initial idea in a standardized format at .ai/plans/<slug>/claude_brainstorm.md. This file is then ready for critique and evolution into focused plans.

Are there limitations to using a namespaced plan slug system for ideation?

The namespaced plan slug system anchors artifacts to a specific directory structure, meaning artifacts are tightly coupled to the .ai/plans workspace. Ideation outside this structure lacks automated status tracking and traceability.