ce-brainstorm

Guide collaborative brainstorming sessions to produce structured feature requirements documents.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill ce-brainstorm-santiagoisper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA/tree/main/.agents/skills/compound-engineering/ce-brainstorm
Command: npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill ce-brainstorm-santiagoisper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the need for a collaborative, structured approach to brainstorming and documenting requirements for feature development.

Core Features & Use Cases

  • Collaborative Dialogue: Encourages collaborative thinking through guided interaction rules and open-ended questions.
  • Feature Description: Facilitates the exploration and clarification of feature ideas or problems to be addressed.
  • Requirements Capture: Guides the creation of a comprehensive requirements document, including problem frame, key decisions, actors, flows, and more.
  • Approach Exploration: Offers guidance on exploring and evaluating multiple approaches to a feature, including risks and suitability.
  • Documentation: Outputs a structured requirements document in markdown or HTML format for easy sharing and reference.

Quick Start

Use the ce-brainstorm skill to start a new brainstorm session and explore a feature idea. For example, 'ce-brainstorm explore a feature to improve user experience on the website'.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I facilitate collaborative brainstorming for feature requirements definition?

Collaborative brainstorming for feature requirements definition is facilitated through structured dialogue, open-ended questions, and guided exploration of feature ideas to produce a comprehensive requirements document.

What is the best way to document feature requirements and key decisions during software development?

Documenting feature requirements and key decisions is best handled by capturing the problem frame, actors, and flows during a brainstorming session, which outputs a structured requirements document in markdown or HTML format.

How do I explore and evaluate multiple approaches to a feature during product management?

Exploring and evaluating multiple approaches to a feature during product management involves guided interaction to assess risks, suitability, and alternative paths before finalizing the requirements document.

Can I use structured dialogue to clarify feature ideas and problems to be addressed?

Structured dialogue can be used to clarify feature ideas and problems by encouraging collaborative thinking through guided interaction rules and open-ended questions throughout the brainstorming process.

Does collaborative brainstorming for requirements definition work for complex software development environments?

Collaborative brainstorming for requirements definition is intended for software development environments, supporting product management by structuring comprehensive requirement capture for complex feature development.