Initial commit

skills/enablement-kit/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: enablement-kit
+description: Use to package collateral, talk tracks, and systems guidance for routed
+  plays.
+---
+
+# Sales Handoff Enablement Kit Skill
+
+## When to Use
+- Launching new campaigns or lifecycle plays that generate routed leads.
+- Rolling out updated messaging, pricing, or objection handling for a segment.
+- Conducting retros where sales lacked context or assets to follow up effectively.
+
+## Framework
+1. **Context Brief** – campaign goal, ICP, offer, key insights, reference dashboards.
+2. **Talk Tracks & Scripts** – intro lines, discovery questions, objection responses, CTA guidance.
+3. **Collateral Pack** – links to decks, one-pagers, case studies, demos, ROI calculators.
+4. **System Instructions** – CRM workflows, sequence enrollment steps, data entry requirements.
+5. **Feedback Loop** – channel for reps to submit learnings, objections, and win stories.
+
+## Templates
+- One-page enablement brief (context, key messages, assets, KPIs).
+- Objection handling table (objection → response → proof).
+- Follow-up checklist (pre-call prep, talk track, assets to send, logging requirements).
+
+## Tips
+- Embed Loom or audio snippets to deliver tone and emphasis quickly.
+- Keep assets in a shared folder with versioning so RevOps can reference in audits.
+- Pair with `run-standups` command to remind reps of latest resources.
+
+---

skills/routing-logic/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: routing-logic
+description: Use when defining or adjusting marketing-to-sales assignment rules.
+---
+
+# Routing Logic Blueprint Skill
+
+## When to Use
+- Designing new lead assignment models (round-robin, territory, pod-based).
+- Troubleshooting misrouted or unassigned leads.
+- Simulating capacity scenarios before changing SLAs.
+
+## Framework
+1. **Qualification Criteria** – map scoring thresholds, enrichment fields, and required consent.
+2. **Owner Model** – hierarchy (account owner, named AE, SDR pod), fallback logic, and tie-breakers.
+3. **Capacity Modeling** – lead volume forecasts vs available headcount, backlog thresholds.
+4. **Automation Flow** – MAP/CRM steps, dedupe rules, webhook/API dependencies.
+5. **Monitoring & Audits** – logging, reconciliation jobs, sample QA cadence.
+
+## Templates
+- Routing matrix (segment → owner → conditions → escalation).
+- Capacity calculator (leads/day vs SLA vs reps).
+- QA checklist for automation updates.
+
+## Tips
+- Keep logic declarative (YAML/JSON) for easier audits and version control.
+- Add synthetic leads to test every path before go-live.
+- Coordinate with data enrichment to ensure required fields populate upstream.
+
+---

skills/sla-tracking/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: sla-tracking
+description: "Use to design measurement, alerting, and reporting for MQL\u2192SQL\
+  \ SLAs."
+---
+
+# SLA Tracking System Skill
+
+## When to Use
+- Establishing or revisiting SLA metrics between marketing, SDR, and sales pods.
+- Building dashboards/alerts for pipeline speed and follow-up compliance.
+- Running retrospectives after SLA breaches or pipeline delays.
+
+## Framework
+1. **Definitions** – clarify timestamps (MQL, SAL, SQL), owner transitions, and acceptance criteria.
+2. **Targets** – set response + acceptance SLAs per segment, region, or channel.
+3. **Measurement** – configure data pipelines pulling MAP + CRM events, dedupe logic, and exclusions.
+4. **Alerting** – thresholds, notification channels, severity levels, and on-call rotation.
+5. **Review Cadence** – weekly dashboards, monthly retros, quarterly recalibration.
+
+## Templates
+- SLA scorecard (segment → target → actual → variance → owner).
+- Alert playbook with trigger conditions and escalation steps.
+- Retro template capturing root cause, fixes, and follow-up experiments.
+
+## Tips
+- Anchor SLAs to revenue impact (pipeline $) to drive accountability.
+- Include qualitative context (reason codes) to separate data gaps vs true SLA misses.
+- Pair with `routing-logic` updates when volume spikes create bottlenecks.
+
+---