namht1st
9 verified skills9 total stars
product-facilitation
Use when any product skill or workflow needs structured intake, shared product-context state, or a single authority for next-step routing. Use on any product work that spans discovery, research, specification, or prioritization to ensure shared context and consistent routing.
testing1
product-prioritization
Use for scoring candidate slices once opportunity context, metric context, and tradeoff criteria are explicit. Use when prioritizing features, ranking backlog items, or applying RICE, MoSCoW, or ICE frameworks.
development1
product-engagement-design
Use for habit loops, progression systems, gamification mechanics, behavioral nudges, freemium funnel design, activation mechanics, and PLG conversion flows that must increase product value without becoming manipulative. Use when designing retention loops, streaks, badges, or onboarding flows.
content-media1
product-metrics-analysis
Use for outcome-based success metrics, baseline and target checks, leading indicators, and counter-metric validation across product work. Use when defining success metrics, building a metric tree, or reviewing KPIs.
development1
product-opportunity-mapping
Use for turning discovery evidence into pursue, monitor, or defer opportunity decisions with dependencies and revisit triggers. Use when the team has evidence but hasn't chosen which opportunity to pursue.
testing1
product-prd-authoring
Use for evidence-linked requirements, explicit non-goals, Given/When/Then acceptance scenarios, and engineering-ready PRDs. Use when writing a PRD, product requirements document, or feature specification.
development1
product-discovery-synthesis
Use for problem framing, JTBD synthesis, evidence-quality checks, and opportunity shaping during product discovery. Use when a feature request needs reframing into a user problem or discovery evidence needs synthesis into an opportunity.
development1
product-validation
Use for evidence-quality diagnosis, validation-method selection, and advisory next-step labels before product work moves forward. Use when evidence is thin, a feature has momentum without proof, or the cheapest next evidence move must be identified.
testing1
skills/product-user-interview-design
--- name: product-user-interview-design description: Use for designing qualitative research packages: interview type, participant targeting, screener, guide, synthesis plan, and completion criteria. Use when a decision is blocked by weak user evidence or the team needs to design a research study. triggers: - "design user interviews" - "research plan" - "interview guide" - "participant screener" - "qualitative research design" - "user research study" --- > **Standalone Mode:** This s
testing1