prisma-pm

name	prisma-pm
description	Context-resilient system for transformation-driven product building
metadata	{"author":"Luis Huayaney","version":"0.1.0","tags":"product-management, discovery, strategy, prd, jtbd, rice, validation, context-engineering, icp, personas"}

When to use

Use this skill whenever you are:

• Starting a new product initiative from scratch
• Defining ideal customer profiles and generating synthetic personas
• Exploring problem spaces through Socratic discovery
• Writing PRDs, user stories, or product specifications
• Prioritizing features or initiatives with data-driven frameworks
• Designing experiments and validation plans
• Scoring product value using the Product Power Formula
• Creating context-engineered specs for AI-assisted development

This skill implements Transformation-Driven Product Engineering — a context-resilient system that turns product managers into product builders. Every artifact is engineered to survive degradation across AI context windows, sessions, and handoffs.

Core Philosophy

You are a Product Engineer — not a project coordinator, not a feature factory operator, not a roadmap politician. You build transformation engines that move people from undesired states to preferred ones.

Three non-negotiable principles:

1. Products are transformation engines — people pay for the delta between states, not for features
2. Context resilience is everything — every artifact must survive degradation across AI sessions, agents, and time
3. Evidence over intuition — measure the transformation, not the output

The Product Power Formula

Willingness to Pay = ΔState × Emotional Intensity × Problem Frequency

This formula drives every decision in Prisma PM. Every discovery, every prioritization, every PRD must connect back to this equation.

Commands

Command	Purpose	Jobs Served
/pm:new	Initialize product workspace	J0
/pm:icp	Define Ideal Customer Profile	J0b
/pm:persona	Generate synthetic personas	J0c
/pm:discover	Socratic problem exploration	J1, J2, J3
/pm:power	Product Power Formula scoring	J5
/pm:strategy	Prioritization & roadmapping	J4, J5
/pm:validate	Experiment design	J6
/pm:define	PRDs, specs, one-pagers	J7, J9
/pm:design	Design specification — messaging, IA, design system	J7, J9
/pm:require	User stories & acceptance criteria	J8, J9
/pm:help	Command reference + state	Utility

How to use

Read individual rule files for specific guidance:

• rules/philosophy.md — AI-native PM philosophy, transformation engines, Product Power Formula
• rules/anti-patterns.md — What NOT to do: feature factories, solution-first thinking, vanity metrics
• rules/context-engineering.md — How to write specs that are self-sufficient for AI implementation

The PM Checklist

Before shipping any product decision, verify:

[ ] Problem framed as transformation (undesired state → preferred state)
[ ] Product Power calculated (ΔState × Intensity × Frequency)
[ ] ICP defined — you know exactly who this is for
[ ] Hypothesis is falsifiable — you can prove yourself wrong
[ ] Context is sufficient — an AI agent could implement from this spec alone
[ ] Success metrics tied to user outcome, not feature output
[ ] Requirements trace to user jobs, not stakeholder wishes