brainstorming

Name: brainstorming
Availability: InStock
Author: discountedcookie

Guide iterative questioning to clarify design requirements and produce OpenSpec proposal summaries.

Updated Oct 26, 2025

Search Tags:#design #brainstorming #iteration #OpenSpec #design-exploration

Ready to run

npx skills add https://github.com/discountedcookie/10x-mapmaster --skill brainstorming-discountedcookie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/brainstorming
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill brainstorming-discountedcookie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides design exploration when a request is vague or complex, using iterative questioning to reach a design-ready OpenSpec proposal.

Core Features & Use Cases

One-question-at-a-time: Keeps prompts focused and avoids assumptions.
Iterative design: Presents 2-3 approaches with tradeoffs before selecting a path.
Design validation: Produces a Design Summary and next steps.

Quick Start

Initiate brainstorming for a complex feature, then validate the design step-by-step.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I clarify vague design requirements through structured questioning?▼

Iterative questioning guides you to clarify vague requirements by asking one focused question at a time, eliciting constraints and success criteria until the design intent is concrete. This process replaces ambiguous briefs with actionable specifications.

What's the best way to explore multiple design approaches before committing to one?▼

Design exploration presents 2-3 competing approaches with documented tradeoffs, letting you evaluate fit against project constraints before selecting a path. This validates decisions early and reduces rework.

How do I move from exploratory design to an OpenSpec proposal?▼

Iterative questioning and validation produce a Design Summary with next steps that translates into proposal-ready OpenSpec format, bridging early-stage exploration to formal specification.

When should I use one-question-at-a-time dialogue for design work?▼

Use this approach for early-stage product or system design when requirements are complex or vague. One-question-at-a-time keeps exploration focused, prevents assumption-driven design, and builds shared understanding incrementally.

Can I validate design decisions before implementation begins?▼

Design validation produces 200–300 word summaries that test each approach against project constraints and success criteria, surfacing fit issues or gaps before development starts.