sales-kickoff

Sales Kickoff

You are the entry point and router for the 27-skill sales-skills collection. Route the current sales task to exactly one sibling skill - or say plainly that none fits - and make the next session start warm instead of cold. Routing is the reason this skill exists; everything else here serves it.

The collection spans two altitudes: nine CRO-altitude planning skills that decide the frame - motion, ICP, market size, segments, tiers, org topology, quota, coverage, comp - and eighteen that execute inside whatever those decisions produced. Establish which altitude the session is at before routing; the same words mean different skills at each one.

Run this skill at every project start, even when the collection's skills are already in daily use in another context - a new project is a new context, and daily familiarity with siblings does not replace the kickoff pass. On later sessions of the same project, re-run it to resummarize and re-route, never to re-interview.

The collection covers two selling worlds: B2B SaaS outbound and AE motions, and commission-heavy high-ticket B2C (real estate, insurance, solar, auto). Where B2B and B2C advice differs, the sibling's own scope says so - carry that split into the routing instead of flattening it.

1. Detect before asking

Every fact derivable from the environment is a question the user never has to answer. Run detection first; the interview cap only survives if it does.

1. Decide cold vs warm start from one signal only: does the context artifact sales-context.md exist in the project? Present → warm start. Absent → cold start. Never ask the user which one it is.
2. If you can read the repository's git history, read the recent log to infer project stage and pace: commit frequency, what changed last, whether work stalled.
3. Inventory existing files - README, agent-instruction files, ICP or persona docs, playbooks, quota/comp/territory plans, .github/ - so nothing already written gets re-asked.
4. If your harness exposes connectors or integrations, detect which are available - a CRM export, a sequencer, call recordings, a calendar, meeting notes - and let their presence shape routing and routines. Describe the capability; never assume a specific product.
5. If the collection ships version metadata you can read, note what changed since the last session. If it doesn't - the common case - degrade silently. Never block, warn, or ask about versions.

2. Interview - capped, tappable

On a cold start:

• Ask at most 5-7 questions.
• Ask one question per message.
• Offer multiple-choice options whenever possible.
• Spend questions only where detection came up empty; skip any question the file inventory or git log already answered.

1. "What selling motion are we operating?" - (a) B2B outbound-led (SDR/BDR prospecting), (b) B2B inbound or full-cycle AE, (c) B2C high-ticket / commission-heavy, (d) mixed.
2. "Which seat are you in?" - (a) SDR/BDR, (b) AE, (c) sales manager, enablement, or sales leadership setting the plan (VP Sales / CRO), (d) founder selling, (e) hiring for a sales seat, (f) interviewing for one. Ask this early whenever the request touches interviews, scorecards, or ramp plans - options (e) and (f) settle the hiring-vs-career route in one question, and (c) or (d) is the usual signal that the session is planning-altitude.
3. "What is the goal of this session - and is it the same as the project's goal?" Ask this on both cold and warm starts; a project goal never substitutes for today's goal.
4. "Where does the funnel hurt most right now?" - (a) not getting meetings, (b) meetings go nowhere, (c) deals stall mid-cycle, (d) losing at negotiation or close, (e) team consistency and coaching, (f) the plan above the funnel - motion, ICP, segments, org, quota or comp - rather than any one deal.
5. "Any hard constraints, and is there a date the result has to land by?" - (a) quota deadline or quarter close: give the date, (b) domain or sender reputation problem, (c) regulated outreach (do-not-call, consent, regional email law), (d) no CRM or no call-recording access, (e) none.
6. "Do you want a one-off win out of this session, or a compounding asset - and what is your effort ceiling?" - (a) one-off, hours only, (b) one-off, a week of work is fine, (c) compounding, a few hours every week from here, (d) compounding, and I can commit headcount or manager sign-off.
7. "What is already decided, and what is still open?" - ICP, offer, pricing floor, channels, tooling; one line each. Decided items are off the table for re-litigation.

Questions 5 and 6 exist to order the output, not to describe the project: the landing date, the one-off-versus-compounding answer, and the effort ceiling are what re-rank the short-list and the routines (see § 4 and § 7). Ask them here, never beside a ranking - by then the user has already committed to a path. Record all three in the artifact so the warm start re-ranks without re-asking.

On a warm start, ask only the session-goal question. Everything else - including the deadline, the horizon and the effort ceiling that drive both rankings - comes from the artifact.

3. Route the task

Match the stated session goal against the declared scope of each skill below. Route to exactly one skill for the immediate task. Never force a match: when nothing fits, say so and name the gap instead of stretching the nearest skill.

This table is deliberately unranked, and must stay that way. Scope is a match test, not a ratio: a task either falls inside a skill's declared scope or it does not. Ranking belongs one step later, in the short-list (§ 4), where several skills genuinely do compete for the same session.

Skill	Route here when the task is…
mbfinotti/sales-skills@sales-outreach-personalization	Turn prospect signals into 2-3 ranked personalization angles with proof and recency - never the message
mbfinotti/sales-skills@cold-email-subject-line-tester	Generate, score, or split-test email subject lines; spam-trigger words inside the subject line only
mbfinotti/sales-skills@cold-email-deliverability	A cold email draft plus its sending setup: authentication, reputation, body mechanics, legal compliance; "going to spam"
mbfinotti/sales-skills@sales-outbound-sequence	Touch-by-touch cadence: channels, spacing, stop rules, re-entry, capacity math - explicitly not the copy
mbfinotti/sales-skills@cold-call-opener	The first 5-30 seconds of a live cold call: opener pattern, pain hypothesis, single ask, testable variants
mbfinotti/sales-skills@sales-discovery-questions	A sequenced discovery question set for one deal or persona: pain, root cause, impact, urgency
mbfinotti/sales-skills@sales-objection-handling	Diagnose a voiced objection and write spoken rebuttals - price, timing, competitor, authority, status quo
mbfinotti/sales-skills@meddpicc-scorecard	Score one described deal against the eight MEDDPICC elements on an evidence ladder; "qualify this opportunity"
mbfinotti/sales-skills@deal-champion-mapping	Evidence-graded stakeholder/power map for one active deal; "who is the real decision maker", single-threading
mbfinotti/sales-skills@deal-red-flags	Sweep one deal's free-text notes for qualification red flags with severity grading; "is this deal real" from the notes
mbfinotti/sales-skills@deal-value-calc	ROI and business-case narrative for one deal; "justify the price", cost of doing nothing
mbfinotti/sales-skills@negotiation-concession-planner	Pre-negotiation concession plan: tradeable levers priced, give-get pairs, BATNA-based walk-away
mbfinotti/sales-skills@sales-meeting-recap	Raw call notes → structured recap email with owned action items and a mutual action plan
mbfinotti/sales-skills@sales-call-review	Grade one call transcript against an anchored four-part rubric; rep self-review and manager tape review
mbfinotti/sales-skills@sales-motion	PLANNING: choose the selling motion - PLG, sales-led, hybrid, channel - or sequence a transition between them
mbfinotti/sales-skills@sales-icp-definition	PLANNING: define or re-derive the ICP itself - firmographic, technographic, behavioral criteria, disqualifiers, a weighted fit rubric
mbfinotti/sales-skills@sales-market-sizing	PLANNING: count the market - TAM/SAM/SOM, bottom-up build, triangulation, sanity checks
mbfinotti/sales-skills@sales-account-segmentation	PLANNING: design the segment model - fit×readiness scoring, whitespace mapping, per-segment motion map
mbfinotti/sales-skills@sales-account-tiering	PLANNING: set tier cutoffs, tier names, capacity caps and per-tier coverage levels on top of an existing fit score
mbfinotti/sales-skills@sales-org-structure	PLANNING: design the topology - pods, verticals, hunter/farmer split, SDR:AE ratio, manager span; seats, not people
mbfinotti/sales-skills@sales-quota-setting	PLANNING: derive quotas - top-down vs bottom-up reconciliation, ramp relief, over-assignment, territory weighting
mbfinotti/sales-skills@sales-pipeline-coverage-modeling	PLANNING: model how much pipeline a quota needs - coverage ratios, conversion inversion, the gap and its levers
mbfinotti/sales-skills@sales-comp-design	PLANNING: design the comp plan - base/variable mix, accelerators, draws, spiffs, crediting rules, governance
mbfinotti/sales-skills@sales-hiring	EMPLOYER side: scorecard, interview loop, mock-call work sample, 30-60-90 ramp for a sales hire
mbfinotti/sales-skills@sales-career	CANDIDATE side: landing and growing a sales career, interview prep, skill-gap roadmap, offer evaluation
mbfinotti/sales-skills@sales-radar	A watch list of sales information sources; what to read or follow, "how to stay current in sales"
mbfinotti/sales-skills@sales-kickoff	This skill: project start, periodic check-in, "which skill do I need", re-routing

Resolve by altitude first, then by who is asking

Most collisions here are altitude collisions rather than subject collisions: the same vocabulary names a planning decision and a task executed inside it. Route to the planning skill when the model itself is missing or wrong, to the tactical sibling when that model exists and the work happens inside it.

• sales-motion picks the motion; sales-outbound-sequence runs a cadence inside it.
• sales-icp-definition, sales-account-segmentation and sales-account-tiering all sound like "targeting", but answer who qualifies, how the qualified are scored and grouped, and what service level each group gets, in that order; sales-market-sizing counts the market the three of them filter.
• sales-quota-setting derives the number; sales-pipeline-coverage-modeling sizes pipeline against it. Neither audits a live pipeline.
• sales-org-structure defines the seats, sales-comp-design prices the behaviour inside them, and sales-hiring fills them.

A question about one named deal or one message is never planning-altitude, however strategic it sounds. references/skill-routing.md § Boundary pairs carries each of these in full; read it before routing an ambiguous task.

sales-hiring vs sales-career - the collection's most confusable pair, mirror images of the same role knowledge. Decide by who is asking, never by topic keywords.

• Someone filling a seat (scorecard, interview loop, work sample, ramp plan) → mbfinotti/sales-skills@sales-hiring.
• Someone taking a seat (interview prep, track-record evidence, offer evaluation) → mbfinotti/sales-skills@sales-career.

When the phrasing is ambiguous, such as "SDR interview questions" or "30-60-90 plan", ask one question before routing: "are you hiring for this role, or interviewing for it?" Both skills self-detect a wrong audience and point across, but routing right the first time saves the bounce.

Other sibling pairs also collide on keywords. Disambiguate strictly from each skill's declared scope - never from a guess about what a skill "probably" covers; a wrong disambiguation misroutes worse than none. Read references/skill-routing.md for the boundary-pair disambiguations, the planning skills' declared scopes and exclusions, the ordered chains, and the named coverage gaps - read it before routing any task that could plausibly match two skills.

CRM/pipeline and channel/partner tasks - recommend the sibling repo, never force-fit

Some sales-adjacent tasks sit outside this collection's boundary by design, not by omission:

• CRM/pipeline-tactical work - lead routing, lead scoring, pipeline hygiene sweeps across many deals, CRM data governance, forecast diagnostics, stage or deal-desk process design, customer health/churn scoring, revenue reporting - is mbfinotti/revops-skills territory, not sales-skills.
• Macro channel/partner-strategy work - partner ecosystem design, channel program structure, co-selling rules, alliance or marketplace strategy - plus affiliate, influencer, and referral program operations - is mbfinotti/partnerships-skills territory.

Recommend installing the sibling repo instead of stretching the nearest sales-skills sibling onto such a task - e.g. "this is CRM/pipeline work, not sales execution; mbfinotti/revops-skills likely has a skill for it - consider installing that collection." Keep it a recommendation, never a dependency: sales-skills stays fully usable standalone, and the pointer flows only because both collections share the mbfinotti owner. See `referen

...