ce:brainstorm

Guides collaborative brainstorming sessions to document feature requirements.

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

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 requirements and approaches, helping users think through feature ideas and plan implementation.

Core Features & Use Cases

  • Collaborative Dialogue: Engage in a structured dialogue to refine and clarify feature ideas.
  • Requirement Documentation: Generate a requirements document for planning and execution.
  • Scope Assessment: Classify the scope of the work to determine the appropriate level of detail for the requirements document.

Quick Start

Start a brainstorm session by initiating a ce:brainstorm conversation and providing a feature idea or problem to explore.

Frequently Asked Questions about ce:brainstorm

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

FAQPage Schema
How do I brainstorm feature ideas and document requirements collaboratively?

To brainstorm feature ideas collaboratively, you initiate a structured dialogue session to explore the problem space, assess project scope, and automatically generate detailed requirement documentation for product planning and execution.

What is the best way to structure a product planning session for new features?

The best way to structure product planning for new features is through guided collaborative dialogue that refines initial concepts, classifies the scope of work, and translates the discussion into a formal requirements document.

Can I use collaborative brainstorming to assess project scope before writing requirements?

Yes, you can use collaborative brainstorming to assess project scope by engaging in structured dialogue that classifies the required work, which then determines the appropriate level of detail needed for your final requirements documentation.

Does requirement documentation work for both engineering and product management teams?

Requirement documentation from these brainstorming sessions is explicitly designed for both product management and engineering teams, ensuring feature ideation and implementation planning are aligned through collaborative scope assessment.

When should I not use a collaborative dialogue for feature ideation?

You should avoid using collaborative dialogue for feature ideation when your project lacks a clear problem to explore or when the scope is already rigidly defined, as the process focuses on refining ideas through open discussion and scope assessment.