kickoff
预防中途偏差和返工，适合复杂或不确定任务。
任务开始前诊断未知与假设，澄清范围与优先级。
在动手写代码前先把未知点、假设和优先级理清楚，会帮你找盲区、挑战不合理前提、做短期可丢弃原型或问关键问题来收窄范围。适合碰到复杂或模糊任务、不知道从哪下手时用。特点是交付的是清晰的方向和问题清单，而不是直接产出代码。
▸ 展开 SKILL.md 英文原文
Kickoff (开工) — run before starting any non-trivial task. Diagnoses the gap between what the user asked for (the map) and what the codebase or domain actually requires (the territory), then applies only the techniques needed — blindspot briefing for unfamiliar territory, premise challenges that falsify what's treated as fact, throwaway prototypes and feasibility spikes for "I'll know it when I see it", one-question-at-a-time interviews for ambiguities, reference extraction, and an unknowns-first plan. Use when the user says "kickoff", "开工", "帮我开始", "找找我的盲区", "help me start", "find my unknowns", "what am I missing", "I don't know where to start", or when a previous attempt — theirs or an AI's — came back wrong and they don't know why.
帮我安装这个 skill：https://raw.githubusercontent.com/lusipad/zhizhi/main/skills/kickoff/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/lusipad/zhizhi/main/skills/kickoff/SKILL.md"# Kickoff The user's request is the map. The codebase and the real world are the territory. The difference between them is the user's **unknowns** — and when you hit one mid-task, you guess. This skill spends a little time up front so you guess less later. **The deliverable is clarity, not code.** Kickoff never implements. **Language:** write everything user-facing — briefings, questions, prototypes' copy, plans — in the language the user is speaking. File names and code identifiers stay in English. ## Step 1 — Diagnose (quietly) Read the request, glance at the relevant territory (code, docs, history, and working-tree state — uncommitted changes are territory too), and score the signals