Loading...
Loading...
Found 209 Skills
Validate that the problem you want to solve is real, painful, and worth solving before building anything. Master Cindy Alvarez's structured approach to problem discovery interviews. Use when: **Before solution interviews** to confirm the problem exists; **Early customer discovery** to understand the problem space; **Pivoting** to find new problems worth solving; **Market expansion** to understand problems in new segments; **Feature prioritization** to validate which problems matter most
Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing skills into a structured process. Use this to
Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions. feature review, prioritization, RICE, WSJF, roadmap, backlog Use when: reviewing features or suggesting new features DO NOT use when: evaluating single feature scope - use scope-guard.
Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring.
Weighted social graph traversal that ranks your network connections by proximity to target leads. Uses exponential decay across hops, parallel execution with lead-intelligence skill, and API-driven outreach prioritization. Replaces Apollo, Clay, and manual networking.
RICE prioritization per Story with market research. Generates consolidated prioritization table in docs/market/[epic-slug]/prioritization.md. L2 worker called after ln-220.
Build and manage a product roadmap for a solopreneur business. Use when deciding what to build next, prioritizing features, planning product development over quarters, communicating plans to customers or stakeholders, or managing scope and expectations. Covers prioritization frameworks, roadmap structure, customer feedback integration, and saying no to feature requests. Trigger on "product roadmap", "what to build next", "feature prioritization", "roadmap planning", "product strategy", "feature requests".
Use when managing multiple initiatives across time horizons (now/next/later, H1/H2/H3), balancing risk vs return across portfolio, sizing and sequencing bets with dependencies, setting exit/scale criteria for experiments, allocating resources across innovation types (core/adjacent/transformational), or when user mentions portfolio planning, roadmap horizons, betting framework, initiative prioritization, innovation portfolio, or resource allocation across horizons.
Use when "RICE prioritization", "feature prioritization", "PRD writing", "user stories", or asking about "product roadmap", "customer interviews", "sprint planning", "backlog grooming"
Product Management frameworks, methodologies, and best practices library. Provides PM knowledge including prioritization (RICE, MoSCoW), goal setting (OKR, SMART), customer research (JTBD, Personas), and product strategy. Use when needing PM methodology guidance or framework application.
Prioritize a product roadmap/backlog and produce a Roadmap Prioritization Pack (season framing, scoring model, ranked opportunities, roadmap, decision narrative, rollout plan).
Support strategy, OKR, roadmap, and prioritization work using PM Brain’s strategy frameworks.