brainstorming
Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.
Security Assessment
About brainstorming
The brainstorming skill transforms vague ideas into validated designs through disciplined reasoning and structured collaboration. It exists to prevent premature implementation, hidden assumptions, misaligned solutions, and fragile systems by enforcing a mandatory design phase before any code is written. This skill operates as a design facilitator that slows down the process just enough to ensure correctness and alignment.
The skill follows a seven-step process: understanding current context, clarifying the idea through focused questions, establishing non-functional requirements, locking understanding with explicit confirmation, exploring design approaches with trade-off analysis, presenting designs incrementally for validation, and maintaining a decision log throughout. Each step includes hard gates that prevent advancement until clarity is achieved. The skill emphasizes asking one question at a time, preferring multiple-choice formats, and ruthlessly applying YAGNI principles to avoid over-engineering.
This skill is designed for software architects, technical leads, product managers, and development teams working on new features, system architecture, or behavioral changes. It ensures shared understanding between stakeholders before implementation begins, reduces rework from misaligned assumptions, and creates durable documentation that captures design rationale. The skill is particularly valuable for complex projects, cross-functional initiatives, or situations where requirements are initially ambiguous.
FAQ
When should I use the brainstorming skill?
Use this skill before any creative or constructive work such as designing new features, planning system architecture, or defining application behavior. It should be activated whenever you need to transform vague ideas into validated designs before implementation begins.
Can I write code while this skill is active?
No. The brainstorming skill explicitly prohibits implementation, coding, or modifying behavior while active. Its purpose is to facilitate design and planning only. Code implementation happens after the design is validated and documented.
What happens at the Understanding Lock stage?
The Understanding Lock is a mandatory hard gate where progress stops until explicit confirmation is received. A summary of what is being built, why, for whom, key constraints, and non-goals is presented along with all assumptions and open questions. You cannot proceed to design until the user confirms this understanding is accurate.
What non-functional requirements must be clarified?
The skill requires explicit clarification of performance expectations, scale considerations (users, data, traffic), security or privacy constraints, reliability and availability needs, and maintenance ownership expectations. If the user is unsure, reasonable defaults can be proposed but must be clearly marked as assumptions.
What documentation is produced at the end?
The skill produces a durable design document in a shared format (such as Markdown) that includes the understanding summary, all assumptions, a decision log capturing what was decided and why, and the final validated design. This document is persisted according to the project's standard workflow.
Install brainstorming
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
sickn33/antigravity-awesome-skills