arkaos 4.26.0 → 4.28.0

package/config/evals/saas.yaml

@@ -0,0 +1,616 @@
+# --- BEGIN imported (marketing-skills, MIT) — regenerated by scripts/tools/evals_import.py ---
+- id: saas-churn-analysis-01
+  department: saas
+  prompt: Our SaaS product has a 7% monthly churn rate and we need to bring it down. We're
+    a $49/month project management tool with about 2,000 paying customers. Can you help us
+    design a churn prevention strategy?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Addresses both voluntary and involuntary churn
+  - Designs cancel flow with proper stages
+  - Includes exit survey with multiple categories
+  - Maps save offers to cancellation reasons
+  - Addresses dunning stack for payment recovery
+  - Recommends health score model
+  - Provides prioritized implementation plan
+  rubric: 'Should check for product-marketing.md first. Should address both voluntary and
+    involuntary churn. Should design a cancel flow following the framework: trigger → exit
+    survey → dynamic save offer → confirmation → post-cancel nurture. Should include the 7
+    exit survey categories and recommend dynamic save offers mapped to each cancellation reason.
+    Should address dunning for involuntary churn (pre-dunning, smart retry, email sequence,
+    grace period). Should recommend a health score model. Should provide prioritized implementation
+    plan.'
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-churn-analysis-02
+  department: saas
+  prompt: We keep losing customers because their credit cards expire. About 15% of our churn
+    is from failed payments. How do we fix this?
+  expected_properties:
+  - Identifies as involuntary churn / payment recovery
+  - Applies dunning stack framework
+  - Includes pre-dunning card expiration reminders
+  - Includes smart retry logic
+  - Provides dunning email sequence with escalating urgency
+  - Recommends grace period before cancellation
+  - Mentions card updater services or backup payment methods
+  - Includes recovery benchmarks
+  rubric: 'Should identify this as involuntary churn / payment recovery. Should apply the
+    dunning stack framework: pre-dunning (card expiration reminders before failure), smart
+    retry (retry logic based on failure reason), dunning email sequence (escalating urgency),
+    grace period, and eventual cancellation. Should provide specific timing for each stage.
+    Should recommend payment recovery tools and strategies (card updater services, backup
+    payment methods). Should include recovery rate benchmarks.'
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-churn-analysis-03
+  department: saas
+  prompt: what should we show users when they click the cancel button? right now they just
+    go straight to cancellation with no attempt to save them
+  expected_properties:
+  - Triggers on casual phrasing
+  - Designs multi-step cancel flow
+  - Includes exit survey with 7 categories
+  - Provides dynamic save offers mapped to reasons
+  - Includes copy recommendations
+  - Warns against dark patterns
+  - Includes confirmation and post-cancel steps
+  rubric: 'Should trigger on casual phrasing. Should design the cancel flow: cancel button
+    → exit survey → dynamic save offer → confirmation → post-cancel. Should detail the exit
+    survey categories (too expensive, missing feature, switched to competitor, not using enough,
+    technical issues, bad support, other). Should provide dynamic save offers matched to each
+    reason (e.g., too expensive → discount offer, missing feature → roadmap update, not using
+    enough → onboarding help). Should include copy recommendations for each screen. Should
+    warn against dark patterns (making it impossible to cancel).'
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-churn-analysis-04
+  department: saas
+  prompt: How do we identify which customers are at risk of churning before they actually
+    cancel? We want to be proactive.
+  expected_properties:
+  - Applies health score model framework
+  - Defines usage-based health signals
+  - Defines engagement-based health signals
+  - Defines account-based health signals
+  - Recommends scoring methodology
+  - Defines risk tiers with interventions
+  - Suggests data sources and implementation
+  rubric: 'Should apply the health score model framework. Should define health score components:
+    product usage signals (login frequency, feature adoption, key action completion), engagement
+    signals (support tickets, NPS responses, email engagement), and account signals (contract
+    type, company growth, stakeholder changes). Should recommend scoring methodology (0-100
+    scale). Should define risk tiers and recommended interventions for each tier. Should suggest
+    data sources and implementation approach.'
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-churn-analysis-05
+  department: saas
+  prompt: Our exit survey shows that 40% of cancellations say 'too expensive' as the reason.
+    What save offers should we try?
+  expected_properties:
+  - References save offers for 'too expensive' reason
+  - Suggests multiple offer types (discount, downgrade, pause)
+  - Recommends testing different offers
+  - Notes that 'too expensive' often masks other issues
+  - Suggests deeper follow-up questions
+  - Provides specific save offer copy or structure
+  rubric: 'Should reference the dynamic save offers mapped to the ''too expensive'' reason.
+    Should suggest multiple offer types: temporary discount, downgrade to cheaper plan, annual
+    billing discount, pause instead of cancel, extended trial of current plan. Should recommend
+    testing different offers to find what works best. Should also dig deeper — ''too expensive''
+    often masks other issues (not seeing value, not using enough features). Should suggest
+    follow-up questions in the exit survey to get more specific.'
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-churn-analysis-06
+  department: saas
+  prompt: We want to set up a win-back email sequence for customers who already cancelled.
+    Can you help write those emails?
+  expected_properties:
+  - Recognizes overlap with email sequence work
+  - References or defers to emails skill
+  - May provide churn-specific context for the sequence
+  - Does not attempt to write a full email sequence
+  rubric: Should recognize this overlaps with email sequence work. Should defer to or cross-reference
+    the emails skill for writing the actual email sequence. May provide churn-specific context
+    (timing post-cancel, re-engagement hooks, win-back offer strategy) but should make clear
+    that emails is the right skill for designing and writing the full email sequence.
+  tags:
+  - churn-analysis
+  - imported
+- id: saas-launch-execute-01
+  department: saas
+  prompt: We're launching a new B2B SaaS product for design teams in 6 weeks. It's a design
+    review tool. We have a small audience (500 email subscribers, 2k Twitter followers). Help
+    us plan the launch.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies ORB Framework (Owned, Rented, Borrowed)
+  - Maps to user's specific channels and audience sizes
+  - Recommends five-phase launch approach
+  - Provides timeline mapped to 6-week window
+  - Provides specific tactics for each phase
+  - Recommends audience building before launch
+  - Includes launch day checklist
+  rubric: 'Should check for product-marketing.md first. Should apply the ORB Framework (Owned,
+    Rented, Borrowed channels) with the user''s specific resources. Owned: email list (500
+    subscribers), website. Rented: Twitter (2k followers). Borrowed: partnerships, communities,
+    Product Hunt. Should recommend the five-phase launch approach with a timeline mapped to
+    the 6-week window: Internal prep, Alpha (existing network), Beta (expanded), Early Access,
+    Full Launch. Should provide specific tactics for each phase. Should recommend building
+    up the audience before launch day. Should include a launch day checklist.'
+  tags:
+  - launch-execute
+  - imported
+- id: saas-launch-execute-02
+  department: saas
+  prompt: We want to launch on Product Hunt. Any tips? We've never done it before.
+  expected_properties:
+  - Applies Product Hunt strategy section
+  - Covers timing (day and time selection)
+  - Covers asset preparation
+  - Addresses hunter network and supporter activation
+  - Recommends preparation timeline
+  - Mentions common mistakes to avoid
+  - Sets realistic expectations
+  rubric: 'Should apply the Product Hunt strategy section. Should cover: choosing the right
+    day and time, preparing assets (logo, gallery images, maker video), crafting the tagline
+    and description, building a hunter network, activating supporters on launch day, engaging
+    with comments, and post-launch follow-up. Should recommend preparation timeline (start
+    2-4 weeks before). Should mention common mistakes to avoid. Should set realistic expectations
+    about outcomes.'
+  tags:
+  - launch-execute
+  - imported
+- id: saas-launch-execute-03
+  department: saas
+  prompt: we just shipped a major feature update. how should we announce it? it's not a full
+    product launch, just a big new feature.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies ongoing launch strategy / update matrix
+  - Identifies as major feature update
+  - Scales tactics appropriately (not full launch)
+  - Recommends announcement channels
+  - Includes email, blog, social, and in-app notification
+  - Provides feature announcement framework
+  rubric: 'Should trigger on casual phrasing. Should apply the ongoing launch strategy section,
+    specifically the major/medium/minor update matrix. Should identify this as a major feature
+    update. Should recommend appropriate channels and tactics for a feature launch (less than
+    a full product launch but more than a changelog entry). Should include: announcement email,
+    blog post, social media push, in-app notification, and possibly a mini Product Hunt launch.
+    Should provide a feature announcement framework.'
+  tags:
+  - launch-execute
+  - imported
+- id: saas-launch-execute-04
+  department: saas
+  prompt: Our launch flopped. We launched 3 weeks ago and only got 50 signups. We expected
+    at least 500. What went wrong and what can we do now?
+  expected_properties:
+  - Applies post-launch product marketing guidance
+  - Diagnoses potential failure causes
+  - Addresses pre-launch audience building gap
+  - Recommends post-launch recovery tactics
+  - Suggests analyzing which channels produced signups
+  - Provides specific recovery plan
+  rubric: 'Should apply the post-launch product marketing section. Should diagnose potential
+    failure causes: insufficient audience building pre-launch, wrong channels, weak value
+    proposition messaging, poor launch execution, targeting the wrong audience. Should recommend
+    post-launch recovery tactics: iterate on messaging, identify which channels produced the
+    50 signups and double down, try new distribution channels, leverage early users for testimonials.
+    Should provide a specific 30-day recovery plan.'
+  tags:
+  - launch-execute
+  - imported
+- id: saas-launch-execute-05
+  department: saas
+  prompt: How do we leverage partnerships and borrowed audiences for our launch? We don't
+    have a big audience of our own.
+  expected_properties:
+  - Focuses on Borrowed channel from ORB Framework
+  - Provides specific borrowed audience tactics
+  - Mentions partnerships, communities, guest content
+  - Recommends how to identify and approach partners
+  - Notes borrowed strategies take time to build
+  - Suggests starting well before launch day
+  rubric: 'Should focus on the Borrowed channel from the ORB Framework. Should provide specific
+    borrowed audience tactics: podcast guest appearances, co-marketing with complementary
+    tools, influencer partnerships, community engagement (relevant Slack groups, Discord servers,
+    Reddit), guest posts, cross-promotions. Should recommend how to identify and approach
+    potential partners. Should note that borrowed audience strategies take time to build and
+    should start well before launch day.'
+  tags:
+  - launch-execute
+  - imported
+- id: saas-launch-execute-06
+  department: saas
+  prompt: Give me some creative marketing ideas to promote our product. We're bootstrapped
+    and don't have a big budget.
+  expected_properties:
+  - Recognizes this as broader marketing ideas request
+  - References or defers to marketing-ideas skill
+  - Does not attempt full marketing brainstorm using launch strategy patterns
+  - May provide some launch-related tactical ideas
+  rubric: Should recognize this is a broader marketing ideas request, not specifically a launch
+    strategy task. Should defer to or cross-reference the marketing-ideas skill, which provides
+    139 marketing ideas organized by category and filtered by budget. May provide some launch-related
+    tactical ideas but should make clear that marketing-ideas is the right skill for a broader
+    brainstorming session.
+  tags:
+  - launch-execute
+  - imported
+- id: saas-onboarding-optimize-01
+  department: saas
+  prompt: Help me optimize our onboarding flow. We have a project management tool and only
+    30% of trial users create their first project within the first week. We need to get them
+    to value faster.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Defines the activation/aha moment
+  - Evaluates time-to-value
+  - Recommends onboarding flow approach
+  - Applies checklist pattern with 3-7 items
+  - Addresses empty states as opportunities
+  - Provides experiment ideas
+  - Includes measurement metrics
+  rubric: Should check for product-marketing.md first. Should start by defining the activation/aha
+    moment — in this case, creating a first project. Should evaluate the current time-to-value
+    and identify friction points. Should recommend an onboarding flow approach (product-first,
+    guided setup, or value-first). Should apply the checklist pattern (3-7 items for onboarding
+    completion). Should address empty states as opportunities to guide users. Should provide
+    experiment ideas for testing improvements. Should include measurement metrics.
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-onboarding-optimize-02
+  department: saas
+  prompt: What should our onboarding checklist include? We're a design collaboration tool.
+    Users need to upload a design, invite a team member, and leave a comment to get full value.
+  expected_properties:
+  - Applies checklist pattern
+  - Includes the 3 stated activation actions
+  - Limits to 3-7 total items
+  - Orders by increasing commitment
+  - Starts with quickest win
+  - Recommends progress indicators
+  - Addresses skipped items
+  - Provides UX recommendations
+  rubric: Should apply the checklist pattern. Should include the 3 stated activation actions
+    (upload design, invite team, leave comment). Should recommend 3-7 total items ordered
+    by increasing commitment. Should suggest starting with the quickest win to build momentum.
+    Should recommend progress indicators and completion rewards. Should address what happens
+    when users skip items. Should provide specific UX recommendations for the checklist implementation.
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-onboarding-optimize-03
+  department: saas
+  prompt: our users sign up but then never come back. like 50% don't even log in a second
+    time. what do we do?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies stalled users framework
+  - Identifies potential root causes for drop-off
+  - Recommends first-session experience improvements
+  - Suggests multi-channel onboarding
+  - Cross-references emails for re-engagement
+  - Provides specific re-engagement triggers
+  rubric: 'Should trigger on casual phrasing. Should address this as a stalled users problem.
+    Should apply the handling stalled users framework: identify drop-off points, re-engagement
+    triggers, multi-channel outreach (email, in-app, push). Should investigate root causes:
+    is the first-run experience too complex? Is value not immediately apparent? Is the setup
+    too long? Should recommend immediate improvements to the first session experience. Should
+    suggest multi-channel onboarding (email sequences to bring them back). Should cross-reference
+    emails for re-engagement emails.'
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-onboarding-optimize-04
+  department: saas
+  prompt: How do we handle the empty state when a new user first logs in? Right now they just
+    see a blank dashboard.
+  expected_properties:
+  - Applies empty states as opportunities guidance
+  - Recommends alternatives to blank dashboard
+  - Suggests sample data or templates
+  - Provides clear first action CTA
+  - Addresses blank canvas paralysis
+  - Provides specific empty state design recommendations
+  rubric: 'Should apply the empty states as opportunities guidance. Should recommend turning
+    the blank dashboard into a guided experience: sample data to show what the product looks
+    like populated, a clear first action CTA, contextual tips, or a quick-start wizard. Should
+    provide specific recommendations for empty state design: what to show, what action to
+    prompt, how to reduce the ''blank canvas paralysis.'' Should reference patterns by product
+    type if applicable.'
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-onboarding-optimize-05
+  department: saas
+  prompt: Should we use tooltips, a product tour, or a setup wizard for onboarding? What works
+    best?
+  expected_properties:
+  - Compares tooltips, product tours, and setup wizards
+  - Explains when each works best
+  - Notes that combination approaches often work
+  - Provides best practices for each
+  - Addresses tooltip fatigue and tour length
+  - Recommends testing different approaches
+  rubric: 'Should apply the tooltips/guided tours guidance. Should compare the approaches:
+    tooltips (contextual, on-demand, less intrusive), product tours (guided walkthrough, can
+    overwhelm), setup wizards (structured, ensures key setup steps). Should recommend based
+    on product complexity and onboarding goals. Should note that the best approach often combines
+    elements. Should provide best practices for each: tooltip fatigue avoidance, tour length
+    limits, wizard step count. Should recommend testing different approaches.'
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-onboarding-optimize-06
+  department: saas
+  prompt: Our signup form has 8 fields and people keep dropping off. Can you help us fix the
+    signup flow?
+  expected_properties:
+  - Recognizes this as signup flow optimization, not onboarding
+  - References or defers to signup skill
+  - Explains that onboarding covers post-signup
+  - Does not attempt signup form redesign using onboarding patterns
+  rubric: Should recognize this is a signup flow optimization task, not post-signup onboarding.
+    Should defer to or cross-reference the signup skill, which handles signup form optimization,
+    field reduction, and registration flow design. Onboarding-cro covers what happens after
+    signup. Should make this distinction clear.
+  tags:
+  - onboarding-optimize
+  - imported
+- id: saas-paywall-design-01
+  department: saas
+  prompt: Help me design the upgrade paywall for our project management tool. Free users can
+    have 3 projects, and we want to show an upgrade screen when they try to create a 4th project.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies as usage limit trigger
+  - Applies paywall screen components framework
+  - Includes headline, value demo, comparison, social proof, CTA
+  - Provides specific copy recommendations
+  - Addresses user's emotional state at the limit
+  - Includes escape hatch option
+  - Warns against anti-patterns
+  rubric: 'Should check for product-marketing.md first. Should identify this as a usage limit
+    trigger point. Should apply the paywall screen components: headline (communicate the value
+    of upgrading, not just the limit), value demonstration (show what they get with paid plan),
+    plan comparison (free vs paid), social proof, CTA (specific and action-oriented), and
+    escape hatch (option to go back). Should provide specific copy recommendations. Should
+    address the emotional state of the user at this moment (frustrated by the limit). Should
+    warn against anti-patterns.'
+  tags:
+  - paywall-design
+  - imported
+- id: saas-paywall-design-02
+  department: saas
+  prompt: Our free trial expires in 14 days and users see a generic 'Your trial has expired'
+    screen. Upgrade rate from this screen is only 2%. How do we improve it?
+  expected_properties:
+  - Identifies as trial expiration trigger
+  - Applies trial expiration paywall guidance
+  - Recommends showing user's accomplishments during trial
+  - Uses loss framing (what they'd lose)
+  - Provides clear plan options
+  - Includes social proof
+  - Diagnoses why current 2% rate is low
+  - Provides specific redesign recommendations
+  rubric: 'Should identify this as a trial expiration trigger. Should apply the trial expiration
+    paywall type guidance. Should recommend: show what they''ve built/accomplished during
+    the trial (endowment effect), highlight specific features they used, show the value they''d
+    lose, provide clear plan options, include social proof from similar users who upgraded.
+    Should diagnose why 2% is low: likely a weak value prop, no personalization, no urgency
+    or loss framing. Should provide specific redesign recommendations.'
+  tags:
+  - paywall-design
+  - imported
+- id: saas-paywall-design-03
+  department: saas
+  prompt: when should we show upgrade prompts? we don't want to be annoying but we also need
+    to convert free users to paid.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies timing and frequency rules
+  - Recommends specific trigger points
+  - Addresses frequency capping
+  - Warns against anti-patterns
+  - Balances user experience with conversion goals
+  - Provides specific recommendations for each trigger type
+  rubric: 'Should trigger on casual phrasing. Should apply the timing and frequency rules.
+    Should recommend trigger points from the skill: feature gates (when they try a paid feature),
+    usage limits (when they hit a threshold), value moments (when they''ve just experienced
+    success), and natural transition points. Should address frequency capping to avoid being
+    annoying. Should recommend the anti-patterns to avoid (blocking basic functionality, too
+    frequent popups, dark patterns). Should provide a balanced approach that respects user
+    experience while driving upgrades.'
+  tags:
+  - paywall-design
+  - imported
+- id: saas-paywall-design-04
+  department: saas
+  prompt: Design a feature gate paywall. When free users click on 'Advanced Analytics' in
+    our dashboard, we want to show them an upgrade prompt.
+  expected_properties:
+  - Identifies as feature gate trigger
+  - Applies feature lock paywall guidance
+  - Recommends showing preview of the feature
+  - Explains specific benefit of the feature
+  - Includes relevant plan comparison
+  - Provides clear CTA and escape hatch
+  - Provides copy recommendations
+  rubric: 'Should identify this as a feature gate trigger. Should apply the feature lock paywall
+    type guidance. Should recommend: show a preview or screenshot of the advanced analytics
+    feature, explain the specific benefit (not just ''this is a paid feature''), include a
+    plan comparison relevant to analytics, provide a clear CTA to upgrade, and include an
+    escape hatch to go back to basic analytics. Should recommend showing what insights they''re
+    missing. Should provide copy recommendations for the paywall screen.'
+  tags:
+  - paywall-design
+  - imported
+- id: saas-paywall-design-05
+  department: saas
+  prompt: What are common mistakes to avoid with in-app paywalls? I don't want to be pushy
+    or make users feel tricked.
+  expected_properties:
+  - Applies anti-patterns section
+  - Covers dark patterns to avoid
+  - Covers conversion killers
+  - Covers frequency issues
+  - Provides positive alternatives for each
+  - Emphasizes helpful over pushy approach
+  rubric: 'Should apply the anti-patterns section. Should cover: dark patterns (making it
+    hard to find the close button, confusing opt-out language), conversion killers (blocking
+    basic functionality, showing paywalls too early before value is demonstrated, no escape
+    hatch), frequency issues (too many prompts, showing the same paywall repeatedly). Should
+    provide positive alternatives for each anti-pattern. Should emphasize that good paywalls
+    feel helpful, not pushy.'
+  tags:
+  - paywall-design
+  - imported
+- id: saas-paywall-design-06
+  department: saas
+  prompt: Can you help me optimize our public pricing page? We want more visitors to choose
+    the Pro plan over the Basic plan.
+  expected_properties:
+  - Recognizes this as public pricing page optimization
+  - References or defers to cro skill
+  - Explains that paywalls is for in-app upgrade prompts
+  - Does not attempt public pricing page optimization
+  rubric: Should recognize this is a public pricing page optimization task, not an in-app
+    paywall task. Should defer to or cross-reference the cro skill for pricing page CRO. Paywall-upgrade-cro
+    specifically handles in-app upgrade prompts for existing users, not public-facing pricing
+    pages.
+  tags:
+  - paywall-design
+  - imported
+- id: saas-pricing-strategy-01
+  department: saas
+  prompt: Help me figure out pricing for our new SaaS product. It's a customer support platform
+    for e-commerce stores. We're not sure whether to charge per agent, per ticket, or flat
+    rate. Currently thinking $49-199/month range.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies three pricing axes framework
+  - Evaluates multiple pricing metrics
+  - Discusses which metric aligns with value delivered
+  - Recommends good-better-best tier structure
+  - Addresses pricing psychology
+  - Provides specific pricing recommendation with rationale
+  rubric: 'Should check for product-marketing.md first. Should apply the three pricing axes
+    framework: packaging (what''s included in each tier), pricing metric (per agent, per ticket,
+    flat rate — evaluate each), price point ($49-199 range evaluation). Should discuss value
+    metrics and which aligns best with value delivered (per agent is common in support, but
+    per ticket aligns with usage). Should recommend a good-better-best tier structure. Should
+    address pricing psychology. Should provide a specific pricing recommendation with rationale.'
+  tags:
+  - pricing-strategy
+  - imported
+- id: saas-pricing-strategy-02
+  department: saas
+  prompt: We want to raise our prices by 30%. We've been at $29/month for 2 years and we've
+    added a lot of features. How do we do this without losing customers?
+  expected_properties:
+  - Applies price increase strategies
+  - Recommends grandfathering or grace period approach
+  - Recommends tying increase to new value
+  - Provides communication strategy
+  - Addresses new vs existing customer timing
+  - Suggests annual billing as softening measure
+  - Notes some churn is expected
+  rubric: 'Should apply the ''when to raise prices'' and price increase strategies sections.
+    Should recommend a strategy: grandfather existing customers (or give them a grace period),
+    tie the increase to new value, communicate the change clearly with advance notice, consider
+    an annual billing discount as a softening measure. Should address different approaches
+    (immediate for new customers, delayed for existing). Should recommend specific communication
+    strategy. Should note that some churn is expected and acceptable.'
+  tags:
+  - pricing-strategy
+  - imported
+- id: saas-pricing-strategy-03
+  department: saas
+  prompt: how do we figure out what people will actually pay? we're launching a new product
+    and have no idea what to charge.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies Van Westendorp price sensitivity method
+  - Applies MaxDiff for feature importance
+  - Recommends competitive benchmarking
+  - Explains how to run each method
+  - Suggests practical alternatives (customer interviews, competitive analysis)
+  - Provides executable pricing research plan
+  rubric: 'Should trigger on casual phrasing. Should apply the pricing research methods: Van
+    Westendorp price sensitivity analysis (too cheap, bargain, expensive, too expensive),
+    MaxDiff for feature importance, competitive benchmarking. Should explain how to run each
+    method. Should also recommend simpler approaches: talking to potential customers, analyzing
+    competitor pricing, testing different price points. Should provide a practical pricing
+    research plan they can execute.'
+  tags:
+  - pricing-strategy
+  - imported
+- id: saas-pricing-strategy-04
+  department: saas
+  prompt: We have a Basic ($19), Pro ($49), and Enterprise (custom) plan. The Pro plan gets
+    70% of signups. Should we add a plan between Pro and Enterprise?
+  expected_properties:
+  - Applies good-better-best tier structure
+  - Analyzes current tier performance
+  - Evaluates whether 4th tier addresses real gap
+  - Considers choice paralysis risk
+  - Applies pricing psychology (Hick's Law)
+  - Provides specific recommendation with rationale
+  rubric: 'Should apply the good-better-best tier structure framework. Should analyze the
+    current situation: Pro capturing 70% is actually healthy, but the gap to Enterprise suggests
+    there may be mid-market customers underserved. Should evaluate whether a 4th tier makes
+    sense: does it address a real gap, or will it create choice paralysis? Should apply pricing
+    psychology (Hick''s Law — more options can reduce decisions). Should recommend either
+    a 4th tier with clear differentiation or adjusting the Pro plan to better bridge the gap.'
+  tags:
+  - pricing-strategy
+  - imported
+- id: saas-pricing-strategy-05
+  department: saas
+  prompt: What pricing psychology tactics should we use on our pricing page? We want the $79
+    plan to be the most popular.
+  expected_properties:
+  - Applies pricing psychology tactics
+  - Applies anchoring effect
+  - Applies decoy effect or visual emphasis
+  - Applies charm pricing or Rule of 100
+  - Provides specific pricing page recommendations
+  - Cross-references cro or marketing-psychology
+  rubric: 'Should apply the pricing psychology section: anchoring (show the $79 plan next
+    to a higher-priced plan), decoy effect (make the lower plan look less valuable), visual
+    emphasis (highlight or ''recommend'' the $79 plan), charm pricing ($79 vs $80), Rule of
+    100 (percentage discounts below $100, dollar discounts above), loss framing (show what
+    lower plans miss). Should provide specific pricing page design recommendations. Should
+    cross-reference cro for broader pricing page optimization.'
+  tags:
+  - pricing-strategy
+  - imported
+- id: saas-pricing-strategy-06
+  department: saas
+  prompt: Our pricing page conversion rate is only 1.5%. Can you review the page and suggest
+    improvements?
+  expected_properties:
+  - Recognizes this as pricing page CRO, not pricing strategy
+  - References or defers to cro skill
+  - Explains that pricing is about pricing decisions
+  - Does not attempt full page CRO audit
+  rubric: Should recognize this is a pricing page conversion optimization task, not a pricing
+    strategy task. Should defer to or cross-reference the cro skill, which handles pricing
+    page conversion rate optimization including plan comparison clarity, CTA optimization,
+    and trust signals. Pricing-strategy focuses on the actual pricing decisions (what to charge,
+    how to package), not the page design.
+  tags:
+  - pricing-strategy
+  - imported
+# --- END imported ---