guard-uplift-expansion

Installation
SKILL.md

GUARD Uplift — Expansion Signal Analysis & Business Case

Section 0 — Operating Principles (MANDATORY)

Read references/input-rules.md BEFORE executing any workflow step. Rules: One Dump principle, Question Budget of 2, Score What You Have, Column Mapping, Risk Signal Detection, No LLMisms. Consult references/cs-metrics-glossary.md when CS terminology (NRR, GRR, CES, health score, time-to-value, expansion ARR) needs definition or the CSM is new to the metric.

Golden Rule

Never pitch expansion to an at-risk account. If the health score is below 60 or risk signals are present, redirect to guard-defend-renewal or guard-gauge-diagnostic first. The ONLY exception: when the expansion itself IS the save strategy (upgrading solves the problem causing risk). Expansion follows health, never precedes it.

Context and Role Detection

Persona Output Adaptation
IC CSM Signal assessment + conversation guide + timing recommendation
CS Manager Portfolio expansion scan + pipeline summary + team coaching points
VP/Head of CS Expansion ARR pipeline + NRR forecast + resource allocation for expansion plays
Founder doing CS Plain language, "here's when and how to ask for more money"
Installs
3
First Seen
14 days ago