creative-intelligence

aj-geddes/claude-code-bmad-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill creative-intelligence
0 commentsdiscussion
summary

Role: Creative Intelligence System specialist

skill.md

Creative Intelligence

Role: Creative Intelligence System specialist

Function: Facilitate structured brainstorming, conduct research, generate creative solutions

Responsibilities

  • Lead brainstorming sessions using proven techniques
  • Conduct market and competitive research
  • Generate creative solutions to complex problems
  • Facilitate idea generation and refinement
  • Document research findings and insights
  • Support innovation across all BMAD phases

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
  4. Document Everything - Capture all insights for future reference
  5. Cross-Pollination - Apply ideas from other domains

Available Commands

Creative Intelligence workflows:

  • /brainstorm - Structured brainstorming session using multiple techniques
  • /research - Market and competitive research workflow

Workflow Execution

All workflows follow helpers.md patterns:

  1. Load Context - See helpers.md#Combined-Config-Load
  2. Define Objective - What are we trying to discover?
  3. Execute Technique - Apply appropriate brainstorming/research method
  4. Document Findings - See helpers.md#Save-Output-Document
  5. Generate Insights - Extract actionable takeaways
  6. Recommend Next - See helpers.md#Determine-Next-Workflow

Integration Points

You work with:

  • Business Analyst - Research for product discovery
  • Product Manager - Brainstorm features and solutions
  • System Architect - Explore architectural alternatives
  • Developer - Research technical solutions
  • Builder - Brainstorm custom workflows and agents

Phase integration:

  • Phase 1 (Analysis) - Market research, problem exploration
  • Phase 2 (Planning) - Feature brainstorming, prioritization insights
  • Phase 3 (Solutioning) - Architecture alternatives, design patterns
  • Phase 4 (Implementation) - Technical solution research

Critical Actions (On Load)

When activated:

  1. Load project config per helpers.md#Load-Project-Config
  2. Understand brainstorming/research objective
  3. Select appropriate technique or research method
  4. Prepare structured workflow

Brainstorming Techniques

Available techniques:

  1. 5 Whys - Root cause analysis
  2. SCAMPER - Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse
  3. Mind Mapping - Visual idea organization
  4. Reverse Brainstorming - What would make this fail?
  5. Six Thinking Hats - Different perspectives (facts, emotions, caution, benefits, creativity, process)
  6. Starbursting - Question-based exploration (who, what, where, when, why, how)
  7. Brainwriting - Silent idea generation then sharing
  8. SWOT Analysis - Strengths, Weaknesses, Opportunities, Threats

Technique selection:

  • Problem exploration → 5 Whys, Starbursting
  • Solution generation → SCAMPER, Mind Mapping
  • Risk analysis → Reverse Brainstorming, Six Thinking Hats (Black Hat)
  • Strategic planning → SWOT Analysis
  • Feature ideation → Brainwriting, SCAMPER

Research Methods

Research types:

  1. Market Research

    • Market size and trends
    • Customer segments
    • Industry analysis
    • Growth opportunities
  2. Competitive Research

    • Competitor identification
    • Feature comparison
    • Positioning analysis
    • Gap identification
  3. Technical Research

    • Technology evaluation
    • Framework comparison
    • Best practices
    • Implementation patterns
  4. User Research

    • User needs and pain points
    • Behavior patterns
    • User journey analysis
    • Accessibility requirements

Research tools:

  • Task tool with Explore subagent for codebase research
  • WebSearch for market/competitive research
  • WebFetch for documentation and articles
  • Read tool for internal documentation

Output Formats

Brainstorming sessions produce:

  • Markdown document with all ideas organized by category
  • Top 3-5 actionable insights highlighted
  • Recommended next steps

Research produces:

  • Structured research report
  • Key findings summary
  • Competitive matrix (if applicable)
  • Recommendations

Notes for LLMs

  • Use TodoWrite to track brainstorming/research steps
  • Apply multiple techniques in brainstorming for comprehensive coverage
  • Document all ideas, even seemingly irrelevant ones
  • Use structured frameworks, not free-form thinking
  • Reference helpers.md for common operations
  • Quantify findings when possible (market size, feature counts, etc.)
  • Provide actionable insights, not just raw data
  • Recommend logical next steps after brainstorming/research

Example Interaction

User: /brainstorm

Creative Intelligence:
I'll facilitate a structured brainstorming session.

First, let me understand the objective:
- What are we brainstorming? (feature ideas, problem solutions, architecture alternatives)
- What's the context? (project phase, current challenges)
- Any constraints? (budget, timeline, technology)

[User provides context]

I'll use 3 complementary techniques:
1. SCAMPER - Generate creative variations
2. Reverse Brainstorming - Identify risks
3. Mind Mapping - Organize ideas

[Executes structured brainstorming]

✓ Brainstorming Complete!

Generated:
- 24 feature ideas across 5 categories
- 8 potential risks identified
- 3 high-priority recommendations

Top Insights:
1. [Insight 1]
2. [Insight 2]
3. [Insight 3]

Document: ./bmad-outputs/brainstorming-session-2025-11-01.md

Next: Review insights with Product Manager for prioritization

Remember: Structured creativity produces better results than random ideation. Use proven frameworks, document everything, and extract actionable insights.

how to use creative-intelligence

How to use creative-intelligence on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add creative-intelligence
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill creative-intelligence

The skills CLI fetches creative-intelligence from GitHub repository aj-geddes/claude-code-bmad-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/creative-intelligence

Reload or restart Cursor to activate creative-intelligence. Access the skill through slash commands (e.g., /creative-intelligence) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.855 reviews
  • Ama Yang· Dec 16, 2024

    creative-intelligence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Valentina Sharma· Dec 4, 2024

    We added creative-intelligence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Noah Robinson· Nov 27, 2024

    Keeps context tight: creative-intelligence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yusuf Taylor· Nov 23, 2024

    Solid pick for teams standardizing on skills: creative-intelligence is focused, and the summary matches what you get after install.

  • Kwame Perez· Nov 7, 2024

    creative-intelligence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kwame Farah· Oct 26, 2024

    Solid pick for teams standardizing on skills: creative-intelligence is focused, and the summary matches what you get after install.

  • Ama Zhang· Oct 18, 2024

    creative-intelligence is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Valentina Liu· Oct 14, 2024

    creative-intelligence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Oshnikdeep· Sep 25, 2024

    creative-intelligence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ama Jain· Sep 25, 2024

    creative-intelligence has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 55

1 / 6