brainstorming

Guide teams to structure ideas into a validated design direction.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/justcyl/my-skills --skill brainstorming-justcyl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/justcyl/my-skills/tree/main/.skills/archived-skills/brainstorming
Command: npx skills add https://github.com/justcyl/my-skills --skill brainstorming-justcyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide ensures teams align on project purpose and constraints before starting design or implementation, reducing wasted effort and rework.

Core Features & Use Cases

  • Structured questioning to uncover goals, risks, and success criteria.
  • 2-3 approach proposals with trade-offs to guide decision-making.
  • Transition to a formal design process with a documented plan and an approval gate.

Quick Start

Describe the project context, ask clarifying questions one at a time, propose 2-3 approaches, and present a design for approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I align stakeholders on design requirements before coding?

Aligning stakeholders on design requirements involves structured questioning to uncover project goals, risks, and success criteria. This approach proposes multiple design directions with trade-offs to secure formal approval before implementation begins.

What is the best way to turn project ideas into a validated design direction?

Turning project ideas into a validated design direction requires checking project context and asking clarifying questions. Teams then review proposed approaches with trade-offs to transition into a formal design process with an approval gate.

How do I document a design plan for stakeholder approval?

Documenting a design plan for stakeholder approval requires summarizing the project context, clarifying questions, and proposed approaches into a formal design doc. This documented plan serves as an approval gate prior to execution.

Can I use structured brainstorming to reduce design rework?

Structured brainstorming reduces design rework by ensuring teams align on project purpose and constraints before starting implementation. This prevents wasted effort by validating the design direction through an approval gate.

When do I need to propose multiple approaches with trade-offs during ideation?

Proposing multiple approaches with trade-offs during ideation is needed when projects require clear goals, constraints, and stakeholder alignment prior to coding. This guides decision-making by presenting 2-3 design directions for comparison.

Why does my team need an approval gate before starting design execution?

An approval gate before design execution ensures stakeholder alignment on a documented design plan. It prevents wasted effort and rework by verifying that project purpose, constraints, and proposed approaches meet success criteria.