product▌

You are a sharp product thinking partner — the kind of experienced PM or design lead who challenges assumptions, asks the hard questions, and pushes ideas further before anyone converges too early. You help product managers explore problem spaces, generate ideas, and stress-test thinking before it becomes a spec.

Turn the current conversation context into a PRD and submit it as a GitHub issue.

Professional product images with studio lighting, angles, and e-commerce conventions. \n \n Covers six shot types: hero shots, packshots (white background), lifestyle, scale reference, close-ups, and group compositions \n Includes camera angles (eye level, 3/4 view, overhead, low angle) and lighting setups (soft box, rim lighting, natural window, flat/even) \n Provides shadow and background guidance, composition rules (rule of thirds, negative space, triangle layouts), and category-specific conv

../../../product-team/agile-product-owner/SKILL.md

../../../product-team/product-manager-toolkit/SKILL.md

RICE prioritization, customer interview analysis, PRD templates, and discovery frameworks for product strategy. \n \n Includes automated RICE scoring with portfolio balance analysis, quarterly capacity planning, and roadmap generation from feature datasets \n NLP-based interview analyzer extracts pain points, feature requests, jobs-to-be-done patterns, sentiment, and key themes from transcripts \n Provides four PRD templates (standard, one-page, agile epic, feature brief) plus discovery framewor

Guides product launch execution—channels, timeline, checklist, and cross-functional coordination. Use this skill when planning the launch of a new product or major feature. For GTM strategy (PLG/SLG/MLG, 90-day framework, ICP, new market entry, repositioning), see gtm-strategy. For cold start (first users, no product yet), see cold-start-strategy.

Comprehensive requirements and planning specialist for PRDs, tech specs, feature prioritization, and epic breakdown. \n \n Creates Product Requirements Documents (PRDs) for complex projects and lightweight Technical Specifications for simpler ones, with structured functional and non-functional requirements \n Prioritizes features using MoSCoW, RICE scoring, and Kano frameworks; includes validation scripts and templates to ensure requirements are testable, measurable, and traceable \n Breaks down

Help teams articulate compelling long-term product visions grounded in user outcomes, not features or taglines. \n \n Provides frameworks from 101 product leaders (Notion, Airbnb, New York Times) covering four criteria for strong vision: lofty yet realistic, free of current technical constraints, and grounded in a potent user problem \n Guides users to describe the user's future world in 5–10 years rather than product features, with emphasis on emotional outcomes and behavioral change \n Include

A product vision answers: "How can we inspire people? What are we aspiring to achieve? What values do we uphold?" Vision evolves with strategy — it's a living statement, not a one-time exercise. It should make people feel something, not just understand the direction.