brainstorming

Organize structured brainstorming sessions to align goals and design approaches before implementation.

5|1|Updated Mar 24, 2026

Search Tags:#design #planning #brainstorming #collaboration #ideation #spec-writing

Ready to run

npx skills add https://github.com/ANONIMO432HZ/OmniBrain-AI-Proxy-Smart --skill brainstorming-anonimo432hz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ANONIMO432HZ/OmniBrain-AI-Proxy-Smart/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/ANONIMO432HZ/OmniBrain-AI-Proxy-Smart --skill brainstorming-anonimo432hz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Brainstorming process provides a structured, consultative approach to understanding user needs, project context, and success criteria before any implementation work.

Core Features & Use Cases

Guided discovery prompts to surface goals, constraints, and success metrics.
Multi-approach design evaluation with 2-3 options and trade-offs before committing to a path.
Spec-forward workflow that generates a design brief and supports a formal design-review loop to move from idea to implementation planning.

Quick Start

Describe your goal, constraints, and success criteria, and I will guide you through a design-first brainstorming session.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I structure brainstorming sessions for product design and feature discovery?▼

Structured brainstorming sessions organize product design by guiding context gathering, clarifying questions, and evaluating 2-3 design approaches before committing to implementation. This enforces a documented process with exploration steps, design submissions, and a spec-review loop.

What is the best way to align project requirements and goals before software implementation?▼

Aligning project requirements before software implementation requires a spec-forward workflow that generates a design brief and supports a formal design-review loop. This consultative approach surfaces goals, constraints, and success metrics to transition from idea to implementation planning.

How do I evaluate multiple design approaches and trade-offs before committing to a build path?▼

Evaluating design approaches involves generating 2-3 options with documented trade-offs during a structured brainstorming session. This multi-approach design evaluation ensures you compare constraints and success criteria before selecting a path for software architecture or feature development.

Can I use guided brainstorming for software architecture planning and spec writing?▼

Guided brainstorming applies directly to software architecture planning and spec writing by enforcing a documented process of context gathering and exploration. It transitions design submissions through a spec-review loop to formalize implementation planning for product development.

When should I not use a structured brainstorming approach for ideation?▼

A structured brainstorming approach may not suit ideation when immediate implementation is required without design evaluation or spec review. If your project lacks defined success criteria or constraints to evaluate 2-3 design approaches against, this consultative process introduces unnecessary overhead.

What do I need to start a design-first brainstorming session for feature development?▼

Starting a design-first brainstorming session for feature development requires describing your goal, constraints, and success criteria. The guided discovery prompts then surface project context and clarify requirements to produce a design brief supporting the implementation planning transition.