brainstorming

Translate user requirements into actionable design options with trade-offs.

1|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/The-Interdependency/a0 --skill brainstorming-the-interdependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/The-Interdependency/a0/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/The-Interdependency/a0 --skill brainstorming-the-interdependency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming and design clarification before implementation to ensure alignment between user intent, requirements, and final design.

Core Features & Use Cases

  • Structured inquiry: guides discovery of goals, constraints, and success criteria.
  • Multi-approach design: proposes 2-3 viable options with trade-offs and recommendations.
  • Design documentation: outputs a design doc and supports the spec-review loop and handoff to implementation.

Quick Start

Ask the user for project context, constraints, and success metrics, then present 2-3 design approaches and seek approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I translate vague product ideas into actionable design options?

To translate ideas into actionable design options, structured brainstorming gathers project context, constraints, and success metrics to propose 2-3 viable design approaches with clear trade-offs and recommendations for implementation planning.

What is the best way to document design requirements before implementation?

The best way to document design requirements is using structured design facilitation that clarifies goals and success criteria, then outputs a comprehensive design doc to support the spec-review loop and handoff to implementation.

How do I clarify project constraints and success criteria for a new feature?

To clarify project constraints and success criteria for a new feature, structured inquiry guides the discovery process by asking targeted questions about your project context, ensuring alignment between user intent and final design.

Can I get multiple design approaches with trade-offs for my product requirements?

Yes, you can get multiple design approaches with trade-offs for your product requirements through multi-approach ideation, which proposes 2-3 viable design options with distinct trade-offs and recommendations tailored to your constraints.

When do I need structured brainstorming for design documentation?

You need structured brainstorming for design documentation when clarifying goals, constraints, and success criteria across product features, ensuring your user intent and requirements align with the final design before implementation begins.

Does this brainstorming process support handoff to implementation planning?

Yes, the brainstorming process supports handoff to implementation planning by outputting a detailed design doc that captures the structured context, chosen design options, and success criteria for the spec-review loop.