CUBRID JIRA Issue Writer

Write a structured JIRA issue saved as markdown to /home/vimkim/gh/my-cubrid-jira/issues/.

Two goals govern every issue:

1. A reviewer can triage it in 10 seconds from the top block alone.
2. A new hire who reads C/C++ but has never opened this subsystem can follow the whole thing on one read — through the writing itself, never by announcing that it was written to be readable.

These two goals fight verbosity from both ends: the triage block stays tiny, the body stays plain, and no fact is told twice. The single most common failure of this skill is the same "why" appearing in the triage, then the Summary, then the Description. The Layer Ownership rule below is the cure — read it before drafting.

When to Use

• User says "write a jira issue", "jira로 작성", "이슈 작성", "리포트 작성"
• User has analysis/findings to document, or wants to formalize a bug report, feature request, or task

Hard Constraints (non-negotiable)