kickofflisted

Start a new project from the approved product brief. Note: $ARGUMENTS The brief's approval was the CEO's "go": from here the team decides and logs; the CEO answers one question (the stack — the most expensive decision to reverse — and the budget) and anything on the escalation list, nothing else. Every step is re-entrant: an output that already exists (the file, the commit) is skipped. 0. Precondition: docs/BRIEF.md with `Status: approved` or `revised` and `Kind: 신규` (from the injected board's Brief line, else Grep those two lines — the one file read allowed here). If there is none, or it is still whiteboard or draft, say so in one sentence — "run `/brainstorm <idea, or the path of a document you wrote>` first" — and stop; with `Kind: 레거시`, say so and suggest `/assess <path>` instead. If CLAUDE.md has no "## Language" section (a brief committed from elsewhere), ask the CEO the working language with AskUserQuestion (options: ko / en / other; default: the language of the brief), run `node .claude/scripts/set-language.mjs --file CLAUDE.md <code>`, and continue in that language. 1. One team-planner call: (a) derive docs/CHARTER.md from docs/BRIEF.md per the `charter` skill (under 60 lines, `Source: docs/BRIEF.md`; a slot the brief leaves undecided gets the planner's default with the reason and a docs/DECISIONS.md line — never a guess presented as fact); (b) write docs/adr/0001-stack.md with 2–3 stack/architecture alternatives and a recommendation, `Status: proposed`, its Contex