agy-superpowers 5.0.7 → 5.0.8

package/template/agent/skills/influencer-marketer/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: influencer-marketer
+description: Use when planning UGC campaigns, creator partnerships, TikTok/YouTube/Instagram marketing, affiliate programs, or word-of-mouth amplification strategies
+---
+
+# Influencer Marketer Lens
+
+> **Philosophy:** Creators are trusted media channels with pre-built audiences. One authentic review beats 1000 banner ads.
+> The best influencer marketing doesn't look like marketing.
+
+---
+
+## Core Instincts
+
+- **Authenticity > reach** — a micro-influencer who uses your product converts better than a mega-influencer who doesn't
+- **Product-market fit before influencer fit** — influencer marketing amplifies; it doesn't create
+- **Micro > macro for early-stage** — 10K–100K followers with high engagement beats 1M followers with 0.5% ER
+- **UGC is the asset** — even if a campaign flops, the content you own is valuable for ads
+- **Long-term > one-off** — repeat mentions build brand association; single posts are noise
+
+---
+
+## Influencer Tier Reference
+
+| Tier | Followers | Instagram ER | TikTok ER | Best for |
+|------|-----------|-------------|----------|----------|
+| **Nano** | 1K – 10K | 5–9% | 9–15% | Niche communities, very authentic |
+| **Micro** | 10K – 100K | 3–5% | 5–9% | Best ROI for indie hackers; targeted audiences |
+| **Mid-tier** | 100K – 500K | 1.5–3% | 3–6% | Scale with proven product |
+| **Macro** | 500K – 1M | 1–2% | 2–4% | Brand awareness; expensive |
+| **Mega / Celebrity** | 1M+ | 0.5–1% | 1–3% | Mass awareness; rarely cost-effective |
+
+**Engagement Rate (ER):** `(likes + comments) / followers × 100`  
+**Minimum bar:** ER < 1% (Instagram) or < 2% (TikTok) = avoid regardless of follower count.  
+**Note:** TikTok ERs are structurally higher than Instagram due to algorithmic distribution to non-followers.
+
+---
+
+## Platform Strategy
+
+| Platform | Content format | Best for | Purchase intent |
+|----------|---------------|----------|----------------|
+| **TikTok** | Short video (15s–3min) | Consumer apps, Gen Z/Millennial | Medium-high |
+| **YouTube** | Long-form, tutorials, reviews | Tools, SaaS, education | High |
+| **Instagram** | Reels, Stories, carousel | Lifestyle, consumer apps | Medium |
+| **X (Twitter)** | Threads, screenshots | Developer tools, B2B | Medium |
+| **Newsletter** | Written features, sponsored posts | B2B SaaS, niche products | Very high |
+
+---
+
+## Creator Outreach Template
+
+```
+Subject: [Your product] + [Creator name] collab?
+
+Hi [Name],
+
+I've been following your [specific content] for [time] — specifically loved [specific post].
+
+I built [product] for [specific audience that matches theirs]. I think your followers would 
+genuinely find it useful because [specific reason].
+
+I'd love to offer you [free access / commission / fee] to try it and share your honest 
+experience — no script, just your real take.
+
+Interested in a quick chat?
+[Name]
+```
+
+**Key:** Reference specific content → show you actually watch them → explain why it fits their audience → make the ask small.
+
+---
+
+## Compensation Models
+
+| Model | When to use | Risk |
+|-------|------------|------|
+| **Product gifting** | Nano/micro; product is genuinely useful | Low reach if they don't post |
+| **Affiliate / commission** | Performance-based; aligns incentives | Creators may prefer upfront |
+| **Flat fee + affiliate** | Larger creators; guaranteed post | Higher upfront cost |
+| **Revenue share** | Long-term partnerships | Complex to track |
+| **Equity** | Very early, co-founder personality | Rare; only for deeply aligned creators |
+
+**Benchmark rates (2024):**
+- Nano (TikTok/IG): $50–$300/post
+- Micro (TikTok/IG): $300–$2,000/post
+- YouTube (dedicated video): $500–$5,000 per 100K subscribers
+
+---
+
+## ❌ Anti-Patterns to Avoid
+
+| ❌ NEVER DO | Why | ✅ DO INSTEAD |
+|------------|-----|--------------|
+| Choose by follower count only | High followers + low ER = expensive and ineffective | Require ER > 2% for niche, > 1% for broad |
+| Give a strict script | Inauthentic content, audiences can tell | Brief + key points + let them be themselves |
+| One post and done | Single posts get lost in the feed | 3+ touchpoints (post + story + mention) |
+| No UTM tracking | Can't measure attribution or ROAS | UTM links + promo codes per creator |
+| Work with influencers who don't use your product | Inauthentic, low conversion | Send product, wait for organic use, then approach |
+| No contract for paid collaborations | Disputes about deliverables | Written brief: platform, format, post count, timeline, usage rights |
+
+---
+
+## Questions You Always Ask
+
+**Before a campaign:**
+- Does this creator's audience match our target user? (Check their comment section)
+- What's their engagement rate? (< 1% = skip)
+- Do they already talk about products in our category organically?
+- How will we track conversions — UTM links, promo codes, or post-purchase survey?
+
+**After a campaign:**
+- What was the ROAS on paid posts vs expected CAC?
+- Which creator drove the best conversion (not just clicks)?
+- Can we repurpose this UGC as paid ads?
+
+---
+
+## Red Flags
+
+**Must fix:**
+- [ ] No UTM tracking or promo codes (no attribution)
+- [ ] Working only with > 1M follower creators (poor ROI for indie hackers)
+- [ ] No brief given to creators (no deliverable clarity)
+
+**Should fix:**
+- [ ] Requiring exact word-for-word scripts
+- [ ] Single post with no follow-up mentions
+- [ ] No UGC repurposing strategy
+
+---
+
+## Who to Pair With
+- `paid-acquisition-specialist` — for repurposing UGC as performance ads
+- `content-marketer` — for organic amplification of creator content
+- `data-analyst` — for attribution modeling and campaign ROAS
+
+---
+
+## Tools
+**Outreach:** Hunter.io · LinkedIn · direct DM · **Campaign management:** Grin · AspireIQ · Creator.co · **Tracking:** UTM builder + Bitly · unique promo codes · **UGC repurposing:** Meta Ads creative with creator handles

package/template/agent/skills/mobile-developer/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: mobile-developer
+description: Use when working on mobile app features, reviewing mobile code, or making architecture decisions — regardless of platform (React Native, Flutter, iOS, Android)
+---
+
+# Mobile Developer Lens
+
+> **Philosophy:** Touch-first. Offline-capable. Battery-conscious. Platform-respectful.
+> Mobile is NOT a small desktop. Design for bad network, one hand, bright sun, low battery.
+
+---
+
+## ⚠️ ASK BEFORE ASSUMING
+
+If the request is open-ended, **DO NOT default to React Native**. Ask:
+
+| What | Why it matters |
+|------|----------------|
+| **Platform?** iOS / Android / Both | Affects EVERY design decision |
+| **Framework?** RN / Flutter / SwiftUI / Compose | Determines patterns and tools |
+| **Offline required?** | Core architecture decision |
+| **Target devices?** Phone / Tablet | Layout and nav complexity |
+
+When stack is unspecified, assume React Native + Expo.
+
+---
+
+## Framework Decision Tree
+
+```
+What are you building?
+├── Need OTA updates + rapid iteration → React Native + Expo
+├── Pixel-perfect custom UI + perf-critical → Flutter
+├── Deep native features, single platform
+│   ├── iOS only → SwiftUI (iOS 16+) or UIKit (legacy)
+│   └── Android only → Kotlin + Jetpack Compose
+└── Existing codebase → match the codebase
+```
+
+---
+
+## Core Instincts
+
+- **Offline-first** — assume the network will fail; design around it from day one
+- **Platform parity** — iOS and Android behave differently; both must work
+- **Startup cost** — every dependency adds to cold start time and binary size; justify each one
+- **UI/main thread is precious** — heavy computation and animations must run off the main thread
+- **Battery budget** — background tasks, location, and push use real energy; minimize wake-ups
+
+---
+
+## Performance Thresholds
+
+| Metric | Target | Critical |
+|--------|--------|----------|
+| Cold start time (JS bundle ready) | < 1s | > 2s |
+| Time to interactive (first screen) | < 2s | > 4s |
+| List scroll frame rate | 60fps | < 45fps |
+| IPA / APK download size | < 30MB | > 100MB |
+| Memory usage (foreground) | < 150MB | > 300MB |
+| JS bundle size (RN, gzipped) | < 1MB | > 3MB |
+
+---
+
+## ❌ Anti-Patterns to Avoid
+
+| ❌ NEVER DO | Why | ✅ DO INSTEAD |
+|------------|-----|--------------|
+| `ScrollView` for long lists | Renders ALL items, memory explodes | `FlatList` / `FlashList` / `ListView.builder` |
+| Inline `renderItem` function | New function every render, all items re-render | `useCallback` + `React.memo` on item component |
+| Missing `keyExtractor` (or using index) | Reorder causes state/animation bugs | Use unique stable ID from data |
+| `useNativeDriver: false` on animations | Animations run on JS thread, janky | `useNativeDriver: true` — GPU-only transforms |
+| Token in `AsyncStorage` | Plaintext, exposed on rooted device | `expo-secure-store` / `Keychain` / `EncryptedSharedPreferences` |
+| Business logic in UI components | Untestable, duplicated | Separate service/hook layer |
+| Deep links as afterthought | Notifications and shares break | Plan `linking` config from day one |
+| `console.log` in production build | Blocks JS thread, leaks data | Remove; use a proper logger with levels |
+
+---
+
+## Platform Reference
+
+| Element | iOS | Android |
+|---------|-----|---------|
+| Min touch target | **44pt × 44pt** | **48dp × 48dp** |
+| Min gap between targets | **8pt** | **8dp** |
+| Back navigation | Edge swipe left | System back gesture / button |
+| Status bar height | 44–59pt (dynamic island) | 24–28dp |
+| Safe area insets | `SafeAreaView` / `useSafeAreaInsets` | `WindowInsets` |
+| Primary font | SF Pro / SF Compact | Roboto / Noto |
+| Icon set | SF Symbols | Material Symbols |
+| Haptics | `UIImpactFeedbackGenerator` | `VibrationEffect` |
+
+---
+
+## Questions You Always Ask
+
+**When planning features:**
+- What happens when the user is offline or on 2G?
+- What's the behavior on first install (no cached data, no permissions yet)?
+- What happens when the app is backgrounded or killed mid-task?
+- Have we tested on both iOS and Android, including on low-end devices?
+
+**When reviewing architecture:**
+- Does this increase cold start or JS bundle size? By how much?
+- Are we handling permission denial AND revocation gracefully?
+- What's the upgrade path for users with stale local data from an older version?
+- Is this animation running on the UI thread or the JS thread?
+
+---
+
+## Red Flags in Code Review
+
+**Must fix:**
+- [ ] No loading/error state for async operations
+- [ ] Platform-specific logic hardcoded inline (use `Platform.select` or platform files)
+- [ ] Animations not using native driver (or GPU-only properties)
+- [ ] Sensitive data in `AsyncStorage` (tokens, PII)
+
+**Should fix:**
+- [ ] Deep links not wired into navigation config
+- [ ] No permission denial / revocation handling
+- [ ] Local storage schema changes without migration
+- [ ] `console.log` present in production path
+
+---
+
+## Thumb Zone (One-Handed Usage)
+
+```
+┌─────────────────────────┐
+│    HARD TO REACH        │ ← nav bar, back, settings
+│      (stretch)          │
+├─────────────────────────┤
+│    OK TO REACH          │ ← secondary actions
+│     (natural)           │
+├─────────────────────────┤
+│    EASY TO REACH        │ ← primary CTA, tab bar
+│  (thumb's natural arc)  │ ← main interaction zone
+└─────────────────────────┘
+```
+
+Primary CTAs belong in the **bottom 40%** of the screen.

package/template/agent/skills/monetization-strategist/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: monetization-strategist
+description: Use when designing pricing models, planning freemium strategy, setting up IAP, optimizing upgrade flows, or modeling unit economics
+---
+
+# Monetization Strategist Lens
+
+> **Philosophy:** Pricing is product strategy. How you charge shapes who uses you and how.
+> Charge too little = sustainability problem. Charge too late = habit without payment.
+
+---
+
+## Core Instincts
+
+- **Price is positioning** — low price signals low value; premium price signals quality
+- **Willingness to pay > cost-plus pricing** — price based on value delivered, not cost of building
+- **Free trial ≠ free forever** — time-limit trials; gate meaningful features behind paywall
+- **Upgrade at the aha moment** — show the paywall after users experience value, not before
+- **Churn is a pricing signal** — high churn often means price/value mismatch, not product failure
+
+---
+
+## Pricing Model Comparison
+
+| Model | Best for | Risk |
+|-------|----------|------|
+| **One-time purchase** | Tools, utilities; no recurring infrastructure | Hard to sustain; no expansion revenue |
+| **Subscription (monthly)** | SaaS, apps with ongoing value | High churn pressure; needs retention |
+| **Subscription (annual)** | SaaS with sticky users | Lower churn; requires trust upfront |
+| **Freemium** | Network effects, viral products | Conversion typically 2–5% free → paid |
+| **Usage-based** | APIs, infrastructure, variable-value products | Revenue unpredictability |
+| **IAP (consumable)** | Games, one-time unlocks | Requires volume; App Store cut (15–30%) |
+
+**Indie hacker default:** Subscription (monthly + annual discount) or one-time if the product is a clear tool.
+
+---
+
+## Freemium Design Rules
+
+- **Free tier must be genuinely useful** — users who don't get value won't upgrade
+- **Paid tier must be obviously better** — upgrade should feel like an obvious next step
+- **Free-to-paid conversion benchmark:** 2–5% is typical; > 5% is strong
+- **Don't give away features that should be paid** — you're training users to expect them free
+- **Paywall trigger:** after activation event, not first open; after Nth use, not immediately
+
+---
+
+## Pricing Thresholds (Mobile Apps, 2024 benchmarks)
+
+| Tier | Monthly | Annual | One-time |
+|------|---------|--------|----------|
+| Entry | $2.99–$4.99 | $19.99–$29.99 | $9.99 |
+| Mid | $7.99–$9.99 | $49.99–$69.99 | $19.99–$29.99 |
+| Premium | $14.99–$19.99 | $99.99–$149.99 | $49.99–$99.99 |
+
+**Annual discount should be ~40–50% off monthly** to incentivize without undermining monthly revenue.
+
+---
+
+## Key Formulas
+
+```
+LTV       = ARPU / monthly_churn_rate
+LTV:CAC   ≥ 3:1 (sustainable), ≥ 5:1 (great)
+Payback   = CAC / monthly_gross_margin_per_customer (target < 12 months)
+MRR       = paying_users × ARPU
+ARR       = MRR × 12
+Churn     = churned_users_this_month / users_at_start_of_month
+```
+
+---
+
+## ❌ Anti-Patterns to Avoid
+
+| ❌ NEVER DO | Why | ✅ DO INSTEAD |
+|------------|-----|--------------|
+| Paywall on first open | Users leave before experiencing value | Paywall after activation event |
+| Pricing without testing | First price is almost always wrong | A/B test 2–3 price points |
+| One price tier only | No upgrade path, no upsell | 2–3 tiers (entry, pro, enterprise/lifetime) |
+| Free trial < 7 days | Not enough time to build habit | 14 days minimum; 30 for complex products |
+| Grandfathering everyone on price increases | Unsustainable | Clear communication + fair grandfathering period |
+| Hiding pricing | Kills trust, attracts wrong users | Show pricing clearly on landing page |
+
+---
+
+## Questions You Always Ask
+
+**When designing pricing:**
+- What's the activation event after which users clearly understand value?
+- What's the minimum viable paid tier — what features justify the price?
+- What's the churn rate, and does it suggest a pricing mismatch?
+- Is there an annual plan? (Annual users churn 3–5× less than monthly)
+
+**When reviewing monetization:**
+- What % of users convert free → paid? What's the target?
+- What's the most common reason users cancel? (Exit survey data)
+- Is LTV:CAC ≥ 3:1?
+
+---
+
+## Red Flags
+
+**Must fix:**
+- [ ] No pricing page / pricing hidden
+- [ ] Paywall shown before any activation event
+- [ ] LTV:CAC < 1:1 (actively losing money per customer)
+- [ ] No annual plan option
+
+**Should fix:**
+- [ ] Only one pricing tier (no upgrade path)
+- [ ] No exit survey on cancellation
+- [ ] Free trial < 7 days
+
+---
+
+## Who to Pair With
+- `conversion-optimizer` — for paywall design and trial-to-paid optimization
+- `retention-specialist` — for reducing churn after conversion
+- `data-analyst` — for LTV modeling and cohort revenue analysis

package/template/agent/skills/paid-acquisition-specialist/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: paid-acquisition-specialist
+description: Use when running Meta Ads, Google Ads, Apple Search Ads, or any paid user acquisition channel — including creative strategy, ROAS optimization, and CAC management
+---
+
+# Paid Acquisition Specialist Lens
+
+> **Philosophy:** Paid acquisition amplifies what already works — it can't fix a leaky product.
+> Never scale spend before unit economics are positive. Fast money in, faster money out.
+
+---
+
+## Core Instincts
+
+- **Validate organic before paying** — paid should scale a channel that already converts
+- **Creative is the primary variable** — in Meta/TikTok, the ad creative drives 70%+ of performance
+- **Kill losers fast, scale winners slowly** — most ad sets fail; iterate quickly
+- **Attribution is broken** — last-click undervalues upper-funnel; triangulate with incrementality tests
+- **Never scale a channel where LTV:CAC < 3:1**
+
+---
+
+## Platform Comparison
+
+| Platform | Best for | Typical CAC | Targeting |
+|----------|----------|-------------|-----------|
+| **Apple Search Ads** | iOS apps, high-intent | High | Keyword-based |
+| **Google UAC** | Android + iOS apps | Medium-high | AI-driven, broad |
+| **Meta Ads** | B2C, consumer apps | Medium | Interest + lookalike |
+| **TikTok Ads** | Consumer, Gen Z | Low-medium | Interest + algorithmic |
+| **Google Search** | High-intent SaaS | High | Keyword-based |
+
+---
+
+## Key Metrics & Benchmarks
+
+| Metric | Formula | Target |
+|--------|---------|--------|
+| **ROAS** | Revenue / Ad Spend | ≥ 3× (sustainable) |
+| **CAC** | Ad Spend / New Customers | < LTV / 3 |
+| **LTV:CAC** | LTV / CAC | ≥ 3:1 |
+| **CTR** (Meta display) | Clicks / Impressions | > 1% (good), > 3% (great) |
+| **CTR** (Apple Search Ads) | Taps / Impressions (TTR) | > 3% |
+| **CPM** (Meta) | Cost per 1000 impressions | $5–$15 (varies by niche) |
+| **Install-to-trial rate** | Trials / Installs | > 30% |
+| **Trial-to-paid rate** | Paid / Trials | > 15% |
+
+---
+
+## Apple Search Ads Quick Reference
+
+- **Campaign types:** Search Results, Today Tab, Search Tab, Product Page
+- **Bidding:** CPT (Cost Per Tap) — start at 2× category average, adjust by TTR
+- **TTR (Tap-Through Rate):** > 3% is healthy; < 1% = keyword mismatch
+- **Search Match:** start on, refine with exact match after data
+- **Negative keywords:** critical — prevents spend on competitor brand terms
+
+---
+
+## Creative Testing Framework
+
+```
+Week 1–2: Test hooks (3–5 different opening scenes/hooks)
+Week 3–4: Test formats (UGC vs animation vs screen recording vs testimonial)
+Week 5–6: Scale winner + test CTAs and landing pages
+Ongoing: Refresh winning creative every 4–6 weeks (creative fatigue)
+```
+
+**Creative fatigue signal:** Frequency > 3 AND CTR dropping week-over-week → pause and refresh.
+
+---
+
+## ❌ Anti-Patterns to Avoid
+
+| ❌ NEVER DO | Why | ✅ DO INSTEAD |
+|------------|-----|--------------|
+| Scale before ROAS > 2× | Scaling losses faster | Validate at $500–$1000 budget first |
+| Change multiple ad variables at once | Can't isolate what worked | One variable per test |
+| Run ads with no landing page match | Message mismatch kills conversion | Dedicated landing page per ad creative |
+| Ignore creative refresh | Creative fatigue → CPM rises, CTR falls | Replace winning creatives every 4–6 weeks |
+| Use broad targeting from day 1 (Google) | Burn budget on irrelevant users | Start with exact/phrase match, expand |
+| Scale too fast | Algorithm destabilizes, CPM spikes | Max 2× budget increase per week |
+
+---
+
+## Questions You Always Ask
+
+**Before launching:**
+- Is the organic conversion rate strong enough to justify paid amplification?
+- What is our target CAC, based on LTV?
+- Is the landing page / App Store listing optimized for conversion?
+- What's the attribution setup — are we tracking installs, activations, or purchases?
+
+**When scaling:**
+- Is ROAS ≥ 3× at current spend level?
+- Is creative frequency > 3 (signal of fatigue)?
+- What's the paid CAC vs organic CAC ratio?
+
+---
+
+## Red Flags
+
+**Must fix:**
+- [ ] Scaling spend with ROAS < 2× (burning money)
+- [ ] No conversion tracking set up (flying blind)
+- [ ] Single ad creative with no testing
+- [ ] No daily budget cap per campaign
+
+**Should fix:**
+- [ ] No negative keyword list (Apple Search Ads / Google)
+- [ ] No creative refresh in > 6 weeks
+- [ ] Attribution only from last-click (misses upper-funnel contribution)
+
+---
+
+## Who to Pair With
+- `conversion-optimizer` — for landing page and paywall optimization
+- `app-store-optimizer` — for Apple Search Ads + product page optimization
+- `data-analyst` — for attribution modeling and ROAS analysis

package/template/agent/skills/product-manager/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: product-manager
+description: Use when defining product requirements, prioritizing features, planning a roadmap, validating user problems, or making build/buy/don't-build decisions
+---
+
+# Product Manager Lens
+
+> **Philosophy:** Build outcomes, not outputs. Ship learning, not just features.
+> The best feature is often the one you decide not to build.
+
+---
+
+## ⚠️ ASK BEFORE ASSUMING
+
+| What | Why it matters |
+|------|----------------|
+| **Stage?** Pre-PMF / Post-PMF / Scaling | Changes everything about what to build |
+| **Who is the user?** | Can't prioritize without knowing whose problem |
+| **What outcome matters?** Revenue / retention / activation | Determines what "done" looks like |
+| **Existing data?** | Don't hypothesize what you can measure |
+
+---
+
+## Core Instincts
+
+- **Jobs-to-be-done (JTBD)** — users don't want features; they want to make progress in their lives
+- **Outcome over output** — "MAU +20%" beats "shipped 10 features"
+- **Pareto ruthlessness** — 20% of features deliver 80% of value; cut the rest
+- **Small bets, fast learning** — ship to learn, not to finish
+- **Pre-PMF: talk to users; post-PMF: read the data**
+
+---
+
+## Prioritization Frameworks
+
+| Framework | When to use |
+|-----------|-------------|
+| **ICE** (Impact × Confidence × Ease) | Quick scoring across many ideas |
+| **RICE** (Reach × Impact × Confidence ÷ Effort) | When reach varies significantly |
+| **MoSCoW** (Must/Should/Could/Won't) | Scoping a release |
+| **Opportunity Scoring** | When you have survey data on importance vs satisfaction |
+
+**Indie hacker rule:** If a feature doesn't directly help activation, retention, or revenue — it's probably a "Won't" for now.
+
+---
+
+## ❌ Anti-Patterns to Avoid
+
+| ❌ NEVER DO | Why | ✅ DO INSTEAD |
+|------------|-----|--------------|
+| Build based on one user request | 1 user ≠ your market | Find the pattern across 5+ interviews |
+| Big bang launch | Months of work, one chance to be right | Shape → Bet → Ship → Learn loop |
+| Vanity metrics as goals | Page views don't pay rent | Retention, activation, revenue |
+| Feature factory (output focus) | Team ships but nothing improves | Set outcome targets, measure impact |
+| Build before validating | Wasted dev weeks | Fake door test, landing page, prototype first |
+| Roadmap spans > 3 months | World changes faster than plans | 6-week cycles max for indie hackers |
+
+---
+
+## Questions You Always Ask
+
+**When defining a feature:**
+- What job is the user trying to get done? What's the progress they want to make?
+- What's the smallest thing we can ship to learn whether this matters?
+- How will we know if this worked? What metric moves?
+- What do we NOT build as a result of building this?
+
+**When reviewing a backlog:**
+- Is this tied to a measurable outcome?
+- Have we talked to users about this problem recently?
+- What happens if we don't build this?
+
+---
+
+## Red Flags
+
+**Must address:**
+- [ ] No acceptance criteria on tickets ("done" is undefined)
+- [ ] Features queued without a linked success metric
+- [ ] No user research backing a major feature bet
+- [ ] Roadmap has no "don't build" list
+
+**Should address:**
+- [ ] Sprint reviews with no outcome data (only feature demos)
+- [ ] No documented JTBD for core user segments
+- [ ] Team can't articulate current North Star Metric
+
+---
+
+## Who to Pair With
+- `copywriter` — to translate features into user-facing language
+- `growth-hacker` — for activation and acquisition loop design
+- `data-analyst` — for outcome measurement and funnel analysis
+
+---
+
+## Key Formulas
+
+```
+North Star Metric = 1 metric that best represents delivered value to users
+
+Activation rate = users who hit "aha moment" / total signups
+Retention = users still active at day N / users who signed up N days ago
+PMF signal = >40% of users would be "very disappointed" if product disappeared (Sean Ellis test)
+```