ck:brainstorm

Brainstorm architectural alternatives with trade-off and risk analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming for architectural decisions with brutal honesty to surface trade-offs early and guide teams toward optimal designs.

Core Features & Use Cases

  • Proactively surfaces 2-3 viable architectural alternatives with explicit trade-offs and risk analysis.
  • Guides decision-making through structured questions, constraints, and guardrails to avoid scope creep.
  • Produces concise design rationale and a plan for next steps to reach a decision quickly.

Quick Start

State the problem you want brainstormed and request 2-3 viable architectural options with 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 and risks for a new system design?

To evaluate architecture trade-offs, you must surface 2-3 viable alternatives and analyze risks across system design. This process enforces disciplined probing questions to produce concise design rationale and next steps to reach maintainable decisions quickly.

What is the best way to brainstorm architecture decisions and avoid scope creep?

The best way to brainstorm architecture decisions is using structured questions, constraints, and guardrails to avoid scope creep. Exploring multiple approaches with brutal honesty surfaces trade-offs early and guides teams toward optimal designs with a final recommendation.

Can I use this for design review and assessing system maintainability?

Yes, you can use this for design review and assessing system maintainability. It evaluates architectural alternatives by explicitly analyzing trade-offs and risks, ensuring your system design maintains high quality and guiding the team toward optimal decisions.

How do I compare viable architectural alternatives for my software project?

To compare viable architectural alternatives, you explore 2-3 options with explicit trade-off and risk analysis. This disciplined process enforces probing questions across system design, yielding a final design recommendation and a plan for next steps.

When do I need brutal honesty in architecture decision-making?

You need brutal honesty in architecture decision-making when you must surface trade-offs early and avoid scope creep. It guides teams toward optimal designs by evaluating risks and maintainability across multiple approaches with a structured, disciplined process.