Skip to main content

Ce Brainstorm

Skill Verified Active

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

Purpose

To help users clearly define and document feature requirements through interactive dialogue, ensuring a solid foundation for subsequent planning and development.

Features

  • Collaborative requirements exploration via dialogue
  • Generation of right-sized requirements documents
  • Guidance on defining scope, success criteria, and approaches
  • Structured interaction rules for effective communication

Use Cases

  • Brainstorming vague or ambitious feature requests
  • Clarifying scope and direction for new initiatives
  • Documenting product decisions before detailed planning
  • Thinking through complex problems or improvements

Non-Goals

  • Implementing code or executing plans
  • Creating detailed technical specifications
  • Providing solutions without user input or clarification

Installation

First, add the marketplace

/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering@compound-engineering-plugin

Quality Score

Verified
100 /100
Analyzed 1 day ago

Trust Signals

Last commit1 day ago
Stars16.7k
LicenseMIT
Status
View Source

Similar Extensions

Deep Dive

99

2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection

Skill
Yeachan-Heo

PRD: Product Requirements Document

98

Write product requirements documents at variable depth: one-pager, brief, full PRD, or RFC. Auto-detects depth from context. Reads existing research and context if available. Triggers on: "write a PRD", "product spec", "one-pager", "RFC", "requirements doc", "spec for", "brief for".

Skill
mshadmanrahman

Agent Teams

100

Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.

Skill
rohitg00

Team Lead Persona

100

Lead a team — run standups, coordinate tasks, and communicate.

Skill
googleworkspace

Teach Guidance

100

Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.

Skill
pjt222

Prepare Inspection Readiness

100

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

Skill
pjt222

© 2025 SkillRepo · Find the right skill, skip the noise.