SKILL.md
Launch Tiering Framework Skill
Not every release deserves a full launch. This skill decides how big a launch should be, then scopes the go-to-market effort to match — so big bets get the push they deserve and minor updates don't burn the team or the audience's attention.
What This Skill Produces
- A launch tier (T1 / T2 / T3) with the scoring rationale
- The set of activities and channels appropriate to that tier
- Owners and a timeline
- A right-sized launch checklist and success metrics
Required Inputs
Ask for these if not provided:
- What's launching — the feature/product and who it's for
- Impact signals — revenue potential, strategic importance, audience reach, competitive pressure, customer demand
- Novelty — incremental improvement vs new capability vs new product
- Readiness — GA vs beta, docs, enablement, support readiness
- Constraints — team bandwidth, date pressure, dependencies
- Any house tiering definitions already in use (use them if provided)
Tiering Rubric
Score the launch on impact and novelty; the higher of the two typically sets the tier.
- T1 — Major: new product or flagship capability; strategic; broad audience; competitive stakes. Full GTM.
- T2 — Notable: meaningful new feature; matters to a segment; worth proactive comms. Moderate GTM.
- T3 — Minor: incremental improvement, fix, or narrow feature. Low-effort, in-product + notes.
If readiness lags the tier the impact warrants, flag the gap rather than downgrading silently.
Process
- Score impact and novelty using the signals provided; note the reasoning.
- Assign the tier (higher of impact/novelty), and state what would move it up or down.
- Scope activities to the tier — don't over- or under-invest.
- Assign owners and a timeline across product, PMM, content, sales, support.