brainstorm

Guide vague ideas into concrete designs through structured questioning and approval.

Updated Aug 27, 2026

Search Tags:#design #planning #collaboration #requirements #brainstorm #design-doc

Ready to run

npx skills add https://github.com/mengdehong/opencode-dotfiles --skill brainstorm-mengdehong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/mengdehong/opencode-dotfiles/tree/main/skills/brainstorm
Command: npx skills add https://github.com/mengdehong/opencode-dotfiles --skill brainstorm-mengdehong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps turn ideas into fully formed designs and specs by guiding discovery, clarifying requirements, and aligning stakeholders before any implementation.

Core Features & Use Cases

Explore project context to surface assumptions and constraints.
Ask clarifying questions one at a time to refine goals and success criteria.
Propose 2-3 approaches with trade-offs and recommendations.
Present design sections and obtain user approval before proceeding to documentation.
Write a design doc and perform a design self-review to ensure clarity and completeness.
Transition to implementation by triggering the planning step once the design is approved.

Quick Start

Begin by outlining the current project context and asking a clarifying question to refine the idea.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I turn vague ideas into a concrete design and design doc?▼

To turn vague ideas into a concrete design doc, you use guided brainstorming that explores project context, asks clarifying questions, proposes approaches, and requires user approval before drafting the final design documentation.

What is the best way to facilitate brainstorming for project requirements?▼

Facilitating brainstorming for requirements involves surfacing assumptions through clarifying questions posed one at a time, then proposing 2-3 approaches with trade-offs and recommendations to align stakeholders before proceeding to design documentation.

How does guided brainstorming transition into implementation planning?▼

Guided brainstorming transitions into implementation planning by presenting design sections, obtaining explicit user approval, writing the design doc, performing a self-review, and then triggering a controlled handoff to the planning step.

Can I align stakeholders and refine goals before writing a design doc?▼

Yes, you can align stakeholders and refine goals before writing a design doc by exploring project context to surface constraints, asking clarifying questions to establish success criteria, and proposing multiple approaches for approval.

Does the brainstorming process enforce a design self-review before handoff?▼

Yes, the brainstorming process enforces a design self-review to ensure clarity and completeness after the design doc is written, requiring user approval before performing a controlled handoff to implementation planning.

When do I need to propose multiple approaches during design planning?▼

You need to propose 2-3 approaches during design planning after clarifying questions have refined goals and success criteria, allowing stakeholders to evaluate trade-offs and recommendations before the final design presentation.