brainstorm

Convert ambiguous product ideas into an approved design document.

46|2|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/gracefullight/krds --skill brainstorm-gracefullight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/gracefullight/krds/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/gracefullight/krds --skill brainstorm-gracefullight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams move from vague intentions to a clear, design-first plan by clarifying user intent and constraints before committing to implementation.

Core Features & Use Cases

  • Intent clarification: Surfaces what users actually need and why, reducing misalignment later in delivery.
  • Constraint mapping: Identifies requirements, limitations, and success criteria so design decisions stay grounded.
  • Approach proposal to approval: Generates candidate directions and produces an approved design document before planning execution.
  • Use Case: Use it at the start of a new feature to define scope and produce a sign-off-ready design before engineering work begins.

Quick Start

Read and follow the steps in .agents/workflows/brainstorm.md to produce an approved design document after clarifying intent and constraints.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a vague product idea into an approved design document?

Converting a vague product idea into an approved design document requires clarifying user intent and mapping constraints early in discovery. This workflow guides you step-by-step through ideation to produce a sign-off ready, design-first artifact before engineering begins.

What is design ideation for pre-planning new features?

Design ideation for pre-planning is the process of surfacing user intent and identifying constraints to define feature scope. It transforms ambiguous requirements into grounded design decisions, reducing misalignment before committing to implementation.

How do I clarify user intent and constraints for product discovery?

Clarifying user intent and constraints during product discovery involves mapping requirements, limitations, and success criteria. This ensures design decisions stay grounded in actual user needs and produces candidate directions for approval.

What's the best way to define scope for a new user flow before engineering?

Defining scope for a new user flow is best achieved by generating an approved design document prior to execution. This approach proposes candidate directions and secures sign-off, ensuring alignment before development work starts.

Do I need a specific environment to produce a design-first artifact?

Producing a design-first artifact requires no specific external environment or dependencies. You simply follow the step-by-step workflow instructions provided in the repository's workflow file to map constraints and clarify intent.