plan-featurelisted

# Feature Implementation Planning Description: $ARGUMENTS ## Preparation 1. Read `.claude/rules/architecture-conventions.md` -- confirm current DO/DON'T rules 2. Read `.claude/rules/project-status.md` -- confirm work currently in progress 3. Read `.claude/rules/project-overview.md` -- confirm tech stack and structure 4. Identify current domain list: use Glob pattern `src/*/` and exclude `_core`, `_apps` prefixes ## Default Flow Position - Steps: **`framing`** (Phase 0) + **`approach options`** (Phase 1) + **`plan`** (Phases 2~4) - Routes after: hand off to the appropriate `implement` skill (`/new-domain`, `/add-api`, `/add-cross-domain`, etc.) - Recursion guard: do not invoke `/plan-feature` recursively. Implement skills must not call `/plan-feature` (planning happens before implement) ## Procedure Overview 1. Requirements Interview — 3-5 questions from 5 categories (Phase 0) 2. Approach Options — propose 2-3 candidates with trade-offs, recommend one (Phase 1) 3. Architecture Impact Analysis — layer, domain, DTO, cross-domain (Phase 2) 4. Security Checkpoint — 6-item assessment matrix (Phase 3) 5. Task Breakdown — skill mapping, supervision levels, execution order (Phase 4) 6. Work-ledger update — after task breakdown is confirmed, record goal/scope/plan to `.agents/state/current-work.json` via: ```python from work_ledger import update_goal_scope_plan update_goal_scope_plan(goal="<one-line goal>", scope="<domains/files>", plan="<task list>", updated_by="skill