assesslisted

Assess an existing codebase and set a rebuild/modernization strategy. Target and context: $ARGUMENTS 0. If CLAUDE.md has no "## Language" section, first ask the CEO the working language with AskUserQuestion (options: ko / en / other; default: the language of the CEO's message), run `node .claude/scripts/set-language.mjs --file CLAUDE.md <code>`, and continue in that language. Skip when it is already set. 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. 2. Report unknowns and "current behaviour that looks like a bug" to the CEO and get a preserve/fix policy per item. 3. Following the `parity-harness` skill, have team-implementer build the characterization-test / golden-output harness and confirm with team-verifier. No rebuild step starts without the harness. 4. Have team-planner compare strategies (strangler fig / module-by-module replacement / full rewrite) with a recommendation; after team-critic review and CEO confirmation, record an ADR and docs/REBUILD_PLAN.md. 5. Have CLAUDE.md written/updated per the `claude-md` skill (including the harness command). 6. Propose the first rebuild step in plan-document form (do not invoke `/plan` via the Skill tool). 7. Run `hire` via the Skill tool (applied after approval) — a rebuild weights critic and reviewer heavily, so assign in that direction.