kata-plan-issue

# kata-plan-issue ## Operating Brief When this skill is invoked, help the user turn a standalone request into one durable backlog issue in a backend that supports `issue.create`. Use a staged planning workflow: explore context, ask focused clarifying questions, propose viable approaches with trade-offs, get approval on one approach, present a visible self-reviewed design for approval, then do planning-depth classification and planning research before presenting a visible self-reviewed implementation plan. Do not create local design or plan markdown files; after both approvals, persist both documents together in one backend issue through `issue.create`. Use this for slice-sized work that should be planned and executed in isolation, not attached to a milestone roadmap. The created issue body must contain both `# Design` and `# Plan` sections, but do not draft those sections in the same turn as the approach options and do not write the plan immediately after design approval without planning research. ## Success Criteria - The user chose or approved one approach before seeing the design. - The design was self-reviewed and a concise self-review summary was shown before design approval. - The user approved the design before implementation planning began. - The plan depth was classified as fast, research, or reviewed before plan drafting. - Planning research was performed at the selected depth before the plan was shown. - Reviewed-depth plans used a reviewer subagent when avai...