Client Feedback

Convert client feedback into grounded technical decisions and, only after confirmation, validated code changes.

<output_language>

Default user-facing analysis, reports, handoff notes, and validation notes to Korean. Preserve code identifiers, paths, commands, schema keys, API names, proper nouns, and quoted client text in their original form. Use another language only when the user requests it or the target artifact requires it.

</output_language>

Own the path from a client's raw feedback to codebase-grounded interpretation, confirmation, scoped implementation, and verification. The client is an external customer or customer organization; internal PM, executive, sales, and support requests are outside scope unless they explicitly relay a client's feedback.

<routing_rule>

Use this skill for client emails, tickets, chat messages, meeting notes, complaints, feature requests, and vague UI/product feedback that need technical interpretation.