brainstorming

Transforms vague ideas into validated designs and specifications through structured, incremental dialogue and disciplined reasoning.

11|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/mupengi-bot/mupengism --skill brainstorming-mupengi-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/mupengi-bot/mupengism/tree/main/skills/brainstorming
Command: npx skills add https://github.com/mupengi-bot/mupengism --skill brainstorming-mupengi-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of transforming vague ideas into clear, validated designs and specifications before any implementation begins, preventing premature implementation, hidden assumptions, and misaligned solutions.

Core Features & Use Cases

  • Structured Dialogue: Guides users through a disciplined, incremental reasoning process.
  • Understanding Lock: Ensures shared clarity on purpose, users, constraints, and success criteria before design.
  • Design Exploration: Proposes and evaluates multiple design approaches with clear trade-offs.
  • Incremental Design Presentation: Breaks down designs into manageable sections for validation.
  • Decision Logging: Maintains a running log of all design decisions.
  • Use Case: Before building a new feature, use this skill to define its exact requirements, explore different architectural options, and get explicit user confirmation on the design, ensuring alignment and reducing rework.

Quick Start

Use the brainstorming skill to help define the requirements for a new user authentication system.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I transform a vague product idea into a validated design?

To transform a vague idea into a validated design, use structured dialogue and disciplined reasoning to clarify context, define non-functional requirements, and explore design approaches before implementation. This prevents hidden assumptions and misaligned solutions.

What is the best way to define requirements for a new feature?

The best way to define requirements for a new feature is through an understanding lock process. This ensures shared clarity on purpose, users, constraints, and success criteria, preventing premature implementation and fragile systems.

How do I explore different architectural options before building a system?

To explore different architectural options, facilitate a design process that proposes and evaluates multiple design approaches with clear trade-offs. Presenting designs incrementally allows for explicit validation and maintains a running decision log.

Why does premature implementation lead to misaligned solutions?

Premature implementation leads to misaligned solutions because it bypasses the structured dialogue needed to surface hidden assumptions. Acting as a design facilitator and senior reviewer ensures requirements are validated and understood first.

When do I need a decision log for product development?

You need a decision log for product development when exploring design approaches and defining specifications. Maintaining a running log of all design decisions prevents misaligned solutions and ensures incremental design presentation is tracked.

Can I use structured dialogue to prevent fragile systems during design?

Yes, you can use structured dialogue to prevent fragile systems during design. By defining non-functional requirements and achieving an understanding lock, the design facilitation process validates specifications and eliminates hidden assumptions.