bmad-v6/skills/cis/creative-intelligence/SKILL.md
Brainstorming and research automation specialist
npx skillsauth add aj-geddes/claude-code-bmad-skills Creative IntelligenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Role: Creative Intelligence System specialist
Function: Facilitate structured brainstorming, conduct research, generate creative solutions
Creative Intelligence workflows:
All workflows follow helpers.md patterns:
helpers.md#Combined-Config-Loadhelpers.md#Save-Output-Documenthelpers.md#Determine-Next-WorkflowYou work with:
Phase integration:
When activated:
helpers.md#Load-Project-ConfigAvailable techniques:
Technique selection:
Research types:
Market Research
Competitive Research
Technical Research
User Research
Research tools:
Brainstorming sessions produce:
Research produces:
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.
testing
Solutioning-phase UX planning skill (optional; activate when the project has a UI). Produces TWO planning documents: DESIGN.md (the visual system — design tokens, color palette, typography, spacing, component specs, WCAG 2.1 AA contract) and EXPERIENCE.md (user journeys, flow diagrams, screen states, error/empty/loading handling). Use when the user says "design the UX", "create UX planning docs", "define the design system", "map the user flows", "UX for this feature", "wireframe the flows", "what are the user journeys", "accessibility design", "WCAG compliance", "design tokens", "responsive design plan", "mobile-first design", or "create DESIGN.md / EXPERIENCE.md". Runs after architecture is drafted and before stories are created. Supports Create / Update / Validate intents.
testing
Quick Flow lightweight technical specification for small-scope work (1-15 stories). Replaces the full PRD + architecture pair when scope is small and requirements are clear. Produces bmad-output/tech-spec.md as the single planning artifact before story creation. Use when the user says: "write a tech spec", "create a technical specification", "I need a tech spec for this feature", "quick spec", "small project spec", "we don't need a full PRD", "just a tech spec", "spec out this change", "document this feature". QUICK FLOW TRACK ONLY (1-15 stories). If scope grows beyond ~15 stories or involves multiple teams / external integrations at scale, stop and redirect to bmad-prd + bmad-architecture instead — those skills are built for that complexity. Supports three intents: Create (new spec), Update (revise an existing tech-spec.md), Validate (review a draft for completeness against BMAD criteria).
tools
Orchestration handoff bridge: emits and maintains sprint-status.yaml as the project's sequencing system-of-record. Orders stories by epic then dependency, assigns parallel-set (wave) membership, and drives the status lifecycle (backlog → ready-for-dev → in-progress → review → done) as a view — never as a metric. Use when the user says "sequence the stories", "build the sprint status", "plan the waves", "create sprint-status.yaml", "assign parallel sets", "order stories by dependency", "what can run in parallel", "set up story sequencing", "initialize sprint tracking", "ready the backlog", or "prepare for dev handoff". Also triggers on "sprint planning" when the project already has epics defined. SCOPE: SEQUENCING AND ORCHESTRATION ONLY. No velocity, no burndown, no committed points, no coverage metrics. Capacity is expressed as wave width (concurrent story count), not points. The final artifact is a ready-for-dev handoff manifest; implementation is delegated to external dev tools.
development
Distills ANY messy input — brain dump, transcript, long PRD, stakeholder notes, feature request, voice memo — into a tight five-field SPEC.md kernel that any downstream planning skill can consume. The five fields are: Problem, Capabilities, Constraints, Non-Goals, Success Metrics. Use when the user says "create a spec", "write a spec for", "distill this into a spec", "I have a brain dump", "turn this into something structured", "clean up these notes", "make a SPEC from", "I want to define the problem", "help me scope this", "summarize what we're building", "I have a PRD but need a kernel", "what are we actually solving?", or drops raw text/transcript and asks for structure. Also use when starting any new initiative and a clean shared definition is missing.