product-brainstorm
/product-brainstorm — Requirements Exploration
Guided dialogue to explore what to build before committing to specs. Helps clarify fuzzy ideas into concrete, actionable requirements.
When to Use
- User says "brainstorm", "explore this idea", "help me think through"
- Requirements are fuzzy or incomplete
- Multiple approaches seem viable and need evaluation
- Before writing a PRD or tech spec
Process
Step 1: Understand the Problem
If $ARGUMENTS provides a topic, use it as the starting point. Otherwise, ask probing questions to understand the core need:
- What problem are you solving? (not what feature — the underlying problem)
- Who is this for? (specific user type, not "everyone")
- What does success look like? (measurable outcome)
More from elliottrjacobs/bench-skills
product-prd
Write product requirements documents from feature ideas or brainstorm output. Use when the user says "write a PRD", "product requirements", "feature spec", or needs to formalize a product concept into a structured document.
17product-tech-spec
Write technical specifications bridging product requirements and implementation. Use when the user says "tech spec", "technical spec", "architecture doc", "system design", or after writing a PRD and before planning implementation.
11product-naming
Expert naming process for products, companies, and features based on David Placek's methodology. Use when the user says "name this", "brainstorm names", "naming process", or needs to find a name for a product, feature, company, or project.
10knowledge-compound
Document solutions, decisions, and learnings into a searchable knowledge base. Use when the user says "document this", "compound this", "save this solution", "capture this", or after completing significant work that uncovered reusable knowledge.
8security-audit
Deep security audit of codebase with parallel domain-focused agents. Use when the user says "security audit", "check for vulnerabilities", "security review", or before a launch/deployment. More thorough than the security reviewer in /engineer-review.
8engineer-review
Comprehensive multi-agent code review with parallel specialist reviewers. Use when the user says "review this", "code review", "review my PR", provides a PR number or branch, or after completing a /engineer-work cycle.
8