What's on the bench.
Revops Data Governance
Revenue data governance — the operational discipline every other RevOps skill depends on. Use when the user mentions data governance, data quality, data model, data architecture, field governance, property naming conventions, data hygiene, deduplication, integration data flows, system of record, sync rules, data enrichment, data definitions, one vision of truth, data spine, data quality scoring, validation rules, GDPR, field deprecation, or data audit. Also trigger when someone says "our reports don't match," "our CRM is a mess," "we have too many fields," or describes duplicate accounts, conflicting numbers, stale data. Fix data governance before building metrics or scaling. BOUNDARY: Covers data MODEL, QUALITY, and GOVERNANCE. For HubSpot setup, see revops-hubspot. For metrics, see revops-metrics.
Revops Crisis
Revenue crisis triage and emergency response when multiple systems break simultaneously. Use this skill when the user describes a CRISIS state: forecast missed for multiple quarters, win rate collapsing, pipeline coverage below 3x and falling, NRR crashed below 90%, multiple simultaneous system failures, loss of trust between functions, data that can't be trusted, or scenarios like "everything is broken," "forecast is ±30% wrong," "we're losing deals we should win," "I can't trust our data," "sales blames marketing blames product," "three quarters in a row we missed," "board is panicking," or "we need to save this quarter." Also trigger on "we need emergency triage," "nothing is working," "where do we even start," or "we're in firefighting mode." BOUNDARY: This is emergency response (what to fix FIRST when everything is broken). For detailed methodology after stabilization, see revops-diagnostic and revops-maturity. For specific domain fixes, see the relevant domain skill.
Revops Change Management
Revenue change management — plan change, design enablement, make it stick, measure adoption. Trigger on change management, enablement design, adoption failure, rollout plan, communication plan, stakeholder management, training that doesn't stick, behaviour change, coaching programme, process change, system migration, comp plan change, territory change, Kotter, ADKAR, spaced repetition, forgetting curve, reverse salient, traffic light model, Bloom's taxonomy, "nobody follows the new process," "we trained them but nothing changed," "the tool is built but nobody uses it," "how do we get buy-in," "people are pushing back," AI change management, FOBO, shadow AI, AI adoption, works council AI, AI governance framework, AI rollout, or fear of becoming obsolete. BOUNDARY: For HubSpot adoption, see revops-hubspot. For GTM org change, see gtm-planning. For AI Readiness Day, see neon-ai-readiness-day.
Revenue Operating Cadence
Revenue operating cadence — meeting architecture, data pyramid, and board reporting that turns strategy into execution. Use when the user mentions operating cadence, meeting cadence, forecast calls, pipeline review, QBR, board meeting, board deck, monthly business review, sales standup, deal review, meeting architecture, meeting agenda, revenue ceremonies, or structuring revenue meetings. Also trigger when someone asks about board deck structure, running forecast calls, fixing meetings that waste time, or getting accountability. If someone says "our meetings are status updates" or "the board keeps getting surprised" or "nothing gets done," activate this skill. BOUNDARY: Covers meeting structure and data inputs. For forecast methodology, see revops-forecasting. For metrics, see revops-metrics.
Pipeline Visibility
Pipeline visibility, reporting architecture, dashboard design, pipeline hygiene, and forecast reporting for B2B revenue teams. CRM-agnostic patterns for any platform. Use when the user mentions pipeline visibility, pipeline reporting, sales dashboards, pipeline hygiene, stale deals, pipeline coverage, pipeline health, deal inspection, pipeline review, win rate reporting, conversion funnels, pipeline cleanup, pipeline scrub, forecast reporting, forecast accuracy tracking, big deal alerts, or pipeline quality score. Also trigger on 'we can't see our pipeline,' 'deals go stale,' 'pipeline reports are wrong,' 'we need better dashboards,' or 'how do we track pipeline health.' BOUNDARY: Covers pipeline VISIBILITY and REPORTING (CRM-agnostic). For CRM-specific implementation, see revops-hubspot or revops-salesforce. For forecast methodology, see revops-forecasting. For metrics, see revops-metrics.
Partner Ecosystem Architect
Design and install partner ecosystem strategies for B2B SaaS clients using ecosystem-led growth (ELG) and nearbound methodology. Use when someone mentions 'partner strategy,' 'ecosystem-led growth,' 'nearbound,' 'partner ecosystem,' 'build a partner programme,' 'co-selling strategy,' 'account mapping,' 'Crossbeam,' 'Reveal,' 'partner motion,' 'referral programme,' or 'partner revenue.' Also trigger on 'we need partners to grow,' 'partner programme isn't working,' or 'partners should be our next GTM motion.' Also trigger on 'Crossbeam Reveal,' 'Introw,' 'PRM tools,' 'partner tools,' 'cloud marketplace strategy,' 'partner benchmark,' or 'partner economics.' Designs partner strategy and architecture — why this partner type, why now, how it fits the system. BOUNDARY: For partner operational plumbing (deal registration, health scoring, CRM properties), see partner-channel-operations. For handoffs see revops-handoffs.
Operating Cadence Designer
Design and install the operating cadence for a client — the calendar that makes the revenue operating system real. Connects the strategy scorecard (strategy), the revenue dashboard (visibility), and weekly/monthly rituals (execution). Use whenever the user mentions 'operating cadence,' 'cadence design,' 'meeting architecture,' 'install the cadence,' 'ritual design,' 'revenue meetings,' '5P meetings,' 'breach rhythm,' 'WIP limits,' 'decision cadence,' 'signal trigger action,' 'decision rules,' or any engagement where meetings need restructuring. Also trigger on 'our meetings are status updates,' 'nobody makes decisions,' 'nothing gets done,' 'the board keeps getting surprised,' or 'we need a rhythm.' Also trigger on 'forecast calls,' 'pipeline review,' 'QBR,' 'board meeting,' 'board deck,' 'monthly business review,' 'sales standup,' or 'deal review.' BOUNDARY: For the revenue dashboard build itself, see pipeline-visibility.
Marketing Operations
Marketing operations for B2B revenue teams — lead scoring, attribution, campaign tracking, and handoff protocols. Use when the user mentions marketing operations, marops, lead scoring, MQL definition, MQL to SQL handoff, lead routing, attribution modeling, multi-touch attribution, W-shaped attribution, marketing sourced pipeline, campaign operations, UTM taxonomy, demand gen ops, channel mix, marketing SLA, speed to lead, ICP fit scoring, SPICED lead scoring, ICP fit matrix, selection fit, urgency fit, qualification tier scoring, T1 T2 T3 leads, or ICP fit scoring. Also trigger when someone says "sales says our leads are garbage" or "we can't attribute revenue to campaigns." BOUNDARY: Covers marketing OPERATIONS (lead management, attribution, campaign ops). For HubSpot, see revops-hubspot. For funnel math, see revops-metrics. For ICP BUILDING methodology (GAP method, customer interviews), see neon-icp.
Icp Builder
Build, validate, or expand a client's ICP (Ideal Customer Profile) using the GAP method, SPICED framework, and customer interview pipeline. Triggers on 'build their ICP,' 'check their ICP,' 'ICP validation,' 'ICP quality,' 'they don't have an ICP,' 'ICP is too broad,' 'who should they sell to,' 'segment their market,' 'ICP workshop,' 'customer interviews for ICP,' 'GAP method,' 'ICP expansion,' 'Goldilocks zone,' 'tier their customers,' 'A/B/C segmentation,' 'are they targeting the right customers,' 'segmentation check,' 'ICP review,' 'who are they actually selling to,' or any client engagement where the ICP is missing, broken, or needs validation. This skill covers the full ICP lifecycle: validate what exists, build from scratch, refine with interviews, and plan expansion. BOUNDARY: For positioning/messaging (step AFTER ICP), see positioning-messaging-designer.
Gtm Planning
Go-to-market planning, org design, territory design, and capacity planning for B2B revenue teams. Use when the user mentions GTM planning, go-to-market, GTM motion, territory design, org design, sales org, team structure, capacity planning, headcount model, hiring plan, ICP definition, PLG, product-led growth, sales-led, partner-led, channel strategy, named accounts, team ratios, SDR-to-AE ratio, or scaling the sales team. Also trigger when someone asks about entering a new market, redesigning territories, or planning next year's revenue org. If someone says "how should I structure my sales team" or "our territories don't make sense," activate this skill. BOUNDARY: Covers team STRUCTURE, territories, and capacity. For comp plans and quotas, see gtm-compensation. For ICP BUILDING methodology (GAP method, interviews, thresholds), see neon-icp.
Gtm Compensation
GTM compensation plan design, quota setting, OTE structures, and benchmarking for B2B revenue teams. Use when the user mentions comp plans, OTE, on-target earnings, variable pay, commission structure, quota setting, accelerators, decelerators, SPIFs, clawbacks, sales compensation, SDR comp, AE comp, CSM comp, pay mix, commission rates, ramp periods, or comp plan modeling. Also trigger when someone asks about benchmarking GTM salaries, designing incentive structures, or fixing misaligned compensation. If someone says "how should I pay my reps" or "what's a fair OTE" or "our comp plan isn't working," activate this skill. BOUNDARY: Covers how to PAY people. For org design and capacity, see gtm-planning.
Expansion Revenue Architect
Design and install expansion revenue systems improving NRR and GRR for B2B SaaS. GRR/NRR diagnostic, expansion motion architecture, whitespace analysis, CS-Sales handback, renewal pricing, and 90-day NRR programmes. Trigger on 'NRR improvement,' 'GRR strategy,' 'expansion revenue,' 'upsell cross-sell,' 'whitespace analysis,' 'CS expansion,' 'net revenue retention,' 'right side of the bowtie,' 'land and expand,' 'expansion is accidental,' 'CS doesn't own revenue,' 'we keep discounting renewals,' 'health score,' 'time to value,' 'customer advocacy,' 'usage-based pricing NRR,' 'account penetration,' 'second-order revenue,' or 'CSM coverage model.' Also use when NRR below 110% or GRR below 90%. Designs full expansion engine connecting health scoring, signals, whitespace, CS-Sales handbacks, and dashboard tiles. BOUNDARY: For CS operations, see cs-operations. For pricing, see pricing-strategy. For handoffs, see revops-handoffs.
Deal Velocity Engineer
Diagnose and fix deal velocity problems. Sales cycle diagnostics, stage exit criteria, pipeline deflation, zombie deal elimination, multi-threading, mutual action plans, and compression tactics with sourced benchmarks. Trigger on 'deal velocity,' 'sales cycle too long,' 'deals stalling,' 'pipeline velocity,' 'stage exit criteria,' 'zombie deals,' 'pipeline deflation,' 'deals stuck,' 'multi-threading,' 'mutual action plan,' 'deal inspection,' 'pipeline hygiene,' 'cycle time,' 'stage conversion,' 'deals die in negotiation,' 'we keep slipping deals,' 'reps can't close,' or 'pipeline is bloated but nothing closes.' Connects stage gates, deal scoring, inspection cadence, and pipeline deflation into the operating cadence. BOUNDARY: For forecast methodology see revops-forecasting. For pipeline visibility and dashboards see pipeline-visibility. For sales methodology (SPICED/MEDDPICC) see sales-methodology. For operating cadence see revenue-operating-cadence.
Data Enrichment
B2B data enrichment strategy, provider evaluation, integration patterns, and quality management for revenue operations teams. Use when the user mentions data enrichment, lead enrichment, account enrichment, contact enrichment, ZoomInfo, Clearbit, Apollo, Clay, Cognism, Lusha, enrichment automation, enrichment workflows, firmographic data, technographic data, intent data, data append, enrichment API, enrichment coverage, data freshness, enrichment quality, or third-party data providers. Also trigger on 'our data is incomplete,' 'leads come in with no company info,' 'we need better data on our accounts,' 'enrichment isn't working,' or 'which enrichment tool should we use.' BOUNDARY: Covers enrichment STRATEGY, PROVIDER SELECTION, and INTEGRATION. For CRM-specific implementation, see revops-hubspot or revops-salesforce. For data governance, see revops-data-governance. For lead scoring that uses enriched data, see marketing-operations.
Cs Operations
Customer success operations for B2B SaaS — the post-sale revenue engine that prevents churn, drives expansion, and compounds customer value. Use when the user mentions customer success, CS ops, health scoring, renewal management, churn prevention, expansion playbook, expansion signals, onboarding orchestration, time to first value, QBR, customer segmentation, coverage model, high-touch, low-touch, tech-touch, CSM ratios, NPS, CSAT, save plays, red accounts, CS-Sales handoff, churn autopsy, renewal discount governance, discount sunset, renewal pricing, or save plays with pricing components. Also trigger when someone says "we keep losing customers" or "our CS team is reactive" or "we have no idea which accounts will churn" or "discounts are expiring and customers are pushing back" or "renewal price increase resistance."
Pm Workflow Orchestrator
Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.
Pm Skill Auditor
Repo-level cross-cutting governance auditor. Runs the full enforcing validator suite (frontmatter lint, command paths, AGENTS.md sync, family contracts, link validity, count consistency, workflow generator coverage, etc.) via scripts/pre-tag-validate.{sh,ps1}, aggregates results, and surfaces cross-cutting issues no single validator catches alone (sample gaps, aggregate counter drift, family contract orphans / phantoms, thread imbalance, deprecated references, etc.). Re-derives aggregate counters across CONTEXT.md + AGENTS.md + README.md. Returns layered output (full report + Status Summary + Status YAML) graded P0/P1/P2/P3. Explicit invocation only - never proactive. Used by maintainers pre-release and by users running repo-health checks.
Pm Release Conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance past a failed gate. No bypass possible (--skip-gates removed per D24). Tags only the SHA captured at G2.5 (prevents broken-tag class per D22). G4 P0 sub-checks block "Release complete" output (per D23). Maintainer-facing; explicit invocation only.
Pm Critic
Use proactively after any PM-artifact-producing skill completes (deliver-prd, foundation-meeting-recap, foundation-okr-writer, foundation-persona, foundation-lean-canvas, discover-interview-synthesis, define-problem-statement, define-hypothesis, deliver-edge-cases, deliver-user-stories, deliver-acceptance-criteria, iterate-retrospective, iterate-lessons-log, and other Triple Diamond phase skills). Runs adversarial review. Finds weaknesses, not wins. Returns findings graded P0/P1/P2/P3 with concrete fix suggestions for each. Reads canonical standards docs at invocation time.
Pm Changelog Curator
Drafts CHANGELOG entries from git log applying pm-skills CHANGELOG hygiene rules from CLAUDE.md: describe what changed (not where), public paths only, never reference gitignored _NOTES/ or _agent-context/SESSION-LOG/ or docs/internal/efforts/. Distinguishes user-facing from internal-only commits. Returns a draft for maintainer review and edit. Explicit invocation only. Used standalone via the utility-pm-changelog-curator dispatch skill (or @-mention) or chained from pm-release-conductor at gate G2.
Workflow Post Launch Learning
Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons)
Workflow Foundation To Design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff
Workflow Foundation Sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)
Workflow Design Sprint
Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)