brainstorming

Transform initial concepts into detailed technical designs through guided questioning.

Updated Sep 24, 2021
One-click install
npx skills add https://github.com/coolguy1771/dotfiles --skill brainstorming-coolguy1771
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/coolguy1771/dotfiles/tree/main/chezmoi/private_dot_cursor/skills/brainstorming
Command: npx skills add https://github.com/coolguy1771/dotfiles --skill brainstorming-coolguy1771

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you transform raw ideas into well-defined designs and technical specifications by guiding you through a structured brainstorming and validation process.

Core Features & Use Cases

  • Idea Refinement: Asks targeted questions to clarify user intent, requirements, and constraints.
  • Approach Exploration: Proposes and evaluates multiple design options with their trade-offs.
  • Incremental Design Presentation: Delivers designs in manageable sections for continuous feedback.
  • Use Case: Before starting a new feature, use this Skill to explore the problem space, define the core functionality, and get buy-in on the proposed architecture.

Quick Start

Use the brainstorming skill to help design a new user authentication flow.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
What is the best way to turn a raw product idea into a technical specification?

To turn a raw idea into a technical specification, this Skill uses a structured, question-driven dialogue to clarify user intent, explore design alternatives, and incrementally validate requirements prior to implementation.

How do I gather requirements for a new feature before writing code?

You can gather requirements for a new feature by engaging in guided dialogue that asks targeted questions, defines core functionality, evaluates multiple design options, and highlights architectural trade-offs.

When do I need a structured brainstorming process for software design?

You need a structured brainstorming process for software design when starting a new feature, building a component, or modifying behavior, allowing you to map the problem space and validate technical considerations first.

Does this approach help evaluate multiple design options and their trade-offs?

Yes, this approach helps evaluate multiple design options and their trade-offs by proposing alternatives during the ideation phase and validating them incrementally through continuous user feedback.

Can I use this to refine ideas for component building and behavioral modifications?

Yes, you can use this to refine ideas for component building and behavioral modifications by exploring design considerations and user constraints through a structured validation process.