brainstorming

Clarify requirements and explore design options for software development projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps clarify user intent, explore different approaches, and make informed design decisions before proceeding with feature implementation or building components.

Core Features & Use Cases

  • Requirement Clarity: Assess if requirements are clear or if brainstorming is needed.
  • Idea Understanding: Understand the user's intent through structured questions and techniques.
  • Approach Exploration: Propose 2-3 concrete approaches with their pros and cons.
  • Design Capture: Summarize key decisions in a structured design document.
  • Incremental Validation: Ensure alignment with user expectations.
  • Anti-Patterns Avoidance: Promote simplicity and proven patterns in design.

Quick Start

Use the 'brainstorming' skill to help explore the design of a new feature before starting development.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify project requirements before starting software development?

To clarify project requirements before software development, you can use structured brainstorming sessions to assess requirement clarity, understand user intent through targeted questions, and capture key design decisions in a structured document.

What is the best way to explore design options for a new software feature?

The best way to explore design options for a new software feature is to propose 2-3 concrete approaches, evaluate their pros and cons, and ensure alignment with user expectations through incremental validation before implementation.

When do I need to use a structured brainstorming process for software project planning?

You need to use a structured brainstorming process for software project planning when requirements are unclear, requiring you to understand user intent, explore different design approaches, and make informed decisions to ensure project success.

How do I avoid anti-patterns when making design decisions for software development?

To avoid anti-patterns when making design decisions for software development, promote simplicity and use proven patterns during brainstorming, capturing these choices in a structured design document for incremental validation.

Can I capture key design decisions in a structured document after exploring approaches?

Yes, you can capture key design decisions in a structured document after exploring approaches, summarizing the selected design to ensure alignment with user expectations and project requirements before implementation.

Does this brainstorming approach support incremental validation of user expectations?

Yes, this brainstorming approach supports incremental validation of user expectations by proposing concrete design approaches, capturing key decisions, and ensuring alignment throughout the requirements clarification and design decision-making process.