Flesh out an idea through collaborative brainstorming, then gather project-specific details.
Flesh out an idea through collaborative brainstorming, then gather project-specific details.
/plugin marketplace add jeremyodell/claude-assistant/plugin install ideate@claude-assistant-marketplaceFlesh out an idea through collaborative brainstorming, then gather project-specific details.
$IDEA: The idea to brainstorm (required)SLUG=$(echo "$IDEA" | tr '[:upper:]' '[:lower:]' | sed 's/ /-/g' | sed 's/[^a-z0-9-]//g' | cut -c1-50)
DATE=$(date +%Y-%m-%d)
FEATURE_DIR="docs/features/${DATE}-${SLUG}"
mkdir -p "$FEATURE_DIR"
Save $FEATURE_DIR for subsequent phases.
Invoke the superpowers:brainstorming skill with the user's idea.
Let it run its full interactive Q&A process.
When brainstorming completes, capture the design output.
Write the brainstorm output to $FEATURE_DIR/design.md:
# Design: $IDEA
**Date:** $DATE
**Original idea:** $IDEA
## Design
[Captured output from superpowers:brainstorming]
Question 1: UI Components
Ask: "Does this feature have UI components?"
If Yes:
frontend-designer plugin is available❌ ERROR: frontend-designer plugin required for UI features.
Install with: /install frontend-designer
Workflow halted.
frontend-designer plugin$FEATURE_DIR/ui/If No: Continue to next question
Question 2: Linear configuration
Load config from .claude/ideate.local.md
If config exists: Ask: "Upload to $TEAM / $PROJECT? [Y/n or specify different]"
If no config:
Run /ideate:setup first, then continue.
Store confirmed team/project for upload phase.
✅ Brainstorm Complete
Design saved to: $FEATURE_DIR/design.md
UI artifacts: [Yes/No]
Target: $TEAM / $PROJECT
Next: Run /ideate:pressure-test to validate the design.
If $FEATURE_DIR/design.md already exists:
Ask: "design.md already exists. Overwrite? [y/N]"
| Error | Action |
|---|---|
| superpowers plugin missing | Error with install instructions, halt |
| frontend-designer missing (UI needed) | Error with install instructions, halt |
| User abandons | Partial artifacts saved for resume |
/brainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
/brainstormUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes