From c3efe0cdefe386bdd5338462d7626bcc7f487f20 Mon Sep 17 00:00:00 2001 From: mohitagw15856 Date: Thu, 2 Apr 2026 09:01:04 +0100 Subject: [PATCH] feat: add go-to-market --- .DS_Store | Bin 8196 -> 10244 bytes skills/.DS_Store | Bin 12292 -> 14340 bytes skills/go-to-market/SKILL.md | 98 +++++++++++++++++++++++++++++++++++ 3 files changed, 98 insertions(+) create mode 100644 skills/go-to-market/SKILL.md diff --git a/.DS_Store b/.DS_Store index bf10890218cc4eb0e0950ce0dad87252e201f0f6..d31a5275c565f1baec1c9e30b92d92dd5a22dfa2 100644 GIT binary patch literal 10244 zcmeHMU2Ggh60Vv!@hsWIphy9yjwq5oKpre8 zzyz3JFOUuyAp#)+Ap#)+Ap#)+zXt^9o6U;6T+r|xA`l`FA~25t+aF@|Fq#PHoS=N` zpcg*^5Un9LFI1;<0N05HG!f7_LAff8DNYX62MlJ$ z;DmyFcG8P+alnM2;X6biL|`ET?Cib@G|=gXON21mdHhfebCL?;IL3MQw%uRkrZ4%ROEJd&x^S`VJa91>NL% zYB6smwpEqS6CufdlJA3EL>IwFa;r2NXax-L>24)YtCS-IT$thin-1Ps4& zo0rizQ*=9H(O;E+d`&JWo0<0V!Ro)1$y=u9cXWJ+(vq5`%W7p=UM?Riv z&CYJw+}Rr2a$VQ)*4XTgn>whz`G(`iBXVQ>+O0$5Q&!G)PLQuuF!(^g3elc_-$k_w z|IKVM@Cn~3`Sh8hl)Q>uvOKzCWt~#LYIS`>ePd(erE8kjuDYywTv?sbvQrZ-v$of< z9Jj|R7~@KvM?Mc^9ea;!6v@}LZyfWJ=AWo*Rh7b!p&vZYO3ma+rr|t;54z1Y4152C zYwClC4||56E~}5S*|M%h(n5cXLGbcrR!7pK`=VnP#I15= zN3xDp$l2bwQlHhVY{Alequa6=V#KRnnX)*j>PqkP9M`ASroqM)rQjJu290GFjXoOD zn_q?n*hWsRTyw?x4Q-n`Z%*_N?Am*dM`^S%x{uPv_RYhl;f`uv*06P2x#4M3_a{e+ zre|g>BV}tjBT|p8k#luTYu8=Ytg1rbyh2GdUC5Y63#LD##ATV!5mQ^DV>%hP%hA~^ zx~!a`aVSTwR9n>jtf$vC=&c6|SF0PNDUX1W6-@}XM?0daDa!YV;t9^?==JI_55S0` zi+Q@DH>o2<5w{U#hhW|kZB)})Czm4^y@=p-tG(($HtkN$^9S>W%}hEg`u<3L`@Bib zH3p|?zX>ebPF$X>#AizVy6HQ-lhD}RqN<~8xNcqNKCEk6Tc;+~VOe=krX@1%qDgxk zWs}(INe*z-SP^CKEf_+swwRpNUZ@YD1dvxbT zlWrf0&p-ox0%BKQbM2O{Te{~1QABPjSj$s@$9+Y%@VMs*SQWG9cqT?KzoL|S=aW$+ z=P)IVaZF};tJDV4@%1t#jIuOnZn&D7JCtRj+1%DHQ*tU2Z$_IpZH`b1DocW9TPHP9 zG@@H?j!-fxH9_<81T}#-nw$IjX_&K${A)$}NANj(4d1|z6zMB*H8$Z@*nwRX-M8Xy z9^pwG#)CLcTYUy~%%P1A9;H~n9gpLmaSrdGNWYt6{XV=O|AK$TzfrtDj!)o|_%uF4 z(f%U7gfHVi@HKoL-wfjZ6N>tO;lHaQc~@m5<9F4OTui#Q<=7L%FMVt(Rl-(?K!`wy zz{QEc5@B|X-T(Jr`2YVGr*omzAp#)+zX$=W=}Y#pE4d5($YB>)F?tTs!wQp|6O^ma ui-|BkzmBH{yN>7A1jH+yfLMPbked^fI8=V~e+G1Pgy;Y8{QrM_{{I>4+0-)t delta 93 zcmZn(XmOBWU|?W$DortDU;r^WfEYvza8E20o2aMA$h$FMH$NlqW*&jZESoi?C71=7 hfzm)A!3`u_K`J*EerKM{uM)_?2+_~5Ii6<@GXU7w503x< diff --git a/skills/.DS_Store b/skills/.DS_Store index 5196fa3d8f5e24c37b2524867ef6f24a5a8b5142..9b51b46518d8bc26130b5d7baeb826a43aa417fe 100644 GIT binary patch delta 1774 zcmd5-TWl0n7(Uc3P;HM;|=N%zwWB zKj%M}|NC-I95^u(W{jaHt!-c|N?nOQVHKI&1j2GIyuPZBJU((V*2-LF(|?-9^Oblt zA8qlMfTI5V>0l^thR^4(hl7Pm_(}_9l3zlj@Hd-IrZ-{Q3Cc2@m@y5XwDBcu0GMki*_l44>o zOUGH-5IDP{x_)g_YkSAmuKt1D_g$_~DsNjUSIHBGrdzJ@prNP6<4#hyG{ZVLI%{a| z)L6!FjD)F=Sn+8+P>Ghn<%*ixx>X@n^#yowL!gKM0!&?{k4S&&FY=5g1{BR(r&Hdnj%DjQCCx&tx$*6 zQAzn+qB0p)#&D@hR2wpBM~W<#CepRe>qgEc&lP*#T}QeEe?^m+%Gy~U+r@ewZJQ+$Rma24O;JA998_#J=X1~1{& zyoT5E2HwJ3c^mKGoqRLj!uRk&9^-L-h(~Nb;~jttWr_BHXBPkb$fBxdJXP_t|E{Xg zz1s(N$h-cZs=BhGsH0%j?bYGNb?fiy+}3@QZ5}@tDY=yBMRxy16Ge6xYyUT5UM>nw zUR^H~mKAEeB|1-pqofOcP7?Z5$`*!4)=H!crDOp%H51&alzK4K+9r_(6<&mLsC{FA zl&1I=U~30KctGB=H9(qE{2t88tGfuZA_|52`YF#PMf$J!e1%N3jq4aR3Qun1%%#hl$b0@CY8oaXdzReu^0VG;(+j&*KGR^=o(? zZ{Q5xB2K@D_wgY<#(7-8CkyQUnz;QFe)foYldiiLiRxMWN;aPh*2Nbw0YLq0kndFU#e63d@xb{Dt~e&A!?aZ)&uhZ2!{dh~AcKzI;W?h9)77rZXn@`>;#~p@0lm_n;0@O ZOt#^X<^kFWawh|jHrSkDQq2r90RVJ|B!d6| diff --git a/skills/go-to-market/SKILL.md b/skills/go-to-market/SKILL.md new file mode 100644 index 0000000..af6df9d --- /dev/null +++ b/skills/go-to-market/SKILL.md @@ -0,0 +1,98 @@ +--- +name: go-to-market +description: "Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Generates a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases." +--- + +# Go-To-Market Skill + +This skill produces a complete go-to-market asset pack for a product, feature, or initiative. It follows Geoffrey Moore's positioning framework and structures all outputs for use in sales decks, landing pages, launch emails, and internal alignment docs. + +## Required Inputs + +Ask the user for these if not provided: +- **Product/feature name** +- **One-line description** (what it does, technically) +- **Target customer** (role, company size, industry if relevant) +- **Primary problem it solves** +- **Key competitor or alternative** (what people do today without this) +- **Top 3 differentiators** + +## Output Structure + +Always produce all four sections below in order. + +--- + +### 1. Positioning Statement + +Use the Geoffrey Moore format exactly: + +> For **[target customer]** who **[has this problem or need]**, **[Product Name]** is a **[product category]** that **[key benefit/outcome]**. Unlike **[primary alternative or competitor]**, our product **[key differentiator]**. + +Write one primary positioning statement, then offer a shorter tagline version (10 words or fewer) suitable for a hero headline. + +--- + +### 2. Messaging Pillars + +Generate 3–5 messaging pillars. Each pillar must include: + +- **Pillar name** (2–4 words, bold) +- **One-sentence summary** of what this pillar claims +- **2–3 proof points** (specific, evidence-backed where possible — if the user hasn't provided data, flag with [ADD PROOF POINT]) +- **Example use in copy** (one sentence as it would appear in a landing page or deck) + +Pillars should be distinct — avoid overlap. Each pillar should be defensible against the primary competitor. + +--- + +### 3. Feature & Functionality List + +Produce a two-column table: + +| Feature / Functionality | Buyer Benefit (what it means for the user) | +|---|---| +| [Technical capability] | [Outcome in plain language — start with a verb: "Reduces...", "Enables...", "Eliminates..."] | + +Rules: +- Never list a feature without a corresponding benefit +- Benefits should reference the target customer's workflow or pain point +- Aim for 6–12 rows; ask the user for more features if they've only given 1–2 +- Avoid jargon in the benefit column — write as if explaining to a buyer, not an engineer + +--- + +### 4. Use Cases + +Generate 3–5 role-specific use cases. Each use case must follow this format: + +**Use Case [N]: [Role] — [Scenario Title]** + +- **Who:** [Job title / role] +- **Situation:** [The specific moment or trigger that leads them to use the product] +- **Before:** [What they had to do without this product — be specific about time, friction, or risk] +- **With [Product Name]:** [What they do now — concrete action, not vague benefit] +- **Outcome:** [Measurable or tangible result] + +Use cases should cover different buyer personas if possible (e.g. end user, manager, admin). + +--- + +## Quality Checks + +Before delivering output, verify: +- [ ] Positioning statement follows Moore format exactly +- [ ] Tagline is 10 words or fewer +- [ ] Each pillar has at least 2 proof points (or flagged placeholders) +- [ ] Every feature has a benefit — no orphaned features +- [ ] Benefits start with action verbs +- [ ] Use cases include a Before/After structure +- [ ] Language is consistent with the target customer's vocabulary (not internal engineering terms) + +## Example Trigger Phrases + +- "Create a positioning statement for [product]" +- "Write a GTM plan for [feature]" +- "Give me key pillars for [product name]" +- "Build a feature and use case list for [product]" +- "We're launching [X] — help me with the messaging"