skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

ce:brainstorm

Guide teams to produce a concise requirements document with scope and success criteria.

Updated Sep 16, 2025
Search Tags:#planning#brainstorming#collaboration#requirements#decision-making#product-management#problem-framing
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-brainstorm-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:brainstorm
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/ce-brainstorm
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-brainstorm-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to clarify ambiguous requirements and align on scope before committing to a detailed plan by guiding structured, collaborative dialogue.

Core Features & Use Cases

  • Structured dialogue to surface assumptions, constraints, and alternatives.
  • Durable artifact in the form of a concise requirements brief that can feed planning and execution.
  • Use cases include when users request brainstorming, when requirements are vague or ambitious, or when deciding what to build next.

Quick Start

Describe a feature idea or problem to explore, and I will guide a structured brainstorm to produce a durable requirements brief.

Frequently Asked Questions about ce:brainstorm

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

FAQPage Schema
How do I clarify ambiguous requirements before committing to a detailed plan?▼

To clarify ambiguous requirements, you can use structured brainstorming to surface assumptions, constraints, and alternatives. This approach guides collaborative dialogue to align your team on scope before committing to execution.

What is the best way to frame product problems and decide on feature scope?▼

The best way to frame product problems is through structured dialogue that produces a durable requirements brief. This artifact includes a problem frame, concrete requirements, scope boundaries, success criteria, and recommended next steps.

How do I run a structured brainstorm to produce a durable requirements document?▼

Describe a feature idea or problem to explore, and the system will guide a structured brainstorm. It enforces a stable artifact with a problem frame, concrete requirements, scope boundaries, and success criteria.

Can I use structured brainstorming for vague or ambitious product requirements?▼

Yes, structured brainstorming is specifically designed for when requirements are vague or ambitious. It applies across product, design, and planning contexts to help teams decide what to build next.

Does structured brainstorming work for collaborative decision-making across product and design?▼

Structured brainstorming works effectively for collaborative decision-making across product and design contexts. It guides teams to align on feature scope by surfacing hidden assumptions and constraints.

What should a concise requirements brief include when deciding what to build next?▼

A concise requirements brief should include a problem frame, concrete requirements, scope boundaries, success criteria, and recommended next steps. This durable artifact feeds directly into planning and execution.

Related Skills

Explore More Product & Management Skills→
AratKruglikAratKruglik
150

brainstorming

Transform raw ideas into validated designs through structured dialogue.

Community
Advanced
duonghuan2122000duonghuan2122000
1

openspec-propose

Generate proposal.md, design.md, and tasks.md from a brief via OpenSpec CLI.

Community
Advanced
vibbsvibbs
6

prd-writer

Generate structured PRDs with problem statements, acceptance criteria, success metrics, and scope.

Community
Advanced
lv7devlv7dev

problem-solving

Route users to structured problem-solving sub-skills based on stuck-type.

Community
Basic