ce-brainstorm

Facilitate collaborative brainstorming sessions and document software development requirements.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-brainstorm-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-brainstorm
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-brainstorm-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates collaborative brainstorming sessions to explore and document requirements for software development projects. It helps users think through ideas, identify scope, and document decisions before moving to planning or execution.

Core Features & Use Cases

  • Collaborative Dialogue: Engage in structured dialogue to explore ideas and requirements.
  • Requirement Documentation: Generate a concise requirements document capturing decisions made during the brainstorming session.
  • Scope Assessment: Classify the scope of the project as lightweight, standard, or deep, and guide the user accordingly.
  • Facilitation Principles: Follow universal brainstorming facilitation principles to guide the conversation and ensure a productive outcome.
  • Output Guidance: Provide guidelines on how to structure the requirements document for readability and portability.

Quick Start

Use the ce-brainstorm skill to explore the requirements for a new feature in your project. Start by describing the problem you want to solve or the feature you want to build.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I document software requirements through collaborative brainstorming?

You can document software requirements through collaborative brainstorming by engaging in structured dialogue that explores ideas, classifies project scope, and captures decisions in a concise, portable requirements document for future planning.

What is the best way to facilitate a brainstorming session for software development scope assessment?

Facilitating a brainstorming session for software development scope assessment involves classifying the project as lightweight, standard, or deep, then applying universal facilitation principles to guide structured dialogue and capture decisions for future planning.

Can I use structured dialogue to define requirements for lightweight software projects?

Yes, you can use structured dialogue to define requirements for lightweight software projects, as the process supports lightweight, standard, and deep scope classifications, guiding the conversation to ensure a productive outcome and capturing decisions made during the session.

How do brainstorming facilitation principles help explore software development ideas?

Brainstorming facilitation principles help explore software development ideas by guiding structured dialogue, ensuring productive outcomes, and generating a concise requirements document that captures decisions for future execution.

What format should the output requirements document take after a collaborative brainstorming session?

The output requirements document after a collaborative brainstorming session should follow guidelines for readability and portability, capturing decisions made during the session to support future planning or execution of the software development project.