Initial commit

skills/competitive-intel/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: competitive-intel
+description: Use when researching, documenting, and sharing competitor insights with
+  GTM teams.
+---
+
+# Competitive Intelligence Ops Skill
+
+## When to Use
+- Preparing battlecards, objection handling, or exec briefings.
+- Monitoring competitor launches, pricing changes, or campaigns.
+- Running win/loss and market intelligence programs.
+
+## Framework
+1. **Collect** – pull from sales calls, Gong, analyst notes, communities, social, product updates.
+2. **Analyze** – map strengths/weaknesses, feature parity, pricing, GTM motions.
+3. **Package** – build battlecards, alerts, teardown docs, highlights for weekly digests.
+4. **Enable** – deliver via enablement hubs, Slack alerts, office hours.
+5. **Measure** – track adoption, impact on win rates, feedback loops.
+
+## Templates
+- Competitor dossier structure (Overview, Differentiation, Traps, Assets).
+- Alert format for urgent updates.
+- Win/loss survey + summary report.
+
+## Tips
+- Always cite sources and freshness dates.
+- Partner with sales enablement to ensure updates are surfaced during deal cycles.
+- Keep a change log to monitor how competitor narratives evolve.
+
+---

skills/launch-plays/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: launch-plays
+description: Use when orchestrating Tier 1/2/3 launches with repeatable workstreams
+  and governance.
+---
+
+# Launch Playbooks Skill
+
+## When to Use
+- Planning upcoming product/feature launches.
+- Auditing current launch processes for efficiency gaps.
+- Onboarding new PMMs or cross-functional launch partners.
+
+## Framework
+1. **Tiering Model** – define Tier 1/2/3 criteria (impact, audience, readiness) with required workstreams.
+2. **Workstreams** – campaign, content, enablement, comms, success, ops, product readiness.
+3. **RACI** – assign responsible/approver for each deliverable.
+4. **Cadence** – stand-up schedule, checkpoints, risk reviews.
+5. **Measurement** – KPI stack + reporting templates.
+
+## Templates
+- Launch plan board (Notion/Jira/Asana) with tasks + owners.
+- Brief template capturing audience, goals, narrative, dependencies.
+- Retro template for capturing learnings.
+
+## Tips
+- Lock tier and scope early to prevent scope creep.
+- Maintain a risk log with mitigation owners.
+- Pair with `workflow-testing` and automation teams to confirm infra readiness.
+
+---

skills/positioning/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: positioning
+description: Use when structuring positioning statements, message houses, and proof
+  libraries for GTM teams.
+---
+
+# Positioning Systems Skill
+
+## When to Use
+- Kicking off new products/features or entering new markets.
+- Refreshing messaging after competitive or market shifts.
+- Equipping sales/CS with updated stories.
+
+## Framework
+1. **Audience & Problem** – ICP, pain, current workaround.
+2. **Promise** – how we uniquely solve it (functional + emotional).
+3. **Proof** – metrics, customers, analysts, demos.
+4. **Payoff** – business outcome and CTA.
+5. **Variants** – adjust for personas, industries, regions.
+
+## Templates
+- Positioning canvas (Audience, Need, Approach, Differentiation, Proof).
+- Message house diagram.
+- Snippet bank (email, social, ad copy, call intro).
+
+## Tips
+- Validate with customers before rollout.
+- Keep one source of truth; document version and owner.
+- Align with design/content teams so visuals mirror messaging.
+
+---