ce-brainstorm

Facilitate collaborative dialogue to clarify requirements and produce a requirements document.

Updated Apr 26, 2026

Search Tags:#planning #documentation #collaboration #requirements #scope #brainstorm

Ready to run

npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-brainstorm-diestok

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-brainstorm
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-brainstorm-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams clarify problems, explore multiple solution paths, and define a balanced scope before committing to a plan or implementation. It promotes collaborative dialogue to surface assumptions, align on goals, and produce a durable requirements artifact.

Core Features & Use Cases

Structured dialogue: Facilitates collaborative exploration to articulate the problem, user needs, and success criteria before planning.
Artifact-first guidance: Guides toward a durable requirements document and a clear planning handoff, avoiding premature design decisions.
Flexible trigger patterns: Activates when users say phrases like "let's brainstorm" or describe vague or ambitious feature requests, prompting option-rich dialogue.

Quick Start

State the feature idea or problem to explore to trigger the brainstorming workflow.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema

How do I clarify requirements before planning a vague or ambitious feature?▼

To clarify requirements before planning, use collaborative brainstorming to facilitate structured dialogue that surfaces assumptions, aligns on goals, and produces a durable requirements document for implementation handoff.

What is the best way to define project scope through collaborative brainstorming?▼

Defining project scope through collaborative brainstorming involves exploring multiple solution paths and articulating user needs and success criteria, resulting in a balanced scope and artifact-first guidance before committing to a plan.

How do I explore solution options before deciding what to build?▼

Explore solution options before deciding what to build by triggering a brainstorming workflow with your feature idea, which prompts option-rich dialogue to think through alternatives and defer premature design decisions.

Can I use brainstorming dialogue to produce a requirements document for my team?▼

Yes, you can use brainstorming dialogue to produce a requirements document, as the process enforces a frontmatter-driven metadata contract and outputs durable decisions alongside planning guidance for your team.

When should I not use collaborative brainstorming for requirements gathering?▼

You should not use collaborative brainstorming when implementation specifics are already defined, as the process deliberately defers implementation details to the planning phase and focuses solely on scope and requirements gathering.

Does the brainstorming workflow require any specific dependencies or components to run?▼

No, the brainstorming workflow requires no specific dependencies or components to run, allowing you to start immediately by stating the feature idea or problem to explore to trigger the session.