product-brainstorming-with-team

Coordinate parallel expert agents to brainstorm feature ideas and tradeoffs.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/knguyen0125/claude-plugin --skill product-brainstorming-with-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-brainstorming-with-team
Source: https://github.com/knguyen0125/claude-plugin/tree/main/plugins/product/skills/product-brainstorm-with-team
Command: npx skills add https://github.com/knguyen0125/claude-plugin --skill product-brainstorming-with-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated, multi-perspective feature exploration that eliminates single-agent bias by dispatching parallel expert agents, preserving a shared set of meeting notes, and iterating through complexity-based discussion loops with human input at every decision point.

Core Features & Use Cases

  • Parallel expert perspectives (PM, Principal Engineer, Security, UI/UX, Platform, Researcher) to research feature ideas and tradeoffs.
  • Shared meeting notes repository (docs/epics/<feature>/meeting-notes.md) used as a single source of truth for all agents.
  • Complexity-driven iteration loops (LOW/3, MEDIUM/5, HIGH/7) with explicit human-in-the-loop at tensions, architecture, scope, and priorities.
  • Stepwise round-based decision points including clarifications, note creation, and PRD generation.

Quick Start

Spawn all expert agents for the feature and initialize the Round 1 meeting notes workflow.

Frequently Asked Questions about product-brainstorming-with-team

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

FAQPage Schema
How do I coordinate multi-perspective feature brainstorming across different product team roles?

Multi-perspective feature brainstorming is coordinated by dispatching parallel expert agents for PM, engineering, security, UI/UX, and go-to-market roles to research feature tradeoffs simultaneously. These agents share a centralized meeting-notes repository to ensure all viewpoints align before decisions are made.

What are shared meeting notes in product team workflows and why are they needed?

Shared meeting notes in product workflows act as a single source of truth for cross-functional teams. They are needed to preserve research, tradeoffs, and decisions from multiple expert agents, ensuring all design, engineering, and go-to-market perspectives reference the same centralized document throughout feature iteration.

How do I manage feature complexity and iteration loops during product decision-making?

Feature complexity and iteration loops are managed through predefined rounds (LOW/3, MEDIUM/5, HIGH/7) that trigger stepwise discussions. This framework enforces explicit human-in-the-loop decision points at architectural tensions, scope boundaries, and priorities to guide multi-perspective feature brainstorming.

Can I use multi-agent collaboration for generating a product requirements document?

Multi-agent collaboration can generate a product requirements document (PRD) by routing parallel expert perspectives through stepwise, round-based decision points. After initializing shared meeting notes and resolving feature complexities, the workflow automatically outputs a finalized PRD.

Does parallel expert brainstorming work for complex product features requiring diverse viewpoints?

Parallel expert brainstorming is specifically designed for complex product features requiring diverse viewpoints. It eliminates single-agent bias by automatically dispatching specialized agents across design, platform, and research domains, ensuring all feature tradeoffs are evaluated before human-in-the-loop prioritization.

When should I not use automated multi-agent workflows for feature research?

Automated multi-agent workflows should not be used for feature research when rapid, single-perspective output outweighs the need for multi-perspective tradeoff analysis, or when the product scope is too simple to justify the overhead of complexity-driven iteration loops and shared meeting notes.