brainstorm

Generate a markdown document exploring product ideas and technical problems.

3|Updated Apr 27, 2026

Search Tags:#workflow #documentation #brainstorming #ideation #problem-solving #product-management

Ready to run

npx skills add https://github.com/zoraxl/team-brain --skill brainstorm-zoraxl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/brainstorm
Command: npx skills add https://github.com/zoraxl/team-brain --skill brainstorm-zoraxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents premature planning and implementation by providing a structured framework for exploring ideas, identifying risks, and surfacing open questions before any development work begins.

Core Features & Use Cases

Structured Exploration: Guides the user through goals, non-goals, constraints, and edge cases.
Lifecycle Integration: Creates a durable, metadata-tracked brainstorm document that serves as the foundation for the entire development lifecycle.
Use Case: When a team member has a vague idea for a new feature, use this skill to map out the problem space and define success criteria before writing a single line of code or creating tickets.

Quick Start

Invoke the brainstorm skill by typing /brainstorm followed by the idea or problem you want to explore.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I structure product ideas and identify constraints before planning?▼

To structure product ideas before planning, you need a framework that captures goals, non-goals, constraints, and edge cases. This approach generates a comprehensive markdown document to map the problem space and define success criteria.

What is the best way to document brainstorming for product management workflows?▼

The best way to document brainstorming for product management is to use a structured markdown format with lifecycle metadata. This creates a durable document capturing initial requirements and open questions for seamless handoff to subsequent development stages.

How do I prevent premature implementation when exploring a vague feature idea?▼

To prevent premature implementation, use a structured exploration framework to surface risks and open questions before development begins. This maps the problem space thoroughly by defining success criteria prior to writing code or creating tickets.

Does this brainstorming skill require any specific dependencies or environment setup?▼

No specific dependencies or environment setup are required to use this brainstorming skill. It operates independently to guide structured problem exploration and generates a markdown document adhering to defined output format and lifecycle metadata standards.

When should I use a structured ideation document in the development lifecycle?▼

You should use a structured ideation document at the very beginning of the development lifecycle, before planning or implementation. It captures initial requirements and open questions, serving as the foundation for subsequent development stages.

Can I integrate captured brainstorming requirements directly into my team workflow?▼

Yes, you can integrate captured requirements into your team workflow through lifecycle metadata standards. The generated markdown document operates within the team-brain lifecycle to ensure a seamless handoff to subsequent planning and implementation stages.