ce-brainstorm

Facilitate collaborative brainstorming to produce a compact requirements document.

2|Updated Aug 20, 2024
One-click install
npx skills add https://github.com/theZMC/dotfiles --skill ce-brainstorm-thezmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/theZMC/dotfiles/tree/main/.agents/skills/ce-brainstorm
Command: npx skills add https://github.com/theZMC/dotfiles --skill ce-brainstorm-thezmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative teams often struggle to align on problem framing and scope before committing to a plan. This skill guides a structured dialogue to surface assumptions, constraints, and desired outcomes, producing a compact, durable requirements document that informs subsequent planning.

Core Features & Use Cases

  • Facilitated dialogue: prompts and frames questions to explore options, constraints, and success criteria.
  • Artifacts for planning: yields a concise requirements document and a clear handoff path to planning or execution.
  • Use Case: Use when a user requests brainstorming, describes vague or ambitious features, or wants to think through options before deciding what to build.

Quick Start

Start a collaborative brainstorm by describing the problem or feature idea and asking to produce a durable requirements document.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I brainstorm and shape vague feature ideas into clear product requirements?

Brainstorming vague feature ideas into clear product requirements involves facilitated dialogue to surface assumptions, constraints, and desired outcomes, producing a concise, durable requirements document for planning and execution.

What is the best way to align a collaborative team on problem framing before committing to a plan?

Aligning a collaborative team on problem framing requires structured questioning and decision points to explore options and success criteria, yielding a compact requirements document that informs subsequent planning.

How do I facilitate collaborative ideation to scope and clarify decisions for product management?

Collaborative ideation for product management uses a structured workflow that guides questioning and decision points to clarify problems and scope, generating a versioned requirements document ready for collaboration.

When do I need a structured brainstorming workflow for requirements gathering?

You need a structured brainstorming workflow for requirements gathering when a user describes ambitious features or wants to think through options before deciding what to build, ensuring outputs are repo-relative and ready for handoff.

Can I hand off brainstorming artifacts directly to planning and execution workflows?

You can hand off brainstorming artifacts directly to planning or execution workflows, as the generated requirements document provides a clear path and durable artifacts for subsequent planning stages.