ce-brainstorm

Guide collaborative brainstorming to clarify requirements and plan implementation.

Updated Sep 25, 2024
One-click install
npx skills add https://github.com/kwam1na/athena --skill ce-brainstorm-kwam1na
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/ce-brainstorm
Command: npx skills add https://github.com/kwam1na/athena --skill ce-brainstorm-kwam1na

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Facilitates collaborative brainstorming to clarify requirements and plan implementation before drafting a concise requirements document.

Core Features & Use Cases

  • Collaborative dialogue: Guides stakeholders through iterative discussion to surface options, constraints, and trade-offs.
  • Probing and assumption surfacing: Elicits evidence, specificity, and unstated assumptions to sharpen scope.
  • Synthesis to lightweight PRD: Produces a concise synthesis and a minimal requirements document that anchors planning.
  • When to use: Use for feature ideas, vague or ambitious requests, or when the user says "let's brainstorm" or asks what should we build.

Quick Start

Outline your feature idea briefly and start answering clarifying questions to refine scope and decisions.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I brainstorm and clarify requirements for a vague feature request?

Brainstorming vague feature requests requires collaborative dialogue to surface assumptions and constraints. This skill guides stakeholders through targeted questions to sharpen scope, producing a lightweight requirements document with problem frames and acceptance criteria to anchor planning.

What is the best way to align project scope during product discovery?

Aligning project scope during product discovery involves iterative discussion to surface trade-offs and options. This skill facilitates collaborative brainstorming, eliciting evidence and specificity to shape clear scope boundaries and output a concise synthesis for planning.

How do I create a lightweight PRD from an ambitious product idea?

Creating a lightweight PRD from ambitious ideas requires probing to surface unstated assumptions. This skill guides conversations through clarifying questions, outputting a minimal requirements document with scope boundaries, decisions, and acceptance criteria.

Can I use collaborative brainstorming to plan implementation workflows?

Collaborative brainstorming can plan implementation workflows by clarifying requirements before drafting documentation. This skill guides stakeholders through iterative discussion, surfacing constraints and trade-offs to produce a concise requirements synthesis anchoring workflows.

When should I use a structured brainstorming session for product management?

Structured brainstorming for product management is needed when users describe vague or ambitious feature requests or say 'let's brainstorm.' This skill guides collaborative dialogue to surface assumptions and shape clear scope, producing a lightweight requirements document.

What limitations exist when facilitating requirements discovery for complex features?

Requirements discovery for complex features relies on stakeholder input to surface constraints and trade-offs. This skill facilitates collaborative dialogue and probing, but cannot generate scope boundaries or acceptance criteria without active participant engagement.