brainstorming

Convert vague ideas into validated design concepts with an approval gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming helps teams convert vague ideas into structured design concepts through a guided, question-driven process that surfaces intent, requirements, and constraints before implementation.

Core Features & Use Cases

  • Guided discovery and clarification to align on project context
  • Propose 2-3 design approaches with trade-offs and recommended path
  • Produce a design document with sections and approval gate before coding

Quick Start

Begin by clarifying the project context, then lead with the design questions, present a plan, and obtain user approval before any implementation.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into validated design concepts?

Brainstorming for early-stage product development involves a guided discovery process to align on context, explore multiple design approaches with trade-offs, and generate a structured design document before moving into implementation.

What is the best way to structure a design sprint for early-stage product development?

A structured design sprint for product development should enforce a question-driven flow: clarify context, present 2-3 design options with a recommended path, and output a design document gated by user approval before coding starts.

How do I create a design document that prevents premature implementation?

To create a design document that prevents premature implementation, enforce a hard approval gate after presenting design approaches and trade-offs, ensuring user sign-off on the final spec is required before any coding phase begins.

Can I use a guided ideation process to align team collaboration on project requirements?

Yes, guided ideation facilitates team collaboration by applying a question-driven discovery process that surfaces project intent, constraints, and requirements, ultimately aligning stakeholders before selecting a design path.

How does a structured brainstorming workflow handle design option exploration?

Structured brainstorming workflows handle design option exploration by proposing 2-3 distinct approaches, outlining the specific trade-offs for each, and recommending a primary path to guide stakeholders toward a validated design decision.

When should I not use a structured design spec workflow for ideation?

You should not use a structured design spec workflow if your project bypasses early-stage ideation, requires immediate ad-hoc coding without stakeholder alignment, or operates without the need for formal design doc approval gates.