brainstorming

Name: brainstorming
Availability: InStock
Author: Jorge

Facilitate design specification through structured dialogue and design trade-offs.

Updated Feb 25, 2024

Search Tags:#design #brainstorming #ideation #product development #requirements gathering #user stories

Ready to run

npx skills add https://github.com/jorgeluis594/lorito-killer --skill brainstorming-jorgeluis594

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/jorgeluis594/lorito-killer/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/jorgeluis594/lorito-killer --skill brainstorming-jorgeluis594

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the initial stages of any project by ensuring that ideas are thoroughly explored, refined, and approved before any implementation work begins, preventing wasted effort on unvalidated concepts.

Core Features & Use Cases

Idea Exploration: Helps users articulate and refine project ideas through guided questioning.
Design Prototyping: Facilitates the creation of 2-3 distinct design approaches with trade-offs.
User Approval Workflow: Implements a structured process for presenting and gaining approval on design sections.
Use Case: Before building a new feature, use this Skill to explore the user's needs, define the technical approach, and get sign-off on the design, ensuring alignment and reducing scope creep.

Quick Start

Use the brainstorming skill to explore the project context and ask clarifying questions about the new feature request.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I gather requirements and explore design trade-offs for a new feature?▼

Requirements gathering and design trade-offs are explored through a structured dialogue that clarifies user intent and project context before implementation. This process helps articulate needs and validates technical approaches to prevent wasted effort on unvalidated concepts.

What is the best way to prevent scope creep when defining user stories for product development?▼

Preventing scope creep during product development involves using a structured user approval workflow to present and gain sign-off on design sections before implementation begins. This ensures alignment by thoroughly refining ideas and validating technical approaches.

How do I create distinct design approaches for behavioral changes in a component?▼

Creating distinct design approaches for behavioral changes involves facilitating design prototyping to generate 2-3 options with clear trade-offs. This structured exploration validates technical approaches against user needs and project context.

Do I need defined success criteria to start brainstorming a new feature request?▼

Yes, brainstorming a new feature request requires a clear definition of project context, user needs, and success criteria to effectively propose and validate design approaches. This input ensures the ideation phase explores relevant requirements and trade-offs.

When should I not use a structured design dialogue for ideation?▼

You should avoid structured design dialogues for ideation when a project lacks clear context or defined user needs, as the process requires explicit success criteria to validate approaches. Without these inputs, the structured approval workflow cannot effectively prevent scope creep.