kata-execute-issue

# kata-execute-issue ## Operating Brief When this skill is invoked, execute one standalone backend issue created by kata-plan-issue in a backend that supports issue operations. If the user did not provide an issue reference, list open standalone issues with `issue.listOpen` and ask the user to choose. If the user provided an issue number, Kata ID, or partial title, match it against open standalone issues, retrieve the matching issue with `issue.get`, summarize it with a link, and ask for confirmation before execution. After confirmation, follow subagent-driven development as closely as possible: fresh implementer subagent per task, spec compliance review first, code quality review second, review loops until approved, then the next task. Update the issue status through `issue.updateStatus`. ## Success Criteria - The selected standalone issue is confirmed by the user before execution starts. - The issue design and plan are retrieved from the backend, not from a local markdown plan file. - Each plan task is implemented by a fresh subagent with full task text and curated context. - Each task passes spec compliance review before code quality review starts. - Reviewer findings are fixed and re-reviewed before moving to the next task. - A final whole-change code review runs after all tasks complete. - The backend issue status reflects real execution state. ## Do Not - Do not execute without confirming the selected issue with the user. - Do not load all open issue bodies when...