product-frameworks skill

---
name: product-frameworks-for-design-and-management
description: Comprehensive product design and management frameworks including UX heuristics (Hick's Law, Fitts's Law), design processes (Double Diamond, Lean UX, Agile, User-Centered Design), prioritization methods (RICE, MoSCoW, Kano Model, Pareto Principle), product lifecycle guidance, PRD templates, user story formats, design critique guidelines, and usability testing checklists. Use when analyzing features, creating product documentation, facilitating design reviews, planning user research, applying UX principles to interfaces, or making product decisions that require framework-based guidance.
---

# Product Frameworks

## Overview

Comprehensive product design and management frameworks to guide strategic decisions, improve user experience, and structure product workflows.

**Reference Files:**
- [references/design-principles.md](references/design-principles.md) — Hick's Law, Fitts's Law, affordances, feedback
- [references/design-processes.md](references/design-processes.md) — Double Diamond, Agile, Lean UX, User-Centered Design
- [references/prioritization-frameworks.md](references/prioritization-frameworks.md) — RICE, MoSCoW, Kano Model, Pareto Principle
- [references/lifecycle-guidance.md](references/lifecycle-guidance.md) — Product stage strategies
- [references/requirements.md](references/requirements.md) — PRD templates, user stories, acceptance criteria
- [references/critique-guidelines.md](references/critique-guidelines.md) — Design review facilitation
- [references/usability-testing.md](references/usability-testing.md) — Test planning and analysis

## Quick Start

1. **Identify the domain** — Determine which area of product/design work you're addressing
2. **Load the relevant reference** — Read the specific reference file for that domain
3. **Apply the frameworks** — Use the guidance to inform decisions or structure workflows

## When to Use

| Need | Reference File |
|------|----------------|
| UI/UX decisions | `design-principles.md` |
| Planning discovery work | `design-processes.md` |
| Evaluating features | `prioritization-frameworks.md` |
| Product stage strategy | `lifecycle-guidance.md` |
| Creating PRDs or user stories | `requirements.md` |
| Running design reviews | `critique-guidelines.md` |
| Planning user research | `usability-testing.md` |

## Example Workflows

**Feature Evaluation:**
1. Load `prioritization-frameworks.md` for RICE and Kano Model
2. Load `lifecycle-guidance.md` for stage-specific priorities
3. Apply both for informed prioritization

**Interface Design Feedback:**
1. Load `design-principles.md` for Hick's Law and Fitts's Law
2. Evaluate design against heuristics
3. Load `critique-guidelines.md` to structure feedback

**Discovery Phase Planning:**
1. Load `design-processes.md` for Double Diamond
2. Load `usability-testing.md` for research planning
3. Structure discovery using both

## Framework Summaries

**Design Principles:** Hick's Law (choice overload), Fitts's Law (target sizing), affordances, feedback loops, system status visibility

**Design Processes:** Double Diamond (Discover→Define→Develop→Deliver), Agile, Lean UX, User-Centered Design

**Prioritization:** RICE Scoring, MoSCoW (Must/Should/Could/Won't), Kano Model, 80/20 Rule

**Lifecycle:** Introduction, Growth, Maturity, Decline stage strategies

**Documentation:** PRD structure, user story format, acceptance criteria

## Best Practices

**Progressive Loading:** Don't load all references at once. Start with the most relevant file, then add others as needed.

**Context-Specific Application:** Frameworks are guidance, not rigid rules. Apply with judgment based on your product context.

**Complementary Frameworks:**
- Kano Model + RICE = comprehensive prioritization
- Double Diamond + Lean UX = structured but iterative discovery
- User-Centered Design + Usability Testing = validated user focus

**Shared Language:** Use framework terminology to align teams and communicate with stakeholders.