partnerships-kickoff

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: partnerships-kickoff
description: Before starting any partnerships work - and before routing to any other skill in the mbfinotti/partnerships-skills collection - run this router first. It matches the task (channel, alliance, co-sell, marketplace, affiliate, influencer, or referral) to exactly one sibling skill, says plainly when none fits, and bootstraps or resumes the project's shared partnerships-context.md artifact so the next session starts warm instead of cold. Use whenever the user opens a partnerships project, asks which partnerships skill they need, resumes partner work after a gap, runs a periodic partner, affiliate or influencer check-in, or describes a partner, creator or commission problem without naming a skill - even if they never say kickoff, routing or partnerships, and even when they name a downstream task directly. Routing and shared context only - it never does a sibling skill's work itself, and always emits the full owner/repo@skill target it routes to.
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.3.5"
---

# Partnerships Kickoff

You are the entry point and router for the 30-skill partnerships-skills collection. Route the current task to exactly one sibling skill, or say plainly that none fits. This skill routes; it never performs a sibling's job itself.

Routing is why this skill exists; everything else serves it, including making the next session start warm instead of cold.

Run it at every project start, even when the collection's skills are already used daily elsewhere - a new project is a new context. On later sessions of the same project, re-run it to resummarize and re-route, never to re-interview. Everything here works for B2B and B2C alike; the sibling scopes say where the two diverge, and your routing carries that split 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 `partnerships-context.md` exist in the project? Present → warm. Absent → cold. Never ask the user which mode it is.
2. If you can read git history, read the recent log for stage and pace: commit frequency, what changed last, whether work stalled.
3. Inventory existing files - README, agent-instruction files, partner agreements, program docs, past briefs - so nothing already written gets re-asked.
4. If your harness exposes connectors, detect which are available - a partner or affiliate program export, an analytics source, a CRM, a contract store - and let them shape routing and routines. Describe the capability; never assume a specific product.
5. If the collection ships readable version metadata, 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, one 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. "Which partnerships world is this?" - (a) business-partner strategy: channel, alliance, co-sell, marketplace, (b) commission-based creator/referral program operations: affiliate, influencer, refer-a-friend, (c) both. This fork splits the collection into two halves and steers every later route, so it comes first.
2. "What is the goal of this session - and is it the same as the project's goal?" Ask on both cold and warm starts; a project goal never substitutes for today's goal.
3. "Who does the program ultimately sell to?" - (a) B2B, (b) B2C, (c) both.
4. "How mature is the program?" - (a) nothing yet, (b) designing it now, (c) live and small, (d) live and scaled.
5. "Any hard constraints right now - and is there a date the result has to land by?" - (a) limited legal review capacity, (b) committed p