SKILL

Define Events

Produces instrumentation specification with events, properties, owners, and QA steps.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·

Command: define-events

Inputs

  • use_case – business question or KPI the events support.
  • sources – data sources involved (product, web, CRM, MAP, billing).
  • tools – instrumentation stack (CDP, product analytics, warehouse, dbt).
  • constraints – optional legal/compliance requirements.
  • timeline – optional delivery date.

GTM Agents Pattern & Plan Checklist

Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

  • Pattern selection: Instrumentation typically runs pipeline (requirements → catalog → governance → QA → change mgmt). If governance + QA can run parallel, log a diamond segment with merge gate in the plan header.
  • Plan schema: Save .claude/plans/plan-<timestamp>.json capturing objective, data sources, task IDs, dependencies, context passing (schemas, privacy notes), error handling, and success metrics (coverage %, defect ceiling).
  • Tool hooks: Reference docs/gtm-essentials.md stack (Serena for repo diffs, Context7 for platform/legal docs, Sequential Thinking for review flows, Playwright for front-end event QA when applicable).
  • Guardrails: Default retry limit = 2 for QA failures; escalation ladder = Analytics Data Strategist → Data Engineering Lead → RevOps.
  • Review: Run docs/usage-guide.md#orchestration-best-practices-puerto-parity before execution to confirm agents, dependencies, deliverables.

Workflow

  1. Requirement Gathering – clarify KPIs, dimensions, and downstream consumers.
  2. Event Cataloging – list events, payloads, properties, IDs, sampling rate, ownership.
  3. Governance Mapping – document naming conventions, consent handling, retention policies.
  4. QA Plan – outline testing methods (unit tests, replay, observability dashboards).
  5. Change Management – define review/approval steps, rollout plan, and version control.

Outputs

  • Instrumentation spec (event name, description, properties, source, owner, status).
  • Tracking plan (CSV/JSON/YAML) aligned with CDP or analytics tool requirements.
  • QA checklist + evidence plan (logs, dashboards, sample payloads).
  • Plan JSON entry stored/updated in .claude/plans for audit trail.

Agent/Skill Invocations

  • analytics-data-strategist – leads requirements + governance.
  • instrumentation skill – enforces schema + consent rules.
  • quality-gates skill – defines QA expectations.

GTM Agents Safeguards

  • Fallback agents: document substitutes (e.g., BI Publisher covering QA) if specialists unavailable.
  • Escalation triggers: if instrumentation defects or compliance blockers breach guardrails twice in 48h, escalate to Data + Legal leadership, triggering GTM Agents-style rip-cord.
  • Plan maintenance: update plan JSON/change log whenever events, schemas, or governance rules change to keep analytics audit-ready.

More on the bench

SKILL▲0

Launch

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

Corey Haines
marketing-growth-copy+2
⊙ 9
SKILL▲0

Marketing Ideas

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.

Alireza Rezvani
marketing-growth-copy+2
⊙ 7
SKILL▲0

Launch Strategy

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Alireza Rezvani
marketing-growth-copy+2
⊙ 2