brainstorming
starsforks
How to install brainstorming?
nguyenphp/antigravity-marketing/brainstorming
$npx -y skills add nguyenphp/antigravity-marketing --skill brainstormingSocratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.
SKILL.md
| 1 | # Brainstorming & Communication Protocol |
| 2 | |
| 3 | > **MANDATORY:** Use for complex/vague requests, new features, updates. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## 🛑 SOCRATIC GATE (ENFORCEMENT) |
| 8 | |
| 9 | ### When to Trigger |
| 10 | |
| 11 | | Pattern | Action | |
| 12 | |---------|--------| |
| 13 | | "Build/Create/Make [thing]" without details | 🛑 ASK 3 questions | |
| 14 | | Complex feature or architecture | 🛑 Clarify before implementing | |
| 15 | | Update/change request | 🛑 Confirm scope | |
| 16 | | Vague requirements | 🛑 Ask purpose, users, constraints | |
| 17 | |
| 18 | ### 🚫 MANDATORY: 3 Questions Before Implementation |
| 19 | |
| 20 | 1. **STOP** - Do NOT start coding |
| 21 | 2. **ASK** - Minimum 3 questions: |
| 22 | - 🎯 Purpose: What problem are you solving? |
| 23 | - 👥 Users: Who will use this? |
| 24 | - 📦 Scope: Must-have vs nice-to-have? |
| 25 | 3. **WAIT** - Get response before proceeding |
| 26 | |
| 27 | --- |
| 28 | |
| 29 | ## 🧠 Dynamic Question Generation |
| 30 | |
| 31 | **⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles. |
| 32 | |
| 33 | ### Core Principles |
| 34 | |
| 35 | | Principle | Meaning | |
| 36 | |-----------|---------| |
| 37 | | **Questions Reveal Consequences** | Each question connects to an architectural decision | |
| 38 | | **Context Before Content** | Understand greenfield/feature/refactor/debug context first | |
| 39 | | **Minimum Viable Questions** | Each question must eliminate implementation paths | |
| 40 | | **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs | |
| 41 | |
| 42 | ### Question Generation Process |
| 43 | |
| 44 | ``` |
| 45 | 1. Parse request → Extract domain, features, scale indicators |
| 46 | 2. Identify decision points → Blocking vs. deferable |
| 47 | 3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have) |
| 48 | 4. Format with trade-offs → What, Why, Options, Default |
| 49 | ``` |
| 50 | |
| 51 | ### Question Format (MANDATORY) |
| 52 | |
| 53 | ```markdown |
| 54 | ### [PRIORITY] **[DECISION POINT]** |
| 55 | |
| 56 | **Question:** [Clear question] |
| 57 | |
| 58 | **Why This Matters:** |
| 59 | - [Architectural consequence] |
| 60 | - [Affects: cost/complexity/timeline/scale] |
| 61 | |
| 62 | **Options:** |
| 63 | | Option | Pros | Cons | Best For | |
| 64 | |--------|------|------|----------| |
| 65 | | A | [+] | [-] | [Use case] | |
| 66 | |
| 67 | **If Not Specified:** [Default + rationale] |
| 68 | ``` |
| 69 | |
| 70 | **For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md` |
| 71 | |
| 72 | --- |
| 73 | |
| 74 | ## Progress Reporting (PRINCIPLE-BASED) |
| 75 | |
| 76 | **PRINCIPLE:** Transparency builds trust. Status must be visible and actionable. |
| 77 | |
| 78 | ### Status Board Format |
| 79 | |
| 80 | | Agent | Status | Current Task | Progress | |
| 81 | |-------|--------|--------------|----------| |
| 82 | | [Agent Name] | ✅🔄⏳❌⚠️ | [Task description] | [% or count] | |
| 83 | |
| 84 | ### Status Icons |
| 85 | |
| 86 | | Icon | Meaning | Usage | |
| 87 | |------|---------|-------| |
| 88 | | ✅ | Completed | Task finished successfully | |
| 89 | | 🔄 | Running | Currently executing | |
| 90 | | ⏳ | Waiting | Blocked, waiting for dependency | |
| 91 | | ❌ | Error | Failed, needs attention | |
| 92 | | ⚠️ | Warning | Potential issue, not blocking | |
| 93 | |
| 94 | --- |
| 95 | |
| 96 | ## Error Handling (PRINCIPLE-BASED) |
| 97 | |
| 98 | **PRINCIPLE:** Errors are opportunities for clear communication. |
| 99 | |
| 100 | ### Error Response Pattern |
| 101 | |
| 102 | ``` |
| 103 | 1. Acknowledge the error |
| 104 | 2. Explain what happened (user-friendly) |
| 105 | 3. Offer specific solutions with trade-offs |
| 106 | 4. Ask user to choose or provide alternative |
| 107 | ``` |
| 108 | |
| 109 | ### Error Categories |
| 110 | |
| 111 | | Category | Response Strategy | |
| 112 | |----------|-------------------| |
| 113 | | **Port Conflict** | Offer alternative port or close existing | |
| 114 | | **Dependency Missing** | Auto-install or ask permission | |
| 115 | | **Build Failure** | Show specific error + suggested fix | |
| 116 | | **Unclear Error** | Ask for specifics: screenshot, console output | |
| 117 | |
| 118 | --- |
| 119 | |
| 120 | ## Completion Message (PRINCIPLE-BASED) |
| 121 | |
| 122 | **PRINCIPLE:** Celebrate success, guide next steps. |
| 123 | |
| 124 | ### Completion Structure |
| 125 | |
| 126 | ``` |
| 127 | 1. Success confirmation (celebrate briefly) |
| 128 | 2. Summary of what was done (concrete) |
| 129 | 3. How to verify/test (actionable) |
| 130 | 4. Next steps suggestion (proactive) |
| 131 | ``` |
| 132 | |
| 133 | --- |
| 134 | |
| 135 | ## Communication Principles |
| 136 | |
| 137 | | Principle | Implementation | |
| 138 | |-----------|----------------| |
| 139 | | **Concise** | No unnecessary details, get to point | |
| 140 | | **Visual** | Use emojis (✅🔄⏳❌) for quick scanning | |
| 141 | | **Specific** | "~2 minutes" not "wait a bit" | |
| 142 | | **Alternatives** | Offer multiple paths when stuck | |
| 143 | | **Proactive** | Suggest next step after completion | |
| 144 | |
| 145 | --- |
| 146 | |
| 147 | ## Anti-Patterns (AVOID) |
| 148 | |
| 149 | | Anti-Pattern | Why | |
| 150 | |--------------|-----| |
| 151 | | Jumping to solutions before understanding | Wastes time on wrong problem | |
| 152 | | Assuming requirements without asking | Creates wrong output | |
| 153 | | Over-engineering first version | Delays value delivery | |
| 154 | | Ignoring constraints | Creates unusable solutions | |
| 155 | | "I think" phrases | Uncertainty → Ask instead | |
| 156 | |
| 157 | --- |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
