vibe-planninglisted
Install: claude install-skill ZEST-im/vibe-engineering
# Vibe Planning — Kickoff Planning in Six Gates
For developers who have to do the planning too. You ask the questions; the developer
answers; each stage produces artifacts. Planning ends with a project you can start
building in, not with a folder of documents.
**Write every artifact in the language the user is working in.** The templates below use
English headings; mirror them in the user's language when that is what they write in.
## Non-negotiables
- **One question per message.** In Claude Code use `AskUserQuestion`; where that tool does
not exist, ask one concise question directly and wait for the answer — never batch them.
Naming the tool is the point: "the environment's structured input tool, if available" is
an escape hatch, and the rules below assume the question actually got asked. Every option
carries a short
description saying *why the question matters* — the user may not think like a planner.
- **Options are capped at four.** When there are more candidates, group them and label
the last option `(계속)` / `(more)` so the user knows the list was compressed. Never
drop a candidate silently — grouping is already an act of planning, so say you did it.
- **One stage at a time.** Do not draft stage N+1 before stage N is approved.
- **Respect the size caps.** A planning skill that produces a 20-page deck has failed.
- **Never invent facts.** If the user does not know something, it goes in the open
questions table marked `[assumption]` — it does not get qu