brainstorming

Transform project ideas into detailed designs through iterative questioning and dialogue.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/matthewcdaigle/Pattern-Planner --skill brainstorming-matthewcdaigle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/matthewcdaigle/Pattern-Planner/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/matthewcdaigle/Pattern-Planner --skill brainstorming-matthewcdaigle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that every project starts with a well-thought-out design, reducing wasted effort and improving project outcomes.

Core Features & Use Cases

  • Explore Project Context: Analyze files and documentation to understand the project's current state.
  • Ask Clarifying Questions: Refine the project's intent, constraints, and success criteria.
  • Propose Approaches: Offer 2-3 design options with trade-offs and a recommendation.
  • Present Design: Communicate the design in sections, getting user approval before proceeding.
  • Document Design: Save the validated design in a structured document for future reference.

Quick Start

Start a new brainstorming session for your project 'new-features' by running the 'start-brainstorming' command.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I start the project design process for a new software feature?

Begin requirements gathering by analyzing existing project files and documentation to understand the current state, then answer clarifying questions to define your project's intent, constraints, and success criteria.

Can I use collaborative dialogue to refine project requirements before development?

Yes, collaborative dialogue refines project requirements by iteratively questioning constraints, proposing 2-3 design options with trade-offs, and securing user approval section by section before proceeding.

What is the best way to document a validated software design after brainstorming?

The best way to document a validated software design is to save it in a structured document after collaborative dialogue, ensuring the approved design is recorded for future reference and reducing wasted development effort.

Does this requirements gathering approach work for product design outside of software engineering?

Yes, this requirements gathering approach works for product design and other creative endeavors by guiding the transformation of ideas into detailed designs through iterative questioning and structured documentation.

How many design options should I expect during the collaborative design process?

During the collaborative design process, expect 2-3 proposed design options complete with trade-offs and a recommendation, allowing you to select the best approach before the design is presented for approval.