Plan, refine, scope, or divide a NemoClaw GitHub issue into independently valuable capability slices before implementation. Use when a user asks to plan an issue, refine its scope, define acceptance evidence, break it down, split it, or identify the first capability slice. Ask which lifecycle stage they want when a request such as "work on this issue" could mean planning or implementation. Do not use for generic implementation, PR publication, maintainer-loop, or requests without issue-planning intent. Trigger keywords - plan issue, refine issue, scope issue, break down issue, split issue, capability slices, acceptance criteria.