Product Management Skill

---
name: product-management
description: Product management tasks like writing specs, analyzing feedback, and planning features. Use for PRDs, user research synthesis, prioritization frameworks, and roadmap planning.
allowed-tools: read_file write_file http_request sql_query
---

# Skill: Product management

## Purpose

Assist with product management workflows including writing specifications, synthesizing user research, prioritizing features, and creating roadmaps. This skill focuses on clear communication, user-centered thinking, and data-driven decision making.

## When to use this skill

- Writing **product requirements documents** (PRDs) for new features.
- Analyzing **user feedback** from surveys, support tickets, or NPS.
- Prioritizing **feature requests** using RICE, ICE, or other frameworks.
- Creating **user stories** with clear acceptance criteria.
- Planning **roadmaps** and release schedules.

## Inputs

- **Feature request or problem statement**: what needs to be solved.
- **User research**: feedback, interviews, survey data.
- **Business context**: goals, constraints, competitive landscape.
- **Technical constraints**: platform limitations, dependencies.

## Out of scope

- Making **final product decisions** without stakeholder input.
- Setting **pricing or business model** without approval.
- Making **technical architecture** decisions.
- Customer communication or **external announcements**.

## Conventions

- Start with the **problem, not the solution**.
- Ground decisions in **user research and data**.
- Use **clear, jargon-free language**.
- Include **success metrics** for every feature.
- Consider **edge cases and failure modes**.

## Required behavior

1. Define the **problem clearly** before proposing solutions.
2. Identify **user personas** and their needs.
3. Consider **technical feasibility** and constraints.
4. Write **clear acceptance criteria** for each requirement.
5. Prioritize ruthlessly using **impact vs. effort**.
6. Include **success metrics** and how to measure them.

## Required artifacts

- **PRD**: problem statement, solution, requirements, success metrics.
- **User stories**: as a [user], I want [action], so that [benefit].
- **Acceptance criteria**: specific, testable conditions for completion.
- **Prioritization matrix**: scored feature list with rationale.
- **Dependencies**: technical and cross-team requirements.

## Implementation checklist

1. Clarify the problem and who it affects.
2. Gather relevant user research and data.
3. Define the target user persona.
4. Draft the proposed solution.
5. Write detailed requirements with acceptance criteria.
6. Identify success metrics and how to track them.
7. Note dependencies and risks.
8. Get feedback from stakeholders.

## Verification

Before finalizing a PRD:

- Verify the problem is **clearly defined and validated**.
- Check that requirements are **specific and testable**.
- Confirm success metrics are **measurable and achievable**.
- Validate with engineering that the solution is **technically feasible**.

The skill is complete when:

- The PRD clearly communicates what to build and why.
- Engineering can implement from the requirements.
- Success can be measured after launch.
- Stakeholders have reviewed and approved.

## Safety and escalation

- If a feature could have **negative user impact**, flag for ethics review.
- If priorities conflict with **company strategy**, escalate to leadership.
- If technical feasibility is **uncertain**, get engineering input before finalizing.
- If user research is **lacking**, recommend gathering more data.
- Never make **commitments to customers** without proper authorization.

# Write a PRD
autohand --skill product-management --prompt "Write a PRD for adding team workspaces to our product"

# Analyze user feedback
autohand --skill product-management --prompt "Analyze our NPS comments and identify the top 5 themes"

# Prioritize features
autohand --skill product-management --prompt "Help me prioritize these 10 feature requests using RICE scoring"

# Create user stories
autohand --skill product-management --prompt "Break down the payments feature into user stories with acceptance criteria"

# Competitive analysis
autohand --skill product-management --prompt "Compare our onboarding flow to Notion, Linear, and Figma"