ck:brainstorm

Identify and analyze multiple design options for complex software systems.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tonamson/please-done --skill ck-brainstorm-tonamson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:brainstorm
Source: https://github.com/tonamson/please-done/tree/main/ck/.opencode/skills/brainstorm
Command: npx skills add https://github.com/tonamson/please-done --skill ck-brainstorm-tonamson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate well-reasoned design alternatives with clarity about trade-offs, costs, and risks, reducing decision fatigue during architecture sessions.

Core Features & Use Cases

  • Provides structured exploration of multiple solution options with pros/cons
  • Facilitates risk assessment and stakeholder alignment
  • Useful for architecture reviews, technical decision records, and early planning

Quick Start

Propose two to three architectural approaches for a given system and select the best option after comparing trade-offs.

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 when choosing between multiple design options?

Evaluating architecture trade-offs involves comparing multiple design options by analyzing their specific risks, costs, and benefits to provide structured reasoning and reduce decision fatigue during complex system planning.

What is the best way to document design decisions for technical decision records?

Documenting design decisions requires presenting two to three viable architectural alternatives with documented rationale, brutally honest risk assessment, and clear pros and cons to ensure stakeholder alignment.

Can I use structured brainstorming for early planning and feasibility studies?

Structured brainstorming is applicable for early planning and feasibility studies, enabling teams to generate well-reasoned design alternatives and compare risks across different architectural approaches before committing to implementation.

How do I perform a brutally honest risk assessment for complex software architecture?

Performing brutally honest risk assessment for complex software architecture involves identifying potential failure points across proposed design options and transparently documenting these risks to align stakeholders on trade-offs.

When do I need to explore multiple solution options for a feature debate?

You need to explore multiple solution options for a feature debate when facing decision fatigue, requiring a structured comparison of costs and benefits to select the most viable architectural approach.