brainstorming

Guide software design through structured dialogue and user approval.

Updated Dec 4, 2025

Search Tags:#design #planning #brainstorming #product development #requirements gathering #user approval

Ready to run

npx skills add https://github.com/mjmmattoni98/recipe-hub --skill brainstorming-mjmmattoni98

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all creative work, from feature development to bug fixes, begins with a thorough design and user approval process, preventing wasted effort on unvetted ideas.

Core Features & Use Cases

Structured Design Process: Guides users through exploring project context, asking clarifying questions, proposing approaches, and presenting designs incrementally.
Mandatory Design Approval: Enforces a hard gate, requiring explicit user approval of the design before any implementation can begin.
Use Case: Before adding a new user authentication flow, you would use this Skill to define the user journey, security considerations, and technical architecture, ensuring all stakeholders agree before writing a single line of code.

Quick Start

Use the brainstorming skill to design the new 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 structure software design and requirements gathering before coding?▼

Structured software design involves exploring project context, asking clarifying questions, and proposing approaches incrementally. This ensures requirements gathering captures user intent and technical constraints before transitioning to implementation planning.

Why do I need explicit user approval before starting feature development?▼

Mandatory user approval acts as a hard gate to prevent wasted effort on unvetted ideas. Validating the design before implementation ensures stakeholders agree on technical architecture and user journey details.

What is the best way to explore design trade-offs for a new software component?▼

The best way to explore design trade-offs is through collaborative dialogue that systematically questions project context. This process evaluates technical architecture options and documents validated approaches incrementally.

Can I use a structured design process for modifying existing functionality and bug fixes?▼

Yes, a structured design process applies to modifying existing functionality and bug fixes. It enforces thorough design exploration and user approval, ensuring technical changes are vetted before implementation begins.

How do I transition from design planning to implementation planning safely?▼

Transitioning to implementation planning requires explicit user approval of all documented designs. This hard gate validates that design trade-offs and user intent are fully resolved before coding starts.

What are the limitations of starting software development without a design phase?▼

Starting without a design phase risks wasted effort on unvetted ideas. Bypassing requirements gathering and collaborative dialogue often leads to unresolved technical architecture issues and misaligned user intent.