brainstorming

Capture project context and clarify requirements before design approval.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill brainstorming-luizedupp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/LuizEduPP/skills/tree/main/brainstorming
Command: npx skills add https://github.com/LuizEduPP/skills --skill brainstorming-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents jumping into implementation before fully understanding the project context and desired outcomes, avoiding wasted effort caused by hidden assumptions.

Core Features & Use Cases

  • Context Exploration: Guides reviewing files, docs, and recent changes before asking questions, so every design starts anchored in reality.
  • Guided Clarification: Enforces one clarifying question at a time, ensuring purpose, constraints, and success criteria are well understood.
  • Design Proposal Workflow: Requires presenting 2-3 approaches with trade-offs, capturing the chosen design in a committed spec, conducting a self-review, obtaining user sign-off, and gating implementation through writing-plans.

Quick Start

Prompt the assistant to assess the project context, ask clarifying questions, outline alternative approaches, draft the approved design, and then request implementation planning.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I prevent premature implementation before design requirements are fully clarified?

To prevent premature implementation, use a structured brainstorming workflow that captures project context, asks clarifying questions sequentially, and gates coding until a documented design spec is reviewed and approved.

What is the best way to document design approaches for a new product feature?

The best way to document design approaches is to outline 2-3 alternative solutions with trade-offs, capture the chosen approach in a committed spec, and conduct a self-review before requesting user sign-off.

How do I structure a requirements gathering process for UI flows?

Structure the requirements gathering process by first exploring existing files and recent changes, then enforcing one clarifying question at a time to fully understand purpose, constraints, and success criteria before proposing designs.

Does spec-writing require exploring project context before asking clarifying questions?

Yes, effective spec-writing requires reviewing files, docs, and recent changes before asking questions. This ensures the design process starts anchored in reality rather than hidden assumptions.

How do I get design approval before starting implementation on functionality changes?

To get design approval, draft a design doc outlining approaches and trade-offs, commit the chosen spec, conduct a self-review, and gate implementation planning until explicit user sign-off is obtained.

When should I use an implementation gate for design brainstorming?

Use an implementation gate when working on product features, UI flows, or functionality changes that require design approval. It prevents wasted effort caused by jumping into coding with hidden assumptions.