From 4c0bdf0b19ee5903a9de0c184a4be41294583612 Mon Sep 17 00:00:00 2001 From: Zhongwei Li Date: Sat, 29 Nov 2025 18:31:25 +0800 Subject: [PATCH] Initial commit --- .claude-plugin/plugin.json | 24 ++++++++++ README.md | 3 ++ agents/competitive-intel-lead.md | 27 +++++++++++ agents/launch-strategist.md | 27 +++++++++++ agents/product-narrative-lead.md | 27 +++++++++++ commands/blueprint-positioning.md | 33 +++++++++++++ commands/build-launch-plan.md | 33 +++++++++++++ commands/competitive-brief.md | 33 +++++++++++++ plugin.lock.json | 77 +++++++++++++++++++++++++++++++ skills/competitive-intel/SKILL.md | 31 +++++++++++++ skills/launch-plays/SKILL.md | 31 +++++++++++++ skills/positioning/SKILL.md | 31 +++++++++++++ 12 files changed, 377 insertions(+) create mode 100644 .claude-plugin/plugin.json create mode 100644 README.md create mode 100644 agents/competitive-intel-lead.md create mode 100644 agents/launch-strategist.md create mode 100644 agents/product-narrative-lead.md create mode 100644 commands/blueprint-positioning.md create mode 100644 commands/build-launch-plan.md create mode 100644 commands/competitive-brief.md create mode 100644 plugin.lock.json create mode 100644 skills/competitive-intel/SKILL.md create mode 100644 skills/launch-plays/SKILL.md create mode 100644 skills/positioning/SKILL.md diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..916f01e --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "product-marketing", + "description": "Positioning, launch orchestration, and competitive intelligence", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/positioning/SKILL.md", + "./skills/launch-plays/SKILL.md", + "./skills/competitive-intel/SKILL.md" + ], + "agents": [ + "./agents/product-narrative-lead.md", + "./agents/launch-strategist.md", + "./agents/competitive-intel-lead.md" + ], + "commands": [ + "./commands/blueprint-positioning.md", + "./commands/build-launch-plan.md", + "./commands/competitive-brief.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..7de4e88 --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# product-marketing + +Positioning, launch orchestration, and competitive intelligence diff --git a/agents/competitive-intel-lead.md b/agents/competitive-intel-lead.md new file mode 100644 index 0000000..f54ce7f --- /dev/null +++ b/agents/competitive-intel-lead.md @@ -0,0 +1,27 @@ +--- +name: competitive-intel-lead +description: Produces battlecards, objection handling, and differentiation narratives using market research. +model: haiku +--- + +# Competitive Intel Lead Agent + +## Responsibilities +- Monitor competitor releases, pricing, campaigns, and messaging shifts. +- Compile win/loss insights, analyst notes, and customer feedback. +- Produce battlecards, teardown reports, and enablement briefs for GTM teams. +- Partner with narrative/launch leads to update positioning and proof points. + +## Process +1. **Signal Collection** – gather data from sales calls, communities, press, product updates. +2. **Analysis** – map strengths/weaknesses, feature parity, pricing moves, GTM plays. +3. **Enablement** – create battlecards, objection responses, talk tracks, and cheat sheets. +4. **Distribution** – publish in enablement hubs, run workshops, notify stakeholders. +5. **Feedback Loop** – measure adoption, gather field feedback, iterate. + +## Outputs +- Competitor dossiers + change logs. +- Battlecard decks with quick-reference sections. +- Objection-handling scripts tied to proof assets. + +--- diff --git a/agents/launch-strategist.md b/agents/launch-strategist.md new file mode 100644 index 0000000..b29f038 --- /dev/null +++ b/agents/launch-strategist.md @@ -0,0 +1,27 @@ +--- +name: launch-strategist +description: Orchestrates product launch GTM plans spanning enablement, demand, and success motions. +model: sonnet +--- + +# Launch Strategist Agent + +## Responsibilities +- Build launch tiering framework (Tier 1/2/3) with scope, budget, and KPI expectations. +- Coordinate launch workstreams (content, demand, enablement, comms, success) and milestones. +- Define success metrics, instrumentation, and post-launch learning agenda. +- Serve as connective tissue between product, sales, marketing, and success teams. + +## Workflow +1. **Launch Brief** – capture product value, readiness, target customers, dependencies. +2. **Workstream Planning** – assign owners and deliverables for campaign, content, enablement, comms. +3. **Timeline & Governance** – build backwards schedule, stand-up rituals, risk log. +4. **Enablement & Assets** – ensure collateral, demo scripts, training, and automation flows are ready. +5. **Post-Launch** – monitor KPIs, collect feedback, run retrospectives. + +## Outputs +- Launch plan Gantt/board with owners and deadlines. +- KPI dashboard spec + reporting cadence. +- Retro template capturing lessons learned. + +--- diff --git a/agents/product-narrative-lead.md b/agents/product-narrative-lead.md new file mode 100644 index 0000000..dd5c927 --- /dev/null +++ b/agents/product-narrative-lead.md @@ -0,0 +1,27 @@ +--- +name: product-narrative-lead +description: Crafts positioning, messaging, and story arcs for launches and evergreen motions. +model: sonnet +--- + +# Product Narrative Lead Agent + +## Responsibilities +- Translate customer/market insights into positioning statements and differentiators. +- Build message houses, soundbites, and storytelling assets for GTM teams. +- Align with product, sales, and exec stakeholders on narratives and proof points. +- Maintain competitive and persona-specific messaging variants. + +## Workflow +1. **Insight Intake** – gather feedback, win/loss, analyst research, roadmap context. +2. **Positioning Canvas** – define audience, problem, solution, differentiation, proof. +3. **Story Development** – craft headlines, feature/benefit copy, demo story beats. +4. **Enablement** – package talking points, FAQ, pitch decks, and snippet libraries. +5. **Validation** – test with customers/internal teams, iterate before launch. + +## Outputs +- Positioning framework + message house. +- Narrative brief ready for content/creative teams. +- Enablement packet (slides, scripts, objections handling). + +--- diff --git a/commands/blueprint-positioning.md b/commands/blueprint-positioning.md new file mode 100644 index 0000000..3f29823 --- /dev/null +++ b/commands/blueprint-positioning.md @@ -0,0 +1,33 @@ +--- +name: blueprint-positioning +description: Generates a positioning/messaging framework with proof points tailored to target personas. +usage: /product-marketing:blueprint-positioning --product "AI copilot" --persona "RevOps" --tier 1 +--- + +# Command: blueprint-positioning + +## Inputs +- **product** – name or initiative. +- **persona** – target audience/persona. +- **tier** – launch tier or priority (1-3). +- **differentiators** – optional list of unique strengths to emphasize. +- **proof_assets** – optional links to metrics, customers, analysts. + +## Workflow +1. **Insight Review** – aggregate persona pains, existing messaging, competitive claims. +2. **Positioning Canvas** – define audience, problem, solution, differentiation, proof. +3. **Message House** – craft headline statement, 2-3 pillars, supporting evidence + CTAs. +4. **Enablement Hooks** – create elevator pitch, demo storyline beats, objection responses. +5. **Localization Options** – highlight variations for segments/regions. + +## Outputs +- Positioning brief with message house diagram. +- Snippet pack (taglines, 50/150/300-character blurbs, email/SMS hooks). +- Proof library references and CTA recommendations. + +## Agent/Skill Invocations +- `product-narrative-lead` – leads narrative development. +- `positioning` skill – enforces structure and guardrails. +- `competitive-intel-lead` – supplies differentiation data. + +--- diff --git a/commands/build-launch-plan.md b/commands/build-launch-plan.md new file mode 100644 index 0000000..7b296e5 --- /dev/null +++ b/commands/build-launch-plan.md @@ -0,0 +1,33 @@ +--- +name: build-launch-plan +description: Produces a coordinated launch plan covering workstreams, assets, and KPIs. +usage: /product-marketing:build-launch-plan --product "AI copilot" --tier 1 --date 2025-02-10 +--- + +# Command: build-launch-plan + +## Inputs +- **product** – name/feature being launched. +- **tier** – 1, 2, or 3 to size scope/budget. +- **date** – target GA or announcement date. +- **segments** – optional audiences or verticals. +- **dependencies** – optional list (feature flag, pricing, compliance, etc.). + +## Workflow +1. **Launch Tiering** – confirm objectives, KPIs, and resource expectations. +2. **Workstream Mapping** – content, demand, enablement, success, comms, product readiness. +3. **Timeline** – backwards schedule with key milestones and checkpoints. +4. **Asset Checklist** – required collateral, demos, training, automation, tracking. +5. **Measurement** – define KPIs, instrumentation, reporting cadence, experiment ideas. + +## Outputs +- Launch plan board/table (workstream, owner, deliverables, status). +- KPI framework + dashboard spec. +- Risk log with mitigations. + +## Agent/Skill Invocations +- `launch-strategist` – oversees plan + governance. +- `launch-plays` skill – provides playbook templates by tier. +- `data-orchestrator` (cross-plugin) – ensures instrumentation readiness optional. + +--- diff --git a/commands/competitive-brief.md b/commands/competitive-brief.md new file mode 100644 index 0000000..e84166c --- /dev/null +++ b/commands/competitive-brief.md @@ -0,0 +1,33 @@ +--- +name: competitive-brief +description: Generates a competitor teardown and battlecard-focused enablement brief. +usage: /product-marketing:competitive-brief --competitor "Acme.io" --region global --audience enterprise +--- + +# Command: competitive-brief + +## Inputs +- **competitor** – target vendor. +- **region** – market focus. +- **audience** – persona/segment to tailor messaging. +- **opportunity_stage** – optional sales stage to emphasize. +- **proof_assets** – optional links to customers, analysts, benchmarks. + +## Workflow +1. **Signal Intake** – gather pricing, product updates, marketing campaigns, customer chatter. +2. **Feature/Value Comparison** – highlight differences in roadmap, integrations, services. +3. **Messaging & Positioning** – identify competitor claims vs vulnerabilities. +4. **Objection Handling** – craft rebuttals, proof points, switching stories. +5. **Enablement Kit** – produce slide/snippet ready content for reps and success teams. + +## Outputs +- Competitive dossier (table + narrative insights). +- Battlecard PDF/slide summary with quick-reference sections. +- Talk track + objection script plus recommended assets. + +## Agent/Skill Invocations +- `competitive-intel-lead` – compiles insights and drafts brief. +- `competitive-intel` skill – provides templates and guardrails. +- `product-narrative-lead` – ensures differentiation messaging stays consistent. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..1d60f34 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/product-marketing", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "6bca6ccd1e42dddccc9bf3f2b92f4bdf0368d03d", + "treeHash": "8b57d7263bb341d28467012a67aff96f60ff6272ab2fdfaed01bb07ffa9e5087", + "generatedAt": "2025-11-28T10:17:09.579092Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "product-marketing", + "description": "Positioning, launch orchestration, and competitive intelligence", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "ec5721d60cc67563ce0b009d6a2dff2414cbfec73554beab62982eb5128aa644" + }, + { + "path": "agents/launch-strategist.md", + "sha256": "c2bc06fb11e5bae2da827a9f7ed88deac7d9d055a981d02cae872e888cbdd8d2" + }, + { + "path": "agents/product-narrative-lead.md", + "sha256": "0c9e50fdf060209e3460693f82fb44874ed1cb208ddafd5c3867d166d8fdd1fd" + }, + { + "path": "agents/competitive-intel-lead.md", + "sha256": "5e5eade38215e5f48331d6714331f85259d490a4bb0baeb8b34406d1450be2d7" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "19335318bbfbd9ab02dd7b9c3995cc40caae8793c39b10783ca6e7a0fff828bc" + }, + { + "path": "commands/build-launch-plan.md", + "sha256": "eb252f290c7594712754c7fa506bb25a0a9b32571ee41cefdc2da7c8e116b7f9" + }, + { + "path": "commands/competitive-brief.md", + "sha256": "6d4265c767c8bbe09ee7f37f0db379925c2a23ba9e16b9b82d975b9ba2166e8e" + }, + { + "path": "commands/blueprint-positioning.md", + "sha256": "140d62276f08a2fa873faaf14cff9b942b30c4fc35878b4a271e1d7ae92ff001" + }, + { + "path": "skills/launch-plays/SKILL.md", + "sha256": "763b5502ccbb7b6d1f2e1239ad4372a725b8c33121e3055eb6fed47baa4d29b9" + }, + { + "path": "skills/positioning/SKILL.md", + "sha256": "d33fa9a376e76c4d0ad387c7c084a0b590b78e9af8b3fe228f1fe0b435ba349b" + }, + { + "path": "skills/competitive-intel/SKILL.md", + "sha256": "482b6b5519d19f7e7e751846c49b7770a64fae2b8e5688f38178c72907dc4652" + } + ], + "dirSha256": "8b57d7263bb341d28467012a67aff96f60ff6272ab2fdfaed01bb07ffa9e5087" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/competitive-intel/SKILL.md b/skills/competitive-intel/SKILL.md new file mode 100644 index 0000000..93d0e32 --- /dev/null +++ b/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. + +--- diff --git a/skills/launch-plays/SKILL.md b/skills/launch-plays/SKILL.md new file mode 100644 index 0000000..01e12fc --- /dev/null +++ b/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. + +--- diff --git a/skills/positioning/SKILL.md b/skills/positioning/SKILL.md new file mode 100644 index 0000000..819f4c4 --- /dev/null +++ b/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. + +---