skills.rest
pirras-torres
pirras-torresCOMMUNITY
Explore all skills by this author →
GitHub

product-principles

Generates product principles documentation from structured user interviews about trade-off decisions.

Updated May 24, 2026
Search Tags:#documentation#markdown#product management#interview#scrum#decision-making#product principles
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-principles-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-principles
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/product-principles
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-principles-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack explicit decision-making rules, so every product trade-off becomes an ad-hoc debate. This Skill turns real decisions and anchoring answers into a written set of product principles that resolve future trade-offs consistently. ## Core Features & Use Cases - Structured Interview: Asks trade-off scenario questions and anchoring questions one at a time to gather raw material for principles. - Context-Aware Questions: Reads the existing PRD to tailor questions to the specific product rather than generic prompts. - Formatted Document Output: Writes 4-7 ordered principles with rationale and concrete examples to docs/01_product/03_product_principles.md. - Use Case: After writing a PRD for a new app, run this Skill to capture guiding rules like "Clarity over completeness" so the team can resolve design and scope conflicts without lengthy debates. ## Quick Start Use the product-principles skill to interview me and create the product principles document for my project.

Frequently Asked Questions about product-principles

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

FAQPage Schema
How do I create product principles for a software project?▼

Run the product-principles skill, which interviews you with three trade-off scenario questions and four anchoring questions. It derives 4-7 principles with names, rationales, and concrete examples, then writes them to docs/01_product/03_product_principles.md.

What makes a good product principle versus a bad one?▼

A good principle takes a position and resolves trade-offs, such as "Clarity over completeness." A bad one is a vague value statement like "We value quality" that cannot guide an actual decision.

Does the product-principles skill require a PRD first?▼

A PRD is not strictly required, but the skill reads docs/01_product/01_prd.md if it exists to make interview questions specific to your product. Without it, questions remain more generic.

Where does the product principles document get saved?▼

The document is written to docs/01_product/03_product_principles.md. The skill auto-detects the docs folder, asks which one to use if multiple exist, and creates the folder if missing.

How many product principles should a project have?▼

The skill generates 4-7 principles ordered by importance. When two principles conflict, the earlier one in the list takes precedence, so ordering encodes priority.

Related Skills

Explore More Product & Management Skills→
hybrid-npmhybrid-npm
17

product-marketing-context

Create or update a centralized product marketing context document.

Official
Intermediate
archerliarcherli

user-story-mapping

Define segments, personas, and narratives for user workflows using the Jeff Patton Story Mapping Framework.

Community
Advanced
codesour-designcodesour-design

layers-conceptual-model

Model product objects, relationships, states, and vocabulary before interface design.

Community
Advanced
rbaumierrbaumier
4

brainstorming

Guide teams through structured ideation and design validation with formal specifications.

Community
Advanced