goal-setting

Validate metric movability and analyze trade-offs to produce goal statements with milestones.

1|2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill goal-setting-jayhjenkins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-setting
Source: https://github.com/jayhjenkins/ProductOSv0.2/tree/main/.claude/skills/workflows/goal-setting
Command: npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill goal-setting-jayhjenkins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Goal Setting Workflow helps product teams translate strategic ambitions into precise, measurable targets by validating movability and analyzing trade-offs, ensuring alignment across leadership, product, and engineering.

Core Features & Use Cases

  • Aligns metrics with the company North Star to maximize strategic impact.
  • Validates movability of a metric and estimates initiative impact across roadmaps.
  • Evaluates target scenarios (conservative, ambitious, moonshot) and generates a final goal with milestones and dependencies.
  • Use Case: A PM defines an OKR for user engagement and maps initiatives to achieve a clear, testable target within a quarterly horizon.

Quick Start

Define your metric and baseline, then run the three-step workflow: align north star, assess movability, and evaluate trade-offs to produce a final goal with milestones.

Frequently Asked Questions about goal-setting

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

FAQPage Schema
How do I set OKRs that align with my company's north star metric?

OKR alignment with your north star metric requires validating metric movability and evaluating target trade-offs across product roadmaps, generating a final goal statement with milestones and dependencies.

What is metric movability and why does it matter for goal setting?

Metric movability validation assesses whether planned initiatives can realistically impact a chosen target metric, preventing teams from committing to goal-setting targets that engineering roadmaps cannot actually shift.

How do I evaluate trade-offs between conservative and ambitious target scenarios?

Evaluating target trade-offs involves comparing conservative, ambitious, and moonshot scenarios against initiative impact estimates and resource assumptions, ensuring the final goal balances strategic ambition with engineering accountability.

Can I use this goal-setting workflow for quarterly product and engineering milestones?

Yes, this goal-setting workflow applies to planning quarterly milestones across product, engineering, and leadership teams, mapping initiative impact and dependencies to ensure accountability within a quarterly horizon.

What's the best way to structure a goal statement with clear dependencies?

Structuring a goal statement with clear dependencies requires running the three-step workflow to align north star metrics, assess movability, and evaluate trade-offs, outputting a final goal statement with milestones and defined resource dependencies.

When should I use proxy metrics instead of north star metrics for OKR planning?

Proxy metrics are selected for OKR planning when the north star metric is too broad for quarterly movability, allowing teams to define a testable target that validates initiative impact and maintains strategic alignment.