keel-planlisted

# keel-plan — Implementation Planning Write the plan for an engineer with zero context for this codebase and questionable taste. Every ambiguity you leave is a decision they will make wrong. ``` INPUT an approved spec (keel-discover) or requirements clear enough to name exact file paths OUTPUT a plan file: header (Goal, Spec Version, Global Constraints, Success Criteria) + tasks each carrying Delivers / Files / Interfaces / Skills, no placeholder phrases ``` Missing INPUT → `BLOCKED: 缺 <approved spec | requirements naming exact file paths> → 退回 keel-discover`. This is the INPUT-contract miss every stage declares; it is distinct from the spec-status gate below, which fires when a spec *exists* but is not yet approved. **If INPUT is the spec path**, the spec's `Status:` field must read `approved` before this skill proceeds; otherwise `BLOCKED: spec 未核准 → 退回 keel-discover`. This check is scoped to an actual spec file — it does not apply to the "requirements clear enough to name exact file paths" path or the Medium-task lightweight shortcut below, neither of which has a spec file to check. ## When to skip Single-file reversible changes don't need a plan file. Medium tasks (multi-file, under half a day) may use the lightweight path: dispatch the `planner` agent (by name, never `general-purpose`; **do not pass a `model` override**) for a one-shot plan you review in-conversation, skip the artifact. This skill's full artifact is for work that will be