product-goal

Creates a measurable Product Goal document from PRD success indicators through structured coaching.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-goal-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-goal
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/product-goal
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-goal-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often write vague, unfalsifiable goals that cannot guide sprint priorities or be evaluated at the end of a time horizon. This Skill turns PRD success indicators into a concrete, time-bound Product Goal with specific metrics, a defensible minimum acceptable outcome, and identified risks. ## Core Features & Use Cases - Devil's Advocate Coaching: Challenges ambiguous goal statements, demands numbers, and blocks unmeasurable or vanity metrics before anything is written. - PRD-Driven Starting Point: Reads docs/01_product/01_prd.md to reuse existing success indicators instead of starting from a blank page. - Structured Output: Writes a formatted Product Goal document to docs/01_product/02_product_goal.md with goal statement, metrics table, minimum acceptable outcome, and risks. - Use Case: After finishing a PRD, a product manager runs this Skill to define a 6-month goal such as "70% of active users open the app 3+ times per week," with a realistic floor and top risks reviewed before writing. ## Quick Start Ask the assistant to create a Product Goal document based on the existing PRD, defining measurable success metrics and a minimum acceptable outcome.

Frequently Asked Questions about product-goal

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

FAQPage Schema
How do I write a measurable product goal from a PRD?▼

Start from the PRD's success indicators and convert them into a time-bound statement naming a specific user, a measurable outcome, and a horizon. Each metric needs a target number and a measurement method so the goal is falsifiable.

What is a minimum acceptable outcome in product goal setting?▼

It is the floor of success: the minimum evidence that the product hypothesis is valid even if the full goal is missed. It should be expressed in absolute numbers and sit meaningfully below the full goal, not as a small percentage reduction.

Does this Skill require a PRD to exist first?▼

No, but it works best with one. It reads docs/01_product/01_prd.md for success indicators; if no PRD exists, it asks for a short product description and intended success, while recommending the prd skill be run first.

What makes a product metric a vanity metric?▼

Vanity metrics like installs or signups measure reach rather than value delivered to the user. A good metric shows the user got something real from the product, such as weekly active usage measured via app events.

Where is the Product Goal document saved?▼

The document is written to docs/01_product/02_product_goal.md, and the folder is created if missing. The Skill detects the docs directory automatically and asks which one to use if multiple exist.