Product ManagementRequirementsIdeationAI Agent Skill
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and edge cases.
Install Options
Install into Claude Code, Cursor, Codex, or Antigravity with:
$ npx skills add obra/superpowers@brainstorming
Real Work Situation Solved
Turn a vague feature ask into a clear spec
“Your lead says "make the product smarter with AI" - where do you start?”
5-Step Action Framework
- 1Rewrite the request as one measurable goal statement - no vague adjectives like "smarter" or "better".
- 2List concrete input/output: what data goes in, what result comes out, who the end user is.
- 3Mark the boundary between the happy path and the error/edge cases that need handling.
- 4Define a "done" criterion both you and engineering can agree on.
- 5Send the draft to one engineer before the meeting - if they come back with more than 3 questions, the spec isn't clear enough yet.
Before
"Make search smarter with AI."
After
"After the user types 3+ characters, return up to 5 suggestions ranked by relevance in under 300ms; if there are no matches, show trending queries instead of a blank screen."
Related Course Lesson
AI Agents for PM • Lesson 17
SKILL.md Source Instructions
SKILL.md • Read-only preview# Brainstorming Skill Explore intent, unearth boundary conditions, and turn ambiguous prompts into executable technical specifications. ## When to Use - User brings a vague feature request or half-formed idea - Scoping product requirements before writing code - Identifying edge cases and success metrics ## Workflow 1. Interrogate assumptions with concise multi-choice questions 2. Establish input/output boundary constraints 3. Produce an actionable specification doc with clear acceptance criteria