ce:brainstorm

Clarify ambiguous feature ideas through structured dialogue and capture requirements.

Updated Nov 11, 2023

Search Tags:#planning #collaboration #requirements #scope #brainstorm #product-strategy #feature-ideation

Ready to run

npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-brainstorm-michaelvolz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce:brainstorm
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-brainstorm
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-brainstorm-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns vague feature asks or undecided problems into a shared understanding of what should be built, preventing planning from inventing product scope, behavior, or success metrics after the fact.

Core Features & Use Cases

Guided discovery: Ask one focused question at a time, prefer single-select choices, and surface relevant repo context before locking down the idea.
Product pressure test: Challenge the framing, weigh outcomes, and note opportunities to reframe, simplify, or defer work before committing to a requirement.
Durable documentation: Produce a lightweight requirements doc with the problem frame, concrete requirements, scope boundaries, and success criteria so planning can focus on implementation.

Quick Start

Describe the feature, problem, or improvement you want to explore so I can guide the brainstorming session and capture the requirements.

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 for a vague feature idea before starting product planning?▼

You clarify requirements for ambiguous feature ideas through structured, single-question collaborative dialogue that surfaces relevant context, tests the problem frame, and captures concrete constraints before planning begins.

What is the best way to brainstorm product scope without inventing requirements during planning?▼

Brainstorming product scope before planning involves challenging the initial framing, weighing outcomes, and documenting scope boundaries and success criteria in a lightweight requirements document to prevent planning from inventing product behavior.

How do I structure a collaborative brainstorming session to define feature scope?▼

Structure a collaborative brainstorming session by asking one focused question at a time, preferring single-select choices to guide discovery, and noting opportunities to simplify or defer work before committing to a requirement.

Can I use this approach to reframe ambition and decide what should be built first?▼

Yes, you can apply this approach when exploring options or reframing ambition, as it pressure-tests the problem framing and produces a durable requirements document with success criteria to decide what should be built.

What should be included in a requirements document to prepare for feature planning?▼

A requirements document for feature planning should include the problem frame, concrete requirements, scope boundaries, and success criteria so that downstream planning can focus strictly on implementation.

When should I not use structured brainstorming for feature ideation?▼

You should avoid structured brainstorming for feature ideation when the requirements are already concrete and unambiguous, as the guided discovery process is specifically designed to resolve vagueness and undecided problems before planning.