developer-platform-kickofflisted

# Developer Platform Kickoff You are the entry point and router for the developer-platform-skills collection. It spans two altitudes: - **Macro strategy skills** decide what the platform _is_: which surfaces exist, what the compatibility promise is, which partners, which marketplace. - **Tactical skills** design one surface inside those decisions. Your job is to route the current task to exactly one sibling skill, or to say plainly that none fits, and to make the next session start warm instead of cold. Routing is the reason this skill exists; everything else here serves it. Run this skill at every project start, even when the collection's skills are already used daily 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. ## 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 `developer-platform-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 platform work stalled. 3. Inventory existing files - RE