skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
eyadsibai/ltk63 installs

product-management

Use when "RICE prioritization", "feature prioritization", "PRD writing", "user stories", or asking about "product roadmap", "customer interviews", "sprint planning", "backlog grooming"

How do I install this agent skill?

npx skills add https://github.com/eyadsibai/ltk --skill product-management
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides templates and frameworks for product management tasks such as RICE prioritization, PRD writing, and sprint planning. It contains no executable code, external dependencies, or network operations.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

<!-- Adapted from: claude-skills/product-team/product-manager-toolkit -->

Product Management Toolkit

Feature prioritization, PRDs, and product discovery frameworks.

When to Use

  • Prioritizing feature backlog
  • Writing product requirements
  • Analyzing customer interviews
  • Planning sprints and roadmaps
  • Making data-driven product decisions

RICE Prioritization

Formula

Score = (Reach × Impact × Confidence) / Effort
FactorScale
ReachUsers per quarter
ImpactMassive=3, High=2, Medium=1, Low=0.5, Minimal=0.25
ConfidenceHigh=100%, Medium=80%, Low=50%
EffortPerson-months

Example

FeatureReachImpactConfidenceEffortScore
User Dashboard5003 (massive)80%5240
Dark Mode3001 (medium)100%2150
API Rate Limiting10002 (high)90%3600

Value vs Effort Matrix

           Low Effort    High Effort

High       QUICK WINS    BIG BETS
Value      [Prioritize]  [Strategic]

Low        FILL-INS      TIME SINKS
Value      [Maybe]       [Avoid]

PRD Template

# Feature: [Name]

## Problem Statement
What problem are we solving? For whom?

## Success Metrics
- Primary: [Metric and target]
- Secondary: [Supporting metrics]

## User Stories
As a [user], I want [capability] so that [benefit].

## Requirements
### Must Have (P0)
- [Requirement 1]

### Should Have (P1)
- [Requirement 2]

### Out of Scope
- [Explicit exclusion]

## Design
[Link to designs or wireframes]

## Technical Approach
[High-level technical approach]

## Timeline
- Phase 1: [Scope] - [Date]
- Phase 2: [Scope] - [Date]

## Open Questions
- [Question 1]

Customer Interview Framework

Structure (35 min)

  1. Context (5 min)

    • Role and responsibilities
    • Current workflow
    • Tools used
  2. Problem Exploration (15 min)

    • Pain points
    • Frequency and impact
    • Current workarounds
  3. Solution Validation (10 min)

    • Reaction to concepts
    • Value perception
    • Willingness to pay
  4. Wrap-up (5 min)

    • Other thoughts
    • Referrals

Analysis Framework

Extract from each interview:

  • Pain points with severity (high/medium/low)
  • Feature requests with priority
  • Jobs to be done patterns
  • Key quotes for stakeholder communication

Sprint Planning

Capacity Planning

Sprint Capacity = Team Size × Days × Velocity Factor

Example:
5 engineers × 10 days × 0.7 = 35 story points

Story Point Guidelines

PointsComplexityExample
1TrivialCopy change
2SimpleAdd field to form
3MediumNew API endpoint
5ComplexNew feature with UI
8Very ComplexIntegration with external service
13Epic-levelBreak down further

MoSCoW Method

  • Must Have: Critical for launch
  • Should Have: Important but not critical
  • Could Have: Nice to have
  • Won't Have: Out of scope (this release)

Metrics Framework

North Star Metric

  • What's the #1 value to users?
  • Is it measurable and actionable?
  • Does it predict business success?

Feature Success Metrics

  • Adoption: % users using feature
  • Frequency: Usage per user per week
  • Retention: Continued usage over time
  • Satisfaction: NPS/CSAT for feature

Best Practices

Writing PRDs

  • Start with problem, not solution
  • Include clear success metrics
  • Explicitly state what's out of scope
  • Use visuals (wireframes, flows)

Prioritization

  • Mix quick wins with strategic bets
  • Account for dependencies
  • Buffer for unexpected work (20%)
  • Revisit quarterly

Discovery

  • Ask "why" 5 times
  • Focus on past behavior, not intentions
  • Look for emotional reactions
  • Validate with data

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/eyadsibai/ltk/product-management">View product-management on skillZs</a>