ce:brainstorm

Coordinate brainstorming sessions to distill feature ideas into requirements documents.

6|Updated Jan 29, 2023

Search Tags:#workflow #planning #collaboration #requirements #brainstorm #product-management

Ready to run

npx skills add https://github.com/rethinkhealth/glion --skill ce-brainstorm-rethinkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce:brainstorm
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/ce-brainstorm
Command: npx skills add https://github.com/rethinkhealth/glion --skill ce-brainstorm-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill facilitates collaborative brainstorming to clarify scope, frame user problems, and produce a durable requirements document before planning implementation.

Core Features & Use Cases

Guided, iterative dialogue surfaces assumptions, constraints, and success criteria.
Outputs a lightweight requirements document suitable for planning and handoff.
Supports a structured exploration workflow with clear exit criteria and decisions.

Quick Start

Describe the feature idea or problem you want to brainstorm, and I will guide you through a focused brainstorming session to produce a concise requirements document.

Frequently Asked Questions about ce:brainstorm

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

FAQPage Schema

How do I turn a vague feature idea into a requirements document for planning?▼

To turn a vague feature idea into a requirements document, use guided collaborative brainstorming to clarify the problem frame, define success criteria, and establish scope boundaries through iterative dialogue. This process surfaces assumptions and constraints to produce a lightweight document ready for handoff.

What is the best way to facilitate collaborative brainstorming for product management?▼

Collaborative brainstorming for product management works best when applying a structured discussion flow that iteratively surfaces constraints and success criteria. This ensures the team aligns on scope boundaries and decisions before producing actionable next steps suitable for implementation planning.

Can I use structured brainstorming to define project scope and success criteria?▼

Yes, structured brainstorming clarifies project scope and success criteria by guiding teams through focused, interactive prompts. This method ensures all assumptions are surfaced and documented, resulting in clear scope boundaries and defined metrics for project success.

How does a structured discussion flow help distill feature requirements?▼

A structured discussion flow distills feature requirements by systematically exploring the problem frame and challenging assumptions through interactive prompts. This mechanism ensures no critical constraints or decisions are missed, directly translating vague ideas into durable planning artifacts.

What should I prepare before starting a collaborative brainstorming session for requirements?▼

Before starting collaborative brainstorming for requirements, prepare a basic feature idea or user problem description. This initial input serves as the starting point for the guided dialogue to iteratively extract assumptions, clarify scope boundaries, and define actionable next steps.

Are there limitations to using lightweight requirements documents for complex planning?▼

Lightweight requirements documents are designed for clear handoff and planning but may lack deep technical specifications for highly complex implementations. They focus on capturing problem frames, success criteria, and immediate next steps, requiring further detailed design work for intricate technical dependencies.