ce-brainstorm

Explores vague feature ideas into requirements-only unified plan documents through structured dialogue.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Aveer/skills --skill ce-brainstorm-aveer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/Aveer/skills/tree/main/skills/ce-brainstorm
Command: npx skills add https://github.com/Aveer/skills --skill ce-brainstorm-aveer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a vague or ambitious idea into a buildable specification is hard: scope is unclear, assumptions go untested, and planning agents end up inventing product behavior. This Skill runs a structured brainstorming dialogue that resolves product decisions up front and records them in a durable requirements-only unified plan under docs/plans/. ## Core Features & Use Cases - Scoped collaborative dialogue: Classifies work as Lightweight, Standard, or Deep, then asks one question at a time using the platform's blocking question tool to clarify problem, users, constraints, and success criteria. - Grounding and rigor passes: Scans the repository (with a cached repo profile and a grounding-scout subagent), pressure-tests the product framing, and offers blindspot maps or visual probes when the user faces unfamiliar or visual territory. - Requirements-only plan artifact: Writes a unified plan (markdown or HTML) with Goal Capsule, Product Contract, stable R-IDs, and metadata that ce-plan later enriches into an implementation plan. - Use Case: A user says "I'm mulling a canvas annotation feature but know nothing about the drawing code." The Skill maps the unfamiliar territory, probes scope and actors, then produces a requirements-only plan ready to hand off to ce-plan or an autonomous lfg pipeline. ## Quick Start Ask the AI to brainstorm your feature idea, for example: "Use ce-brainstorm to explore adding a highlighter tool to the editor."

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I brainstorm a feature idea before writing an implementation plan?▼

Invoke ce-brainstorm with a feature description; it classifies scope, asks clarifying questions one at a time, and writes a requirements-only unified plan under docs/plans/. That artifact is then handed to ce-plan, which adds the implementation detail.

What is a requirements-only unified plan in compound engineering?▼

It is a lightweight plan document with artifact_readiness: requirements-only containing a Goal Capsule and Product Contract with stable requirement IDs. It captures product behavior, scope boundaries, and success criteria so planning never invents them.

When should I not use brainstorming for a task?▼

Skip it for already-specified work such as direct implementation, debugging, or code review with no product scope left to decide. Verdict questions about adopting a named external technology route to ce-pov instead.

Can brainstorming produce HTML output instead of markdown?▼

Yes, pass output:html or set brainstorm_output in .compound-engineering/config.local.yaml. Output mode is exclusive per run, and pipeline invocations always force markdown so downstream automation can parse it.

What happens if I know nothing about the domain being scoped?▼

The Skill offers a blindspot pass that maps the decision surface of the unfamiliar territory: 3-7 decisions or hazards with realistic options and recommended defaults. You then choose which items to walk through; the rest become recorded assumptions.