pm-kotler

Structures product definitions using Kotler's Five Levels of Product framework.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-kotler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-kotler
Source: https://github.com/ljucask/pureinn-product-development/tree/main/skills/pm-kotler
Command: npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-kotler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams clarify what a product is, why customers value it, and how its current and future capabilities should be positioned without confusing features with outcomes.

Core Features & Use Cases

  • Five-Level Product Definition: Structures a product from core benefit through basic, expected, augmented, and potential product layers using Kotler's framework.
  • KANO Planning Alignment: Maps product levels to Must-be, Performance, and Delighter categories to support MVP and roadmap decisions.
  • Use Case: A product manager preparing a PRD can use this Skill to define the product's value proposition, identify differentiators, and create an early feature scope signal.

Quick Start

Ask the AI to define your product using Kotler's Five Levels framework and create a structured product definition artifact.

Frequently Asked Questions about pm-kotler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define product value for a PRD without confusing features with customer outcomes?

To define product value for a PRD, structure your offering through Kotler's Five Levels of Product framework. This separates core customer benefits from expected attributes and augmented differentiators, ensuring your product definition focuses on outcomes rather than just features.

What is Kotler's Five Levels of Product framework and how does it apply to MVP planning?

Kotler's Five Levels of Product framework structures offerings from core benefit through basic, expected, augmented, and potential layers. For MVP planning, it maps these levels to Must-be, Performance, and Delighter KANO categories to prioritize early feature scope signals.

How do I structure a product roadmap using the KANO model and Kotler's framework?

Structure a product roadmap by mapping Kotler's five product levels to KANO classification signals. This aligns your core benefits and expected attributes with Must-be categories, while positioning augmented and potential capabilities as Delighter features for future roadmap phases.

Can I use Kotler's Five Levels framework for product positioning and strategy definition?

Yes, you can use Kotler's Five Levels framework for product positioning and strategy definition. It clarifies why customers value your product by structuring differentiators and future capabilities, which supports strategic positioning across current and potential product layers.

When do I need to use a five-level product definition approach instead of a standard feature list?

You need a five-level product definition approach when preparing a PRD or roadmap and struggling to distinguish features from outcomes. It is required when your product strategy must identify core benefits, expected attributes, and differentiators to create structured KANO classification signals.

Best way to identify product differentiators and future capabilities for a product strategy?

The best way to identify product differentiators and future capabilities is applying Kotler's Five Levels framework. It isolates augmented product layers as current differentiators and potential product layers as future capabilities, directly feeding KANO Delighter categories for your roadmap.