Brainstorm Skill

Convert vague ideas into concrete design tasks with structured requirements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Brownbull/khujta_sphere --skill brainstorm-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Brainstorm Skill
Source: https://github.com/Brownbull/khujta_sphere/tree/main/skills/core/brainstorm
Command: npx skills add https://github.com/Brownbull/khujta_sphere --skill brainstorm-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill refines rough ideas and requirements into actionable designs through collaborative questioning and structured exploration, reducing planning time and misalignment.

Core Features & Use Cases

  • Socratic refinement: asks the right questions to clarify what to build and why.
  • Alternative exploration: generates multiple design approaches to avoid single-path risk.
  • Output-ready requirements: produces clear user stories, constraints, and risks.

Quick Start

Start a brainstorm session with: "Brainstorm a new feature to improve onboarding experience".

Frequently Asked Questions about Brainstorm Skill

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

FAQPage Schema
How do I turn vague requirements into concrete design tasks?

Brainstorming converts rough ideas into concrete designs by using Socratic questioning to clarify requirements, explore multiple design alternatives, and validate feasibility. The output includes refined requirements, user stories, technical constraints, and risk assessments ready for downstream planning.

What's the best way to explore design alternatives early in development?

Design thinking through structured brainstorming generates multiple approaches to avoid single-path risk. This technique surfaces user stories, constraints, and quality criteria across alternatives, helping teams validate feasibility and alignment before committing to implementation.

How do I reduce planning time and misalignment with stakeholders?

Collaborative brainstorming with cross-functional stakeholders clarifies what to build and why through structured questioning. It produces testable outputs—requirements, user stories, risks, and recommended approaches—that align teams and reduce rework downstream.

Can I use brainstorming to validate technical feasibility with my team?

Yes. Brainstorming engages cross-functional stakeholders to explore design alternatives and surface technical constraints and risks early. The structured output documents feasibility assessments and recommended approaches, enabling informed decisions before development begins.

What should I do before starting a brainstorm session?

Prepare a rough idea or initial requirement statement. Brainstorming refines vague concepts into actionable designs, so begin with a problem statement or feature concept you want to clarify and develop into concrete, testable tasks.

Why is Socratic questioning important in design planning?

Socratic questioning clarifies unstated assumptions and surfaces hidden requirements by asking structured questions rather than stating solutions. This reduces misalignment, uncovers edge cases, and ensures the team understands both what to build and the reasoning behind design choices.