@jairodri/huckleberry-cli 1.0.1 → 1.1.0

package/skills/saas-product-seo/SKILL.md

@@ -0,0 +1,324 @@
+---
+name: saas-product-seo
+description: SEO system for SaaS products targeting features, comparisons, and B2B buyers.
+---
+
+# Skill: SaaS Product SEO
+
+## Overview
+
+SaaS-focused SEO system for ai.withjai and similar product businesses. Unlike local SEO (GBP, citations, service areas), SaaS SEO targets: product features, comparison content, developer adoption, and B2B buyer journey.
+
+## When to Use
+
+- SaaS/automation products with feature pages and pricing
+- Developer tools and APIs
+- Product-led content marketing (tutorials, case studies, documentation)
+- Competitor comparison pages (Product A vs Product B)
+- Building authority in SaaS ecosystem (directories, reviews, integrations)
+
+## Core Value Proposition
+
+**Problem:** Most SaaS companies do generic SEO or borrow local SEO tactics (GMB, citations, service areas) that don't apply to software products.
+
+**Solution:** Systematic SaaS SEO that targets:
+1. **Product Keywords:** Feature names, use cases, integrations
+2. **Comparison SEO:** "X vs Y" pages, feature comparison tables
+3. **Technical Content:** Developer docs, API guides, integration tutorials
+4. **Authority Signals:** SaaS directories, product reviews, tool mentions
+5. **Buyer Journey:** Problem-aware → comparison → decision → integration
+
+---
+
+## Quick Start
+
+```bash
+# Load business context (adapted for SaaS model)
+node scripts/seo/load-business-context.js --brand ai.withjai --interactive
+
+# Run SaaS-specific SEO prompts
+node scripts/seo/saas-prompts/run-prompt.js --prompt 1 --brand ai.withjai
+```
+
+---
+
+## Prompt System (10 Prompts)
+
+### Phase 1: Foundation (Weeks 1-2)
+**Prompt 0: SaaS Business Context Loader**
+- Load product details, features, pricing, target customers
+- Identify key product differentiators
+- Map buyer journey stages (problem-aware → evaluation → adoption)
+
+**Prompt 1: Product Keyword Research**
+- Extract product keywords from: feature names, use cases, integrations, problems solved
+- Identify competitor ranking for these product keywords
+- Prioritize by: (1) Your unique features, (2) High-intent comparison searches
+
+**Prompt 2: Competitor Product Analysis**
+- Analyze competitor pricing pages, feature lists, case studies
+- Extract: Value propositions, messaging angles, feature positioning
+- Identify gaps: Features competitors don't highlight that you should
+
+### Phase 2: Content Foundation (Weeks 3-5)
+**Prompt 3: Comparison Page Strategy**
+- Build "ai.withjai vs Make.com" framework
+- Create comparison tables for all major competitors
+- Generate content briefs for: Feature vs feature, pricing vs pricing, use case vs use case
+
+**Prompt 4: Feature Page Optimization**
+- Optimize product feature pages (e.g., "Newsletter Automation" page)
+- Structure: Problem → Feature → Benefit → Use Case → CTA
+- Include: Feature screenshots, integrations, pricing anchors
+
+**Prompt 5: Technical Content Strategy**
+- Identify developer-facing content opportunities:
+  - API documentation and guides
+  - Integration tutorials
+  - Developer use cases
+  - Code examples
+- Build content calendar targeting technical keywords
+
+### Phase 3: Authority Building (Weeks 6-7)
+**Prompt 6: SaaS Directory Audit**
+- Research SaaS/product directories:
+  - G2, Product Hunt, Capterra
+  - Capterra, Trustpilot, SoftwareAdvice
+  - Niche directories (newsletter automation, etc.)
+- Check: Listings exist, NAP consistency, reviews, feature descriptions
+- Build submission prioritized list
+
+**Prompt 7: Backlink Gap Analysis**
+- Use Ahrefs to find:
+  - Backlinks to Make.com, Zapier, Automation Anywhere
+  - SaaS blog mentions (features, integrations)
+  - Tool directory listings
+- Identify: High-value targets, low-hanging fruit
+- Build 90-day outreach plan
+
+**Prompt 8: Product Review Strategy**
+- Research how competitors collect and showcase reviews:
+  - G2 reviews, Trustpilot, Capterra screenshots
+  - Social proof on pricing pages
+  - Case study testimonials
+- Build review collection system + showcase strategy
+
+### Phase 4: Competitive Intelligence (Weeks 8-10)
+**Prompt 9: Competitor Content Audit**
+- Analyze competitor blog content strategy:
+  - Topics covered (features, use cases, comparisons)
+  - Content formats (tutorials, case studies, product updates)
+  - Publishing frequency and cadence
+  - Social distribution of blog content
+- Identify gaps: Topics they don't cover (your opportunity)
+
+**Prompt 10: Product Positioning Map**
+- Map competitor positioning across dimensions:
+  - Price point (budget, mid-market, premium)
+  - Feature focus (comprehensive vs specialized vs minimal)
+  - Target audience (enterprise vs SMB vs indie)
+  - Brand voice (technical vs playful vs enterprise)
+- Identify: Unoccupied positioning territory (your competitive advantage)
+
+---
+
+## Business Context Structure
+
+**File:** `businesses/{business}/seo/business-context.json`
+
+```json
+{
+  "business_basics": {
+    "name": "[product name]",
+    "address": "Remote/Digital-first",
+    "phone": "[contact if applicable]",
+    "website": "[website URL]",
+    "years_in_business": "[X years]",
+    "team_size": "[solo / small team / large team]"
+  },
+  "product_market": {
+    "primary_category": "SaaS - Newsletter Automation",
+    "product_type": "B2B SaaS with freemium",
+    "target_customer": "Digital entrepreneurs, indie builders, AI-forward creators",
+    "average_revenue_per_customer": "$X/month",
+    "pricing_model": "Monthly subscription: [starter, growth, enterprise]"
+  },
+  "product_differentiators": [
+    "[unique feature 1]",
+    "[unique feature 2]",
+    "[unique feature 3]"
+  ],
+  "seo_goals": {
+    "top_keywords": [
+      "[primary product keyword]",
+      "[secondary product keyword]",
+      "[competitor comparison keyword]"
+    ],
+    "currently_rank_for": [
+      "[keyword 1]",
+      "[keyword 2]"
+    ],
+    "should_rank_but_dont": [
+      "[opportunity keyword 1]",
+      "[opportunity keyword 2]"
+    ]
+  },
+  "competitors": [
+    {
+      "name": "Competitor Name",
+      "website": "https://competitor.com",
+      "product_type": "[SaaS / automation tool]",
+      "pricing": "[budget / mid-market / premium]",
+      "why_they_beat_you": "[strength analysis]"
+    }
+  ],
+  "current_standings": {
+    "organic_traffic": "[monthly organic traffic]",
+    "top_ranking_pages": "[top pages by traffic]",
+    "conversion_rate": "[free trial to paid conversion %]",
+    "biggest_seo_problem": "[honest assessment]"
+  }
+}
+```
+
+---
+
+## Success Metrics
+
+**90-Day Targets (Per Brand):**
+- Product keyword rankings: +5 top 10 positions
+- Comparison traffic: 40-60% increase
+- Backlink profile: +5-10 quality SaaS links
+- SaaS directory listings: 10+ new listings
+- Product reviews showcased: 20+ reviews on site
+
+### Proof Points
+- Comparison pages → higher CTR for research-stage keywords
+- Technical content → developer trust and backlinks
+- SaaS directories → authority signals in product niche
+- Product positioning → stand out from crowded market
+
+---
+
+## Key Advantages Over Local SEO System
+
+| Aspect | Local SEO (Sarvesh) | SaaS Product SEO |
+|--------|---------------------|------------------|
+| **Keywords** | Service + city | Product features + comparisons |
+| **Pages** | Service + city location | Feature pages, comparison pages |
+| **Authority** | GBP reviews, local citations | SaaS directories, product reviews |
+| **Content** | Neighborhood-specific | Technical, tutorials, case studies |
+| **Target** | Local homeowners | Digital entrepreneurs, developers |
+| **Competition** | Local service businesses | Other SaaS products |
+| **Timeline** | 7-14 days (local intent) | 90+ days (SaaS consideration) |
+
+---
+
+## Implementation
+
+### Scripts
+
+**Directory:** `scripts/seo/saas-prompts/`
+
+**Prompt Runner:** `run-prompt.js` (reuses existing structure)
+- Loads SaaS business context
+- Executes prompt from prompt library
+- Tracks execution log
+
+**Business Context:** Adapted for SaaS model
+- Removed GBP-specific fields
+- Added product differentiators
+- Replaced services with product categories
+- Updated goals for product keywords
+
+---
+
+## Integration with Existing Workflows
+
+**Connects to:**
+- `content-pipeline-complete` - Use comparison page briefs for blog posts
+- `platform-content-generator` - Distribute SaaS-focused content
+- `publishing-blog-articles` - Create optimized feature pages
+- `analytics-tracking` - Track product keyword rankings
+
+**Complementary Skills:**
+- `developing-seo-strategy` - Product-focused keyword research
+- `schema-markup` - SoftwareApplication schema for product pages
+- `seo-audit` - Technical SEO validation
+
+---
+
+## Common Mistakes to Avoid
+
+- ❌ Using local SEO tactics for SaaS products (GMB, citations, service areas)
+- ❌ Ignoring competitor comparison opportunities (huge traffic source)
+- ❌ Not creating feature-specific pages (e.g., "Newsletter Automation" vs generic "Features" page)
+- ❌ Missing technical content (developers need docs, not just benefits)
+- ❌ Forgetting SaaS directories (G2, Product Hunt, Capterra matter)
+- ❌ Not showcasing product reviews and social proof
+
+---
+
+## Example: ai.withjai Comparison Strategy
+
+**Competitor:** Make.com
+
+**Comparison Page Structure:**
+1. Hero section: "ai.withjai vs Make.com: Which Newsletter Automation Platform is Right for You?"
+2. Feature comparison table: Core features with checkmarks
+3. Pricing comparison: Starter plans side-by-side
+4. Use case section: Real newsletter examples from each platform
+5. Differentiators: "Why ai.withjai for [specific user type]"
+6. CTA: "Start free trial and compare side-by-side"
+
+**Keywords Targeted:**
+- "newsletter automation tool"
+- "make.com alternatives"
+- "best ai newsletter tool"
+- "newsletter platform comparison"
+- "ai.withjai vs make.com"
+
+---
+
+## Resources
+
+### SaaS Directories
+- G2: https://www.g2.com/
+- Product Hunt: https://www.producthunt.com/
+- Capterra: https://www.capterra.com/
+- Trustpilot: https://www.trustpilot.com/
+- SoftwareAdvice: https://www.softwareadvice.com/
+- Capterra: https://www.capterra.com/
+
+### Competitor Research Tools
+- SimilarWeb: https://www.similarweb.com/
+- BuiltWith: https://www.builtwith.com/
+- G2 StackShare: https://stackshare.io/
+
+### Schema Markup
+- SoftwareApplication: https://schema.org/SoftwareApplication
+- TechArticle: https://schema.org/TechArticle
+- HowTo: https://schema.org/HowTo
+
+---
+
+## Support
+
+### Getting Started
+1. Run SaaS business context loader with interactive mode
+2. Execute prompts 1-2 first (foundation)
+3. Review outputs and adjust context if needed
+4. Continue through phases systematically
+5. Use monthly performance tracking to measure results
+
+### Questions
+- For implementation help: Check scripts/seo/saas-prompts/
+- For prompt customization: Review business context structure
+- For integration guidance: See "Integration with Existing Workflows" section
+
+---
+
+**System Status:** ✅ Designed | 📊 SaaS-Focused | 🎯 10 Proven Prompts | 💰 Competitor-First
+
+**Last Updated:** 2026-03-25
+**Philosophy:** Don't force local SEO system onto SaaS business model. Build system that matches your customers, competitors, and content reality.

package/skills/sales-enablement/SKILL.md

@@ -0,0 +1,349 @@
+---
+name: sales-enablement
+description: Create sales collateral, pitch decks, one-pagers, and demo scripts.
+metadata:
+  version: 1.1.0
+---
+
+# Sales Enablement
+
+You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals.
+
+## Before Starting
+
+**Check for brand-specific assets in businesses/{business}/brand/ first:**
+If `businesses/{business}/brand/` exists (or `businesses/{business}/brand/` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+1. **Value Proposition & Differentiators**
+   - What do you sell and who is it for?
+   - What makes you different from the next best alternative?
+   - What outcomes can you prove?
+
+2. **Sales Motion**
+   - How do you sell? (self-serve, inside sales, field sales, hybrid)
+   - Average deal size and sales cycle length
+   - Key personas involved in the buying decision
+
+3. **Collateral Needs**
+   - What specific assets do you need?
+   - What stage of the funnel are they for?
+   - Who will use them? (AE, SDR, champion, prospect)
+
+4. **Current State**
+   - What materials exist today?
+   - What's working and what's not?
+   - What do reps ask for most?
+
+---
+
+## Core Principles
+
+### Sales Uses What Sales Trusts
+Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first.
+
+### Situation-Specific, Not Generic
+Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show.
+
+### Scannable Over Comprehensive
+Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.
+
+### Tie Back to Business Outcomes
+Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%."
+
+---
+
+## Sales Deck / Pitch Deck
+
+### 10-12 Slide Framework
+
+1. **Current World Problem** — The pain your buyer lives with today
+2. **Cost of the Problem** — What inaction costs (time, money, risk)
+3. **The Shift Happening** — Market or technology change creating urgency
+4. **Your Approach** — How you solve it differently
+5. **Product Walkthrough** — 3-4 key workflows, not a feature tour
+6. **Proof Points** — Metrics, logos, analyst recognition
+7. **Case Study** — One customer story told well
+8. **Implementation / Timeline** — How they get from here to live
+9. **ROI / Value** — Expected return and payback period
+10. **Pricing Overview** — Transparent, tiered if applicable
+11. **Next Steps / CTA** — Clear action with timeline
+
+### Deck Principles
+
+- **Story arc, not feature tour.** Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there.
+- **One idea per slide.** If you need two points, use two slides.
+- **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals.
+
+### Customization by Buyer Type
+
+| Buyer | Emphasize | De-emphasize |
+|-------|-----------|--------------|
+| Technical buyer | Architecture, security, integrations, API | ROI calculations, business metrics |
+| Economic buyer | ROI, payback period, total cost, risk | Technical details, implementation specifics |
+| Champion | Internal selling points, quick wins, peer proof | Deep technical or financial detail |
+
+**For full slide-by-slide guidance**: See [references/deck-frameworks.md](references/deck-frameworks.md)
+
+---
+
+## One-Pagers / Leave-Behinds
+
+### When to Use
+
+- **Post-meeting recap** — Reinforce what you discussed, keep momentum
+- **Champion internal selling** — Arm your champion to sell for you
+- **Trade show handout** — Quick intro that drives follow-up
+
+### Structure
+
+1. **Problem statement** — The pain in one sentence
+2. **Your solution** — What you do and how
+3. **3 differentiators** — Why you vs. alternatives
+4. **Proof point** — One strong metric or customer quote
+5. **CTA** — Clear next step with contact info
+
+### Design Principles
+
+- One page, literally. Front only, or front and back maximum.
+- Scannable in 30 seconds. Bold headers, short bullets, whitespace.
+- Include your logo, website, and a specific contact (not info@).
+- Match your brand but keep it clean — this is a sales tool, not a brand piece.
+
+**For templates by use case**: See [references/one-pager-templates.md](references/one-pager-templates.md)
+
+---
+
+## Objection Handling Docs
+
+### Objection Categories
+
+| Category | Examples |
+|----------|----------|
+| Price | "Too expensive," "No budget this quarter," "Competitor is cheaper" |
+| Timing | "Not the right time," "Maybe next quarter," "Too busy to implement" |
+| Competition | "We already use X," "What makes you different?" |
+| Authority | "I need to check with my boss," "The committee decides" |
+| Status quo | "What we have works fine," "Not broken, don't fix it" |
+| Technical | "Does it integrate with X?," "Security concerns," "Can it scale?" |
+
+### Response Framework
+
+For each objection, document:
+
+1. **Objection statement** — Exactly how reps hear it
+2. **Why they say it** — The real concern behind the words
+3. **Response approach** — How to acknowledge and redirect
+4. **Proof point** — Specific evidence that addresses the concern
+5. **Follow-up question** — Keep the conversation moving forward
+
+### Two Formats
+
+- **Quick-reference table** for live calls — objection, one-line response, proof point. Fits on one screen.
+- **Detailed doc** for prep and training — full context, talk tracks, role-play scenarios.
+
+**For the full objection library**: See [references/objection-library.md](references/objection-library.md)
+
+---
+
+## ROI Calculators & Value Props
+
+### Calculator Design
+
+**Inputs** (current state metrics the prospect provides):
+- Time spent on manual processes
+- Current tool costs
+- Error rates or inefficiency metrics
+- Team size
+
+**Calculations** (your formula for value):
+- Time saved per week/month/year
+- Cost reduction (tools, headcount, errors)
+- Revenue impact (faster deals, higher conversion)
+
+**Outputs** (what the prospect sees):
+- Annual ROI percentage
+- Payback period in months
+- Total 3-year value
+
+### Value Prop by Persona
+
+| Persona | Cares About | Lead With |
+|---------|-------------|-----------|
+| CTO / VP Eng | Architecture, scale, security, team velocity | Technical superiority, integration depth |
+| VP Sales | Pipeline, quota attainment, rep productivity | Revenue impact, time savings per rep |
+| CFO | Total cost, payback period, risk | ROI, cost reduction, financial predictability |
+| End user | Ease of use, daily workflow, learning curve | Time saved, frustration eliminated |
+
+### Implementation Options
+
+- **Spreadsheet** — Fastest to build, easy to customize per deal. Works for inside sales.
+- **Web tool** — More polished, captures leads, scales better. Worth building if deal volume is high.
+- **Slide-based** — ROI story embedded in the deck. Good for executive presentations.
+
+---
+
+## Demo Scripts & Talk Tracks
+
+### Script Structure
+
+1. **Opening** (2 min) — Context setting, agenda, confirm goals for the call
+2. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities
+3. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain
+4. **Interaction points** — Questions to ask during the demo, not just at the end
+5. **Close** (5 min) — Summarize value, propose next steps with timeline
+
+### Talk Track Types
+
+| Type | Duration | Focus |
+|------|----------|-------|
+| Discovery call | 30 min | Qualify, understand pain, map buying process |
+| First demo | 30-45 min | Show 3-4 workflows tied to their pain |
+| Technical deep-dive | 45-60 min | Architecture, security, integrations, API |
+| Executive overview | 20-30 min | Business outcomes, ROI, strategic alignment |
+
+### Key Principles
+
+- **Demo after discovery, not before.** If you don't know their pain, you're guessing which features matter.
+- **Customize to their use case.** Use their terminology, their data (if possible), their workflow.
+- **Leave time for questions.** A demo where the prospect doesn't talk is a demo that doesn't close.
+
+**For full script templates**: See [references/demo-scripts.md](references/demo-scripts.md)
+
+---
+
+## Case Study Briefs (Sales Format)
+
+### How Sales Case Studies Differ
+
+Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.
+
+### Structure
+
+1. **Customer profile** — Industry, company size, buyer role
+2. **Challenge** — What they were struggling with (2-3 sentences)
+3. **Solution** — What they implemented (1-2 sentences)
+4. **Results** — 3 specific metrics (before/after)
+5. **Pull quote** — One sentence from the customer
+6. **Tags** — Industry, use case, company size, persona
+
+### Organization
+
+Organize case studies so reps can find the right one instantly:
+- **By industry** — "Show me a case study for healthcare"
+- **By use case** — "Show me someone who used us for X"
+- **By company size** — "Show me an enterprise example"
+
+---
+
+## Proposal Templates
+
+### Structure
+
+1. **Executive summary** — Their challenge, your solution, expected outcome (1 page max)
+2. **Proposed solution** — What you'll deliver, mapped to their requirements
+3. **Implementation plan** — Timeline, milestones, responsibilities
+4. **Investment** — Pricing, payment terms, what's included
+5. **Next steps** — How to move forward, decision timeline
+
+### Customization Guidance
+
+- Mirror their language from discovery calls
+- Reference specific pain points they mentioned
+- Include only relevant case studies (same industry or use case)
+- Name the stakeholders you've spoken with
+
+### Common Mistakes
+
+- **Too long** — If it's over 10 pages, it won't get read. Aim for 5-7.
+- **Too generic** — Templated proposals signal low effort. Customize the exec summary at minimum.
+- **Burying the price** — Don't make them hunt for it. Be transparent and confident.
+
+---
+
+## Sales Playbooks
+
+### What Goes in a Playbook
+
+- **Buyer profile** — Who you're selling to, their goals and pains
+- **Qualification criteria** — BANT, MEDDIC, or your framework
+- **Discovery questions** — Organized by topic, not a script
+- **Objection handling** — Top 10 objections with responses
+- **Competitive positioning** — How you win against each competitor
+- **Demo flow** — Recommended sequence for each persona
+- **Email templates** — Follow-up, proposal, check-in, breakup
+
+### When to Build
+
+- **New product launch** — Reps need a single source of truth
+- **New market segment** — Different buyers need different approaches
+- **New hire ramp** — Playbooks cut ramp time significantly
+
+### Keeping It Living
+
+Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots.
+
+---
+
+## Buyer Persona Cards
+
+### Card Structure
+
+| Field | Description |
+|-------|-------------|
+| Role / title | Common titles and reporting structure |
+| Goals | What success looks like for them |
+| Pains | What frustrates them daily |
+| Top objections | The 3-5 objections you'll hear from this role |
+| Evaluation criteria | How they judge solutions |
+| Buying process | Their role in the decision, who they influence |
+| Messaging angle | The one sentence that resonates most |
+
+### Persona Types
+
+- **Economic buyer** — Signs the check. Cares about ROI and risk.
+- **Technical buyer** — Evaluates the product. Cares about capabilities and integration.
+- **End user** — Uses it daily. Cares about ease and workflow fit.
+- **Champion** — Advocates internally. Needs ammunition to sell for you.
+- **Blocker** — Opposes the purchase. Understand their concern to neutralize it.
+
+---
+
+## Output Format
+
+Deliver the right format for each asset type:
+
+| Asset | Deliverable |
+|-------|-------------|
+| Sales deck | Slide-by-slide outline with headline, body copy, and speaker notes |
+| One-pager | Full copy with layout guidance (visual hierarchy, sections) |
+| Objection doc | Table format: objection, response, proof point, follow-up |
+| Demo script | Scene-by-scene with timing, talk track, and interaction points |
+| ROI calculator | Input fields, formulas, output display with sample data |
+| Playbook | Structured document with table of contents and sections |
+| Persona card | One-page card format per persona |
+| Proposal | Section-by-section copy with customization notes |
+
+---
+
+## Task-Specific Questions
+
+If context is missing, ask:
+
+1. What collateral do you need? (deck, one-pager, objection doc, etc.)
+2. Who will use it? (AE, SDR, champion, prospect)
+3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
+4. Who is the target persona? (title, seniority, department)
+5. What are the top 3 objections you hear most?
+
+---
+
+## Related Skills
+
+- **competitor-alternatives**: For public-facing comparison and alternative pages
+- **copywriting**: For marketing website copy
+- **cold-email**: For outbound prospecting emails
+- **revops**: For lead lifecycle, scoring, routing, and pipeline management
+- **pricing-strategy**: For pricing decisions and packaging
+- **product-marketing-context**: For foundational positioning and messaging