brainstorming

Generates Socratic questions and tradeoff analyses to explore architectural decisions before implementation.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/JenilRevaliya/ARGUS --skill brainstorming-jenilrevaliya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/JenilRevaliya/ARGUS/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/JenilRevaliya/ARGUS --skill brainstorming-jenilrevaliya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding vague feature requests, leading to wrong architectural choices, scope creep, and costly rework. This Skill enforces a structured exploration phase that surfaces hidden assumptions and decision points before any code is written. ## Core Features & Use Cases - Socratic Questioning Protocol: Generates prioritized questions (blocking, high-leverage, nice-to-have) that reveal architectural consequences rather than just gathering data. - Tradeoff Analysis Tables: Compares 3+ distinct approaches across dimensions like cost, latency, complexity, and maintenance burden. - Lateral Expansion: Introduces edge cases and adjacent features users haven't considered, such as timezone handling or offline capability. - Use Case: When a user says "build an Instagram clone," the Skill produces decision questions on photo storage strategy, feed algorithms, and authentication methods with concrete tradeoff tables instead of premature boilerplate code. ## Quick Start Ask the assistant to brainstorm architectural options and tradeoffs for your new feature idea before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm software architecture before coding?▼

Use a Socratic questioning approach that identifies blocking decisions first, such as storage strategy, authentication method, and data model. Present 3 or more options per decision with tradeoff tables covering cost, complexity, and timeline before writing any code.

What questions should I ask before building a new feature?▼

Ask questions that reveal architectural consequences, not preferences. Focus on blocking decisions like payment provider choice, real-time versus polling, and single versus multi-tenant data models, each with explicit tradeoffs and a default recommendation.

How do I compare technical approaches with tradeoffs?▼

Build a comparison table with one row per approach and columns for speed to market, operational cost, latency, and maintenance burden. This forces implicit consequences into the open so stakeholders choose based on business reality rather than defaults.

When should brainstorming end and implementation begin?▼

Brainstorming ends when all blocking decisions are resolved and outputs are distilled into rigid assertions covering architecture, database, and third-party services. At that point the session transitions into plan-writing or implementation.

What are the limitations of AI-assisted brainstorming?▼

AI brainstorming can generate plausible options but cannot validate business assumptions, regulatory constraints, or team skill levels. Always verify recommended defaults against your actual scale requirements, budget, and compliance obligations before committing.