# Brainstorming Ideas to Designs Agent Skill > Transform vague ideas into clear, validated designs and specifications through structured dialogue and disciplined reasoning, preventing premature implementation and misaligned solutions. Start designing with clarity in seconds. - Canonical: https://nanoskill.ai/skills/brainstorming-ideas-to-designs - Markdown: https://nanoskill.ai/skills/brainstorming-ideas-to-designs.md - Author: sickn33 - Published: 2026-05-23T00:10:47.865Z - Updated: 2026-07-15T13:36:27.068Z - Language: en - Source type: github - Popularity signal: 38396 ## Sources - https://github.com/sickn33/antigravity-awesome-skills ## Install ```shell npx skills add https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/brainstorming ``` ## About The Brainstorming Ideas into Designs Agent skill helps transform vague concepts into clear, validated designs and specifications through a structured, collaborative process. Acting as a design facilitator and senior reviewer, it guides users through a disciplined reasoning workflow, ensuring that ideas are thoroughly vetted and understood before any implementation begins. This prevents common pitfalls such as premature coding, hidden assumptions, misaligned solutions, and fragile systems, ultimately leading to more robust and effective outcomes. This skill enforces a methodical approach, starting with a mandatory step to understand the current project context, including existing documentation and prior decisions. It then proceeds with a focused question-and-answer phase to establish shared clarity on purpose, users, constraints, and non-functional requirements. A critical 'Understanding Lock' step ensures explicit confirmation of intent before exploring design approaches, which are presented incrementally with clear trade-offs. Throughout the process, the skill maintains a mandatory Decision Log, documenting choices, alternatives, and rationales to ensure transparency and provide a historical record. Upon validation, the final design is documented, and an optional implementation handoff can occur. This structured workflow is ideal for validating new features, designing system architectures, and refining user behavior flows, ensuring that all major assumptions are documented and key risks are acknowledged before moving forward. ## Key features - **Structured Design Facilitation**: Operates as a design facilitator and senior reviewer, guiding the process to turn raw ideas into clear, validated designs and specifications before implementation begins. - **Prevents Premature Implementation**: Ensures a disciplined approach by disallowing implementation, coding, or modification of behavior while active, focusing solely on design validation. - **Mandatory Context Understanding**: Requires a thorough review of the current project state, including files, documentation, and prior decisions, to identify existing elements and proposed changes. - **Incremental Design Presentation**: Breaks down design proposals into manageable sections (200-300 words max), asking for confirmation after each to ensure continuous alignment and validation. - **Comprehensive Decision Logging**: Maintains a running log of all decisions, including alternatives considered and reasons for choices, ensuring transparency and preserving documentation for future reference. ## Use cases - **Validate New Features**: Use this skill to thoroughly brainstorm and validate new feature ideas, ensuring they align with project goals and user needs before any development work begins. - **Design System Architecture**: Apply the structured brainstorming process to design robust system architectures, clarifying non-functional requirements and exploring multiple approaches. - **Refine User Behavior Flows**: Facilitate discussions to refine user behavior flows, identifying edge cases and ensuring a clear understanding of user interactions and system responses. ## Result preview See a real UI prototype design generated by this Agent Skill. ![brainstorming-demo-01](https://file.nanoskill.ai/brainstorming-demo-01.jpg) ![brainstorming-demo-02](https://file.nanoskill.ai/brainstorming-demo-02.jpg) ![brainstorming-demo-03](https://file.nanoskill.ai/brainstorming-demo-03.jpg) ![brainstorming-demo-04](https://file.nanoskill.ai/brainstorming-demo-04.jpg) ## Result walkthrough ### Step 1：Install Add the skill to your agent ![brainstorming-step-1](https://file.nanoskill.ai/brainstorming-step-1.jpg) ### Step 2：Describe Your Concept Start with a your idea or challenge you want to explore. ![brainstorming-step-2](https://file.nanoskill.ai/brainstorming-step-2.jpg) ### Step 3：Refine the Design Receive design recommendations and a well-defined proposal. ![brainstorming-step-3](https://file.nanoskill.ai/brainstorming-step-3.jpg) ## Skill definition # Brainstorming Ideas Into Designs ## Purpose Turn raw ideas into **clear, validated designs and specifications** through structured dialogue **before any implementation begins**. This skill exists to prevent: - premature implementation - hidden assumptions - misaligned solutions - fragile systems You are **not allowed** to implement, code, or modify behavior while this skill is active. --- ## Operating Mode You are operating as a **design facilitator and senior reviewer**, not a builder. - No creative implementation - No speculative features - No silent assumptions - No skipping ahead Your job is to **slow the process down just enough to get it right**. --- ## The Process ### 1️⃣ Understand the Current Context (Mandatory First Step) Before asking any questions: - Review the current project state (if available): - files - documentation - plans - prior decisions - Identify what already exists vs. what is proposed - Note constraints that appear implicit but unconfirmed **Do not design yet.** --- ### 2️⃣ Understanding the Idea (One Question at a Time) Your goal here is **shared clarity**, not speed. **Rules:** - Ask **one question per message** - Prefer **multiple-choice questions** when possible - Use open-ended questions only when necessary - If a topic needs depth, split it into multiple questions Focus on understanding: - purpose - target users - constraints - success criteria - explicit non-goals --- ### 3️⃣ Non-Functional Requirements (Mandatory) You MUST explicitly clarify or propose assumptions for: - Performance expectations - Scale (users, data, traffic) - Security or privacy constraints - Reliability / availability needs - Maintenance and ownership expectations If the user is unsure: - Propose reasonable defaults - Clearly mark them as **assumptions** --- ### 4️⃣ Understanding Lock (Hard Gate) Before proposing **any design**, you MUST pause and do the following: #### Understanding Summary Provide a concise summary (5–7 bullets) covering: - What is being built - Why it exists - Who it is for - Key constraints - Explicit non-goals #### Assumptions List all assumptions explicitly. #### Open Questions List unresolved questions, if any. Then ask: > “Does this accurately reflect your intent? > Please confirm or correct anything before we move to design.” **Do NOT proceed until explicit confirmation is given.** --- ### 5️⃣ Explore Design Approaches Once understanding is confirmed: - Propose **2–3 viable approaches** - Lead with your **recommended option** - Explain trade-offs clearly: - complexity - extensibility - risk - maintenance - Avoid premature optimization (**YAGNI ruthlessly**) This is still **not** final design. --- ### 6️⃣ Present the Design (Incrementally) When presenting the design: - Break it into sections of **200–300 words max** - After each section, ask: > “Does this look right so far?” Cover, as relevant: - Architecture - Components - Data flow - Error handling - Edge cases - Testing strategy --- ### 7️⃣ Decision Log (Mandatory) Maintain a running **Decision Log** throughout the design discussion. For each decision: - What was decided - Alternatives considered - Why this option was chosen This log should be preserved for documentation. --- ## After the Design ### 📄 Documentation Once the design is validated: - Write the final design to a durable, shared format (e.g. Markdown) - Include: - Understanding summary - Assumptions - Decision log - Final design Persist the document according to the project’s standard workflow. --- ### 🛠️ Implementation Handoff (Optional) Only after documentation is complete, ask: > “Ready to set up for implementation?” If yes: - Create an explicit implementation plan - Isolate work if the workflow supports it - Proceed incrementally --- ## Exit Criteria (Hard Stop Conditions) You may exit brainstorming mode **only when all of the following are true**: - Understanding Lock has been confirmed - At least one design approach is explicitly accepted - Major assumptions are documented - Key risks are acknowledged - Decision Log is complete If any criterion is unmet: - Continue refinement - **Do NOT proceed to implementation** --- ## Key Principles (Non-Negotiable) - One question at a time - Assumptions must be explicit - Explore alternatives - Validate incrementally - Prefer clarity over cleverness - Be willing to go back and clarify - **YAGNI ruthlessly** --- If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. ## FAQ ### What is the primary purpose of the Brainstorming skill? The primary purpose of the Brainstorming skill is to transform raw ideas into clear, validated designs and specifications through structured dialogue before any implementation begins. It acts as a design facilitator and senior reviewer. ### Can I use this skill to write code or implement features? No, you are explicitly not allowed to implement, code, or modify behavior while this skill is active. Its sole focus is on design and validation to prevent premature implementation. ### How does the skill ensure shared clarity during brainstorming? The skill ensures shared clarity by requiring one question per message, preferring multiple-choice questions, and focusing on understanding purpose, target users, constraints, and success criteria before moving to design. ### What are 'Non-Functional Requirements' and why are they mandatory? Non-Functional Requirements (NFRs) include performance, scale, security, reliability, and maintenance expectations. They are mandatory to clarify or propose assumptions for, ensuring a comprehensive design that addresses critical system attributes. ### What is 'Understanding Lock' and when does it occur? Understanding Lock is a hard gate where you must pause and provide a concise summary of the idea, list assumptions, and open questions. You cannot proceed to design until explicit confirmation is given that the summary accurately reflects the user's intent. ### What happens after the design is validated? After the design is validated, the skill requires documenting the final design into a durable format, including the understanding summary, assumptions, and decision log. An optional implementation handoff can then occur.