brainstorming

Transform user ideas into detailed design specifications through guided questioning.

5|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill brainstorming-faisalalqarni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/FaisalAlqarni/sp-ecc/tree/main/skills/brainstorming
Command: npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill brainstorming-faisalalqarni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users transform vague ideas into concrete, actionable designs and specifications by guiding them through a structured questioning and validation process.

Core Features & Use Cases

  • Intent Clarification: Asks targeted questions to understand user needs, constraints, and success criteria.
  • Approach Exploration: Proposes and discusses multiple design approaches with their trade-offs.
  • Design Presentation: Delivers designs in digestible sections for incremental validation.
  • Use Case: Before starting a new feature, use this Skill to ensure everyone agrees on the purpose, scope, and technical approach, preventing costly rework later.

Quick Start

Use the brainstorming skill to explore the idea of adding a user profile page.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a vague product idea into a concrete design specification?

To transform a vague idea into a design specification, engage in a guided dialogue that clarifies user intent, explores design approaches, and validates requirements incrementally. This structured process ensures the final specification is actionable and documented.

What is the best way to brainstorm requirements before starting feature development?

The best way to brainstorm requirements is to use a structured, question-based dialogue that explores user needs and discusses multiple design approaches with their trade-offs. This prevents costly rework by ensuring scope and technical approach are agreed upon beforehand.

Can I explore multiple design approaches and their trade-offs during product planning?

Yes, you can explore multiple design approaches during product planning by proposing and discussing each option's trade-offs. This allows you to evaluate different technical directions and select the most suitable design before implementation begins.

How do I document design specifications incrementally to avoid scope creep?

Document design specifications incrementally by delivering designs in digestible sections for validation and adhering to YAGNI principles. This step-by-step validation ensures only necessary features are specified, preventing scope creep and unnecessary complexity.

Does the brainstorming process require any specific tools or dependencies?

No specific tools or dependencies are required for the brainstorming process. It operates independently to facilitate your creative work through a guided dialogue focused on exploring intent, requirements, and design options.