Split Issue Into Subissues

Turn a broad issue into a reviewable dependency graph of bounded child issues. Separate planning from mutation: show the complete decomposition first and create or update issues only after explicit approval.

Required workflow

1. Resolve and inspect the parent

• Resolve the exact issue tracker, repository or project, and parent issue.
• Verify that any local checkout belongs to the resolved parent before inspecting it. When the user supplies issue text without a repository, plan from the supplied evidence and mark repository context as unknown; never adopt an ambient checkout as the target.
• Read the complete parent title, body, attachments, labels, assignees, milestone, comments, and existing child links when available.
• Inspect linked designs, specifications, and repository context needed to understand existing implementation. Use read-only operations during this phase.
• Distinguish facts from assumptions. List missing destinations, content, ownership, or product decisions that could block a child issue.
• Do not create, edit, close, assign, label, or link issues yet.

2. Audit the current state

Summarize: