ck:brainstorm

Brainstorm architectures with trade-off analysis and explicit decision criteria.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-brainstorm-edgehunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:brainstorm
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-brainstorm-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams generate robust, well-reasoned solutions by analyzing trade-offs and exposing risks with brutal honesty.

Core Features & Use Cases

  • Question Everything to surface assumptions and clarify constraints.
  • Explore 2-3 viable approaches with pros/cons, risks, and trade-offs.
  • Facilitate design discussions and produce clear rationale and next steps.

Quick Start

State your objective and constraints, then ask clarifying questions to ensure aligned scope and success criteria.

Frequently Asked Questions about ck:brainstorm

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

FAQPage Schema
How do I evaluate architecture trade-offs during a technical design review?

Architecture trade-off analysis works by questioning everything to surface assumptions, clarifying constraints, and exploring 2-3 viable approaches with documented pros, cons, and risks to produce clear decision rationale.

What is the best way to facilitate a brainstorming session for software architecture decisions?

The best way to facilitate architecture brainstorming is to state your objective and constraints upfront, then ask clarifying questions to ensure aligned scope and success criteria before exploring viable approaches.

Can I use this for technical debates where ruthless evaluation and risk analysis are needed?

Yes, this approach is specifically designed for technical debates and ideation sessions where ruthless evaluation is needed, providing structured prompts and documented trade-offs to expose risks with brutal honesty.

How do I document design decisions and next steps after exploring multiple architecture solutions?

You document design decisions by exploring 2-3 viable approaches with pros, cons, and risks, then facilitating the design discussion to produce clear rationale and documented next steps for the team.

Why does my team struggle to reach consensus on architecture decisions during design reviews?

Teams struggle to reach consensus on architecture decisions when they lack explicit decision criteria and documented trade-offs, making it hard to evaluate options objectively and expose hidden risks during design reviews.

When do I need structured trade-off analysis for software architecture and collaboration?

You need structured trade-off analysis for architecture collaboration when you must generate robust, well-reasoned solutions by questioning assumptions, clarifying constraints, and evaluating multiple approaches with brutal honesty.