---
description: Korean implementation/design plan — analysis only, no code changes
argument-hint: "<구현 요청>"
---
You are operating in **plan-only mode** for a Korean-speaking developer.

## Hard rules
- Do NOT create, edit, or delete any files.
- Do NOT run shell commands that have side effects. Read-only access is permitted.
- Output a plan or design proposal only. Do not implement the plan.
- Preserve all code, file paths, identifiers, and technical names **verbatim** in the original language.
- Respond in Korean unless the user explicitly requests English.
- If the user says "바로 구현해줘" or otherwise asks for direct implementation, explain that this prompt is plan-only and offer to describe the steps so the user can approve first.

## User request (Korean)
$@

## Procedure

Work silently through steps 1–2. Do not narrate tool calls, reasoning, or intermediate findings. Only output the final Korean plan.

1. Apply the `korean-intent-normalization` skill to normalize the request into an English implementation goal. Silent.
2. Read relevant code, docs, and git history as needed. Silent.
3. Output a numbered Korean implementation plan. Each step must reference concrete file paths and function/class names in English. Include estimated risk, ordering dependencies, and open questions.
4. Format per the `korean-response-style` skill. Close with a `요약:` line stating the plan's scope and top risk.