brainstorming

Refine rough ideas into approved design documents through collaborative dialogue.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill brainstorming-sammy9322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/sammy9322/ventura-dental-facturacion/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill brainstorming-sammy9322

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates wasted development work caused by jumping into implementation without validating ideas, even for seemingly simple projects where unexamined assumptions often lead to costly rework.

Core Features & Use Cases

  • Iterative idea refinement: Ask clarifying questions one at a time to fully understand user intent, constraints, and success criteria.
  • Structured design workflow: Propose 2-3 approaches with trade-offs, present design sections for incremental approval, and generate formal spec documents.
  • Optional visual companion: Offer mockups, diagrams, and visual comparisons just-in-time for UI, architecture, or layout questions.
  • Use case: Perfect for planning new features, building components, adding functionality, or modifying behavior in any software project, from simple utilities to complex platforms.

Quick Start

Use the brainstorming skill to walk through refining your new feature idea and get an approved design document before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough feature ideas into approved spec documents before coding?

Structured brainstorming refines unstructured ideas into approved spec documents by asking clarifying questions, proposing approaches with trade-offs, and enforcing mandatory design approval gates before any implementation work begins.

What is the best way to plan software features without wasting development time?

Structured brainstorming prevents wasted development work by validating designs before implementation, proposing 2-3 approaches with trade-offs, and securing formal approval through iterative idea refinement sessions.

Can I get visual mockups and diagrams during the feature planning workflow?

Optional visual companion support provides mockups, diagrams, and visual comparisons just-in-time for UI, architecture, or layout questions during the brainstorming workflow to help validate design decisions.

Does this design workflow work for modifying behavior in existing software components?

The brainstorming workflow applies to modifying behavior in existing components, adding functionality, building new components, and creating features across any project scope or complexity level.

How do I write formal specifications for new software functionality additions?

Spec writing involves presenting design sections for incremental approval, refining ideas through clarifying questions, and generating the final spec document only after mandatory design approval gates are passed.

When should I not skip the design approval gate for simple utility projects?

Skipping the design approval gate is not recommended even for simple utility projects because unexamined assumptions often lead to costly rework, making mandatory validation essential across all project scopes.