brainstorm-ideas-new
This Claude Code skill generates feature ideas for new products by soliciting input from product management, design, and engineering perspectives during early-stage discovery. Use it when beginning product validation for a startup, exploring initial features for a new product concept, or conducting initial brainstorming sessions with cross-functional teams before development begins.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/brainstorm-ideas-new && cp -r /tmp/brainstorm-ideas-new/pm-product-discovery/skills/brainstorm-ideas-new ~/.claude/skills/brainstorm-ideas-newSKILL.md
## Brainstorm Product Ideas (New Product) Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints. ### Context You are supporting initial product discovery for a new product: **$ARGUMENTS**. If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed. ### Domain Context **Initial Discovery vs Continuous Discovery**: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for **initial discovery**. ### Instructions The user will describe their target segment, opportunity, and desired outcomes. Work through these steps: 1. **Understand the opportunity**: Confirm the product concept, target market segment, and what the users want to achieve. 2. **Ideate from three perspectives** — generate 5 specific feature ideas each from: - **Product Manager**: Focus on market fit, value creation, and competitive advantage - **Product Designer**: Focus on user experience, onboarding, and engagement - **Software Engineer**: Focus on technical innovation, API integrations, and platform capabilities 3. **Prioritize the top 5 ideas** across all perspectives. For a new product, weight heavily toward: - Core value delivery (does it solve the primary problem?) - Speed to validate (can we test this quickly?) - Differentiation potential 4. **For each prioritized idea**, provide reasoning and key assumptions to test. Think step by step. Save substantial output as a markdown document. --- ### Further Reading - [Startup Canvas: Product Strategy and a Business Model for a New Product](https://www.productcompass.pm/p/startup-canvas) - [Product Innovation Masterclass](https://www.productcompass.pm/p/product-innovation-masterclass) (video course) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.