skills.rest
dthuy62
dthuy62COMMUNITY
Explore all skills by this author →
GitHub

ck:brainstorm

Evaluate software ideas and design options to clarify decisions.

Updated May 10, 2026
Search Tags:#architecture#feasibility#brainstorm#system-design#tradeoffs#technical-decision
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-brainstorm-dthuy62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:brainstorm
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/brainstorm
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-brainstorm-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn ambiguous software ideas into clear, well-reasoned decisions by exploring constraints, risks, and trade-offs before anyone starts building.

Core Features & Use Cases

  • Architecture Decisions: Compare multiple system designs and identify the most maintainable path.
  • Feasibility Analysis: Pressure-test ideas for scope, effort, and hidden risks.
  • Technical Debate Support: Challenge assumptions, surface trade-offs, and align stakeholders around a defensible direction.
  • Use Case: A team wants to add chat, billing, and analytics to an app, and this Skill helps break the problem into sane sub-projects and pick a realistic build order.

Quick Start

Ask this skill to brainstorm the best approach for your software problem and explain the trade-offs in plain language.

Frequently Asked Questions about ck:brainstorm

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

FAQPage Schema
How do I evaluate software architecture trade-offs before implementation?▼

To compare system design options, analyze trade-offs across maintainability, constraints, and risks for each architecture. This process turns vague problems into clear, defensible decisions before implementation begins.

What is the best way to pressure-test software feasibility and scope?▼

Software feasibility analysis pressure-tests ideas by evaluating scope, effort, and hidden risks against project constraints. It validates whether a proposed feature is realistic before committing engineering resources to build it.

How do I break down a large feature addition into realistic build phases?▼

Breaking down feature additions involves analyzing cross-functional constraints, dependencies, and risks to sequence sub-projects logically. This method aligns stakeholders around a defensible build order and realistic implementation plan.

Can I use brainstorming techniques for technical debate support and stakeholder alignment?▼

Brainstorming techniques support technical debates by challenging assumptions and surfacing trade-offs in plain language. This aligns cross-functional product and engineering teams around a single, defensible technical direction.

When should I avoid jumping straight into implementation for complex system designs?▼

Avoid jumping straight into implementation when architecture decisions involve hidden risks or unresolved constraints. Performing honest risk assessment and alternative comparison first prevents costly rework and misaligned stakeholder expectations.

Related Skills

Explore More Software Engineering Skills→
bankielewiczbankielewicz

discovering-requirements

Guide phased elicitation of software requirements from business ideas.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

speckit-plan

Generate structured implementation plans from spec.md files using spec-kit workflows.

Community
Intermediate
ApothecaryManApothecaryMan

problem-analyzer

Analyze technical problems through database inspection and visual diagramming.

Community
Advanced
mafvietnammafvietnam

ck:brainstorm

Brainstorm architectural alternatives with trade-off and risk analysis.

Community
Advanced