brainstorming

Convert ideas into structured design proposals with question-driven workflows.

3|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/JoaquinCampo/codex-skills --skill brainstorming-joaquincampo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/JoaquinCampo/codex-skills/tree/main/brainstorming
Command: npx skills add https://github.com/JoaquinCampo/codex-skills --skill brainstorming-joaquincampo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming Ideas Into Designs converts vague ideas into concrete design directions by guiding a structured, questions-first dialogue that uncovers intent, constraints, and success criteria before implementation.

Core Features & Use Cases

  • Structured inquiry: Start from project context, ask one clarifying question at a time to refine goals.
  • Design exploration: Propose 2-3 alternative approaches with trade-offs, then recommend a preferred path.
  • Incremental validation: Deliver design content in short sections (200-300 words), pausing for each check before continuing.
  • Documentation ready: Generate a concise design plan suitable for documentation and handoff.
  • Implementation readied: Provide a step-by-step plan for moving from design to implementation if requested.

Quick Start

Provide a clear project brief and success criteria to begin. Then ask the AI to draft the initial design in 200-300 word sections, presenting 2-3 approaches with trade-offs, and prompting you to validate after each section.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I convert vague product ideas into structured design proposals?

To convert vague ideas into structured design proposals, use a question-driven workflow that clarifies intent and constraints, then proposes 2-3 alternative design approaches with trade-offs. This method ensures early-stage product definition is validated before implementation.

What is the best way to explore design alternatives during early-stage product definition?

Exploring design alternatives during product definition involves generating 2-3 approaches with clear trade-offs, delivering the design in 200-300 word incremental sections, and pausing for validation to ensure the recommended path aligns with project goals.

How do I clarify project requirements before starting the design process?

Clarify project requirements before starting the design process by engaging in a structured inquiry that asks one clarifying question at a time. This interactive dialogue uncovers intent, constraints, and success criteria to refine goals.

Can I generate documentation-ready design plans through an interactive brainstorming process?

Yes, you can generate documentation-ready design plans through an interactive brainstorming process. By validating design content delivered in short 200-300 word chunks, the process produces a concise design plan suitable for handoff and step-by-step implementation.

Does this structured design exploration work for product management use cases?

Yes, this structured design exploration works for product management use cases. It specifically supports early-stage product definition by helping a PM refine goals through one-question-at-a-time clarification and incremental validation of proposed design directions.

What are the limitations of using incremental validation for design brainstorming?

A limitation of incremental validation for design brainstorming is that delivering content in 200-300 word sections requires frequent pauses for user approval. This structured inquiry process may slow down rapid iteration if the initial project brief and success criteria are not clearly defined.