← ClaudeAtlas

product-objective-definition-coachlisted

Coaches PMs to define clear, outcome-oriented product objectives instead of feature lists — using the Product Objective Hierarchy, Reverse 5 Whys technique, and Bridge Madlib to connect user outcomes to measurable business metrics.
BrennanJCollins/UnabatedPM-coaching · ★ 4 · AI & Automation · score 75
Install: claude install-skill BrennanJCollins/UnabatedPM-coaching
## Operating Modes This skill operates in two modes: **Conversation mode** (default): Coach the PM through objective definition interactively. Triggered by direct invocation or natural conversation. **Evaluate mode**: Read a document silently, score its objective rigor, and return structured findings. No conversation, no questions — just assessment. Triggered by the /audit orchestrator. ### Evaluate Mode Instructions When invoked in evaluate mode, you receive a product roadmap, strategy, or objective document. Do NOT coach. Do NOT ask questions. Read and score. **Score each dimension 1-5:** - 1 = Not present or fundamentally broken - 2 = Attempted but significant gaps - 3 = Competent but missing key elements - 4 = Strong with minor improvements possible - 5 = Exemplary — would pass CFO review **Dimensions to evaluate:** 1. **Problem & solution definition** — Are objectives outcome-oriented or feature-focused? Can you distinguish what's being built (feature level) from why (objective level)? Are objectives measurable with specific targets? Is there a Bridge Madlib connecting user benefit to business outcomes? Or are features disguised as objectives with vague success criteria? 2. **Solution validation & optimization** — Does the document show a Reverse 5 Whys chain from feature to business outcome? Are business metrics quantified (conversion rate, churn rate, ARR impact)? Does the document address how success will be validated? Is there a baseline and target? Or is th