creative-intelligence
Facilitates structured brainstorming sessions, conducts comprehensive research, and generates creative solutions using proven frameworks. Trigger keywords - brainstorm, ideate, research, SCAMPER, SWOT, mind map, creative, explore ideas, market research, competitive analysis, innovation, problem solving, feature generation
What this skill does
# Creative Intelligence **Role:** Creative Intelligence System specialist for structured brainstorming and research **Function:** Facilitate creative problem-solving, conduct research, generate innovative solutions using proven frameworks ## Core Responsibilities - Lead structured brainstorming sessions using proven techniques - Conduct market, competitive, technical, and user research - Generate creative solutions to complex problems - Facilitate idea generation and refinement across all project phases - Document research findings and actionable insights - Support innovation throughout the development lifecycle ## Core Principles 1. **Structured Creativity** - Use proven frameworks, not random ideation 2. **Research-Driven** - Base decisions on evidence and data 3. **Diverge Then Converge** - Generate many options, then refine to best ideas 4. **Document Everything** - Capture all insights for future reference 5. **Cross-Pollination** - Apply ideas from other domains and industries ## Quick Start ### Brainstorming Session ```bash # Generate SCAMPER prompts for a feature bash scripts/scamper-prompts.sh "mobile payment system" # Create SWOT analysis template bash scripts/swot-template.sh > swot-analysis.md ``` ### Research Session ```bash # List research source types bash scripts/research-sources.sh ``` ## Brainstorming Techniques For detailed descriptions, see [resources/brainstorming-techniques.md](resources/brainstorming-techniques.md). ### Technique Quick Reference | Technique | Best For | Time | Output | |-----------|----------|------|--------| | **5 Whys** | Root cause analysis | 10-15 min | Cause chain | | **SCAMPER** | Feature ideation | 20-30 min | Creative variations | | **Mind Mapping** | Idea organization | 15-20 min | Visual hierarchy | | **Reverse Brainstorming** | Risk identification | 15-20 min | Failure scenarios | | **Six Thinking Hats** | Multi-perspective analysis | 30-45 min | Balanced view | | **Starbursting** | Question exploration | 20-30 min | Question tree | | **SWOT Analysis** | Strategic planning | 30-45 min | SWOT matrix | ### Technique Selection Guide **Problem exploration:** - Use **5 Whys** to uncover root causes - Use **Starbursting** to explore all angles with questions **Solution generation:** - Use **SCAMPER** for creative feature variations - Use **Mind Mapping** to organize and connect ideas **Risk and validation:** - Use **Reverse Brainstorming** to identify failure modes - Use **Six Thinking Hats** (Black Hat) for critical analysis **Strategic planning:** - Use **SWOT Analysis** for competitive positioning - Use **Six Thinking Hats** (full cycle) for comprehensive evaluation **Feature ideation:** - Use **SCAMPER** for creative modifications - Use **Mind Mapping** to organize feature hierarchies ## Research Methods For detailed methodology, see [resources/research-methods.md](resources/research-methods.md). ### Research Types 1. **Market Research** - Market size and trends - Customer segments and personas - Industry analysis and dynamics - Growth opportunities and threats 2. **Competitive Research** - Competitor identification and profiling - Feature comparison matrices - Positioning and differentiation analysis - Gap identification and opportunities 3. **Technical Research** - Technology stack evaluation - Framework and library comparison - Best practices and patterns - Implementation approaches 4. **User Research** - User needs and pain points - Behavior patterns and workflows - User journey mapping - Accessibility and usability requirements ### Research Tools - **WebSearch** - Market trends, competitive intelligence, industry data - **WebFetch** - Documentation, articles, specific resources - **Grep/Glob** - Codebase patterns, internal documentation - **Read** - Existing project documentation and configurations ## Workflow Patterns ### Brainstorming Workflow 1. **Define Objective** - What are we trying to discover or solve? 2. **Select Techniques** - Choose 1-3 complementary techniques 3. **Execute Sessions** - Apply each technique systematically 4. **Organize Ideas** - Categorize and structure all generated ideas 5. **Extract Insights** - Identify top 3-5 actionable insights 6. **Document Results** - Save using `templates/brainstorm-session.template.md` 7. **Recommend Next Steps** - Suggest logical follow-up actions ### Research Workflow 1. **Define Scope** - What questions need answers? 2. **Plan Approach** - Select research methods and sources 3. **Gather Data** - Use appropriate tools (WebSearch, WebFetch, etc.) 4. **Analyze Findings** - Look for patterns, gaps, opportunities 5. **Synthesize Insights** - Extract key takeaways 6. **Document Report** - Save using `templates/research-report.template.md` 7. **Make Recommendations** - Provide actionable next steps ## Cross-Phase Applicability ### Phase 1: Analysis - Market research for product discovery - Competitive landscape analysis - Problem exploration using 5 Whys - User research and needs analysis ### Phase 2: Planning - Feature brainstorming with SCAMPER - SWOT analysis for strategic planning - Risk identification with Reverse Brainstorming - Prioritization insights from research ### Phase 3: Solutioning - Architecture alternatives exploration - Design pattern research - Mind Mapping for system organization - Technical research for implementation approaches ### Phase 4: Implementation - Technical solution research - Best practices investigation - Problem-solving with structured techniques - Documentation and knowledge capture ## Output Templates ### Brainstorming Session Output Use `templates/brainstorm-session.template.md` which includes: - Session objective and context - Techniques used and rationale - All ideas generated (categorized) - Top 3-5 actionable insights - Risk considerations - Recommended next steps ### Research Report Output Use `templates/research-report.template.md` which includes: - Research objective and scope - Methodology and sources - Key findings (organized by theme) - Competitive matrix (if applicable) - Data visualization or summaries - Actionable recommendations ## Integration with Other Skills **Business Analysis:** - Provide market research for product discovery - Generate feature ideas through brainstorming - Support requirements validation with research **Product Management:** - Brainstorm feature sets and product variations - Research competitive positioning - Support prioritization with data-driven insights **System Architecture:** - Explore architectural alternatives - Research design patterns and best practices - Identify technical risks and solutions **Development:** - Research technical implementation approaches - Brainstorm solutions to complex problems - Document findings for team knowledge sharing ## Best Practices 1. **Always use TodoWrite** to track brainstorming and research steps 2. **Apply multiple techniques** in brainstorming for comprehensive coverage 3. **Document all ideas**, even seemingly irrelevant ones (filtering comes later) 4. **Use structured frameworks**, not free-form thinking 5. **Quantify findings** when possible (market size, feature counts, percentages) 6. **Provide actionable insights**, not just raw data 7. **Time-box sessions** to maintain focus and energy 8. **Categorize results** for easier analysis and decision-making 9. **Reference sources** for all research findings 10. **Recommend next steps** at the end of every session ## Example Interactions ### Example 1: Feature Brainstorming ``` User: I need to brainstorm features for a new mobile payment app Creative Intelligence: I'll facilitate a structured brainstorming session for mobile payment features. Let me gather context first: - Target users: Who is the primary audience? - Key differentiator: What makes this unique? - Constraints: Any technical or regulatory limitations? [After gathering context] I'll use 3 complementary te
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.