ck:brainstorm

Generate software solution options with trade-offs and feasibility feedback.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MinhQuyen274/smartify --skill ck-brainstorm-minhquyen274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:brainstorm
Source: https://github.com/MinhQuyen274/smartify/tree/main/Frontend_PROJECT_Figma/.opencode/skills/brainstorm
Command: npx skills add https://github.com/MinhQuyen274/smartify --skill ck-brainstorm-minhquyen274

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly converge on better software and product decisions by generating multiple solution options and stress-testing them with explicit trade-offs, risks, and feasibility constraints.

Core Features & Use Cases

  • Probing clarification: Uses interactive questioning to uncover real requirements, constraints, and success criteria before committing to an architecture.
  • Alternatives with trade-offs: Produces 2–3 viable approaches with pros/cons so you can compare design directions and make a grounded call.
  • Brutal feasibility checks: Challenges assumptions and flags unrealistic, over-engineered, or long-term risky ideas early.
  • Decision-to-document flow: Guides consensus, then summarizes the final recommended solution with rationale, implementation considerations, risks, and next steps.

Quick Start

Ask the assistant to brainstorm solutions for the problem: "Build a scalable frontend architecture for my Figma-to-frontend workflow, with clear trade-offs and a short recommended path."

Frequently Asked Questions about ck:brainstorm

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

FAQPage Schema
How do I brainstorm architecture design options with explicit trade-offs?▼

To brainstorm architecture design with trade-offs, the skill generates 2–3 viable solution options, stress-tests assumptions, and outputs a structured summary with pros, cons, risks, and next steps.

What is the best way to assess implementation risks under technical constraints?▼

Assessing implementation risks involves challenging assumptions and flagging unrealistic or over-engineered ideas early through an iterative question, research, analysis, and debate process.

Can I use this for feature planning and technical decision debates?▼

Yes, you can use it for feature planning and technical decision debates. It applies interactive questioning to uncover real requirements and success criteria before committing to a system design.

How do I validate assumptions during system design exploration?▼

Validate assumptions during system design by running an iterative question–research–analysis–debate process that checks feasibility and challenges long-term risky ideas under constraints.

When should I not use trade-off analysis for product engineering planning?▼

You should avoid using trade-off analysis for product engineering planning when you need a single immediate answer without exploring alternatives, as this process requires iterative probing and comparing multiple approaches.