brainstorming

Guide collaborative brainstorming sessions from context gathering to design framing.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Ramachandrajoshi/Azure-Devops-Copilot --skill brainstorming-ramachandrajoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Ramachandrajoshi/Azure-Devops-Copilot/tree/main/.roo/skills/brainstorming
Command: npx skills add https://github.com/Ramachandrajoshi/Azure-Devops-Copilot --skill brainstorming-ramachandrajoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chokidar, express, ws, and includes scripts (resource) components.

What problem does it solve?

Brainstorming sessions often lack structure, leading to missed requirements, ambiguous goals, and delayed design decisions. This Skill provides a guided, collaborative approach that surfaces user intent, captures constraints, and frames a clear design direction before implementation.

Core Features & Use Cases

  • Guided exploration of project context, goals, constraints, and success criteria to align all stakeholders.
  • Proposes 2-3 design approaches with clear trade-offs and recommended direction.
  • Generates a formal design plan and design doc, followed by a structured spec-review handoff to engineering.

Quick Start

Start a brainstorming session by asking clarifying questions to define goals, constraints, and acceptance criteria, then present design options for user approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I structure design requirements and brainstorming sessions for a new product feature?

Brainstorming sessions clarify user intent by gathering context on project goals, constraints, and success criteria. The process then proposes 2-3 design approaches with clear trade-offs to guide stakeholders toward a recommended direction.

What is the best way to turn early-stage product ideas into a formal design doc?

The best way to turn ideas into a design doc is through a structured brainstorming process that validates goals and constraints. This generates a formal design plan followed by a structured spec-review handoff to engineering.

Can I use this brainstorming skill for early-stage system design and requirements gathering?

Yes, this brainstorming skill fits early-stage system design and requirements gathering. It guides a collaborative session to validate goals, constraints, and success criteria before engineering implementation begins.

How does the spec-review handoff to engineering work after design framing?

The spec-review handoff works by generating a formal design plan and design doc, then initiating a structured review loop. This ensures the validated design framing guides the engineering implementation directly.

What are the limitations of using a design-first brainstorming process for ideation?

A limitation of this design-first brainstorming process is that it imposes structured steps and formal deliverables. It requires validating goals, constraints, and success criteria before proceeding to design framing.