assesslisted

Assess an existing codebase and set a rebuild/modernization strategy. Target and context: $ARGUMENTS (when no path is given, the brief's Kind line names it) 0. Precondition: docs/BRIEF.md with `Status: approved` or `revised` and `Kind: 레거시 (<path>)` (from the injected board's Brief line, else Grep those two lines — the one file read allowed here) — the brief holds why the rebuild happens, the target state, what must not change and the deadline. If there is none, or it is still whiteboard or draft, say so in one sentence — "run `/brainstorm <why, target state, what must not change, deadline>` or `/brainstorm <path of a document you wrote>` first" — and stop; with `Kind: 신규`, say so and suggest `/kickoff` 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. Load the `legacy-assessment` skill. Send the Explore subagent out per area in parallel to gather the inventory, and have team-planner compile docs/ASSESSMENT.md — pass the Explore reports to it verbatim, do not re-summarize, and name docs/BRIEF.md so it marks every "looks like a bug" item that conflicts with the brief's target state or invariants. 2. Report unknowns in chat, then get the preserve/fix policy in one AskUserQuestion call (split only if the tool limits question