domains / families / software-engineering / brainstorming

brainstorming

combined

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

When to use

• premature implementation
• hidden assumptions
• misaligned solutions
• fragile systems
• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies overlap on the core idea of exploring intent before building, but they disagree on the procedure and contain material steps the others lack. obra/superpowers is a conversational discovery skill that explicitly allows skipping questions, uses open-ended questions, and includes visual mockups and spikes. foryourhealth111-pixel and LeoYeAI are near-identical procedural skills that require a hard gate, a fixed checklist, a design doc at a specific path, and a handoff to writing-plans. sickn33 adds mandatory non-functional requirements, an understanding lock, and a decision log. Crowning one would hide real alternatives.