create-issues-from-textlisted

# Create Issues from Text ## Purpose Split a complex assignment into multiple clear, structured issues. --- ## Constraints - Preserve original assignment (store in parent or first issue) - Do not implement code - Assign all issues to current user - Use CLI tools --- ## Execution ### 1. Analyze Assignment - Understand scope and dependencies - Identify logical implementation steps ### 2. Propose Breakdown - List steps with short descriptions - Proceed directly to step 3; do not gate on a confirmation round when the breakdown is unambiguous ### 3. Create Issues - One issue per step - Ensure each is independently deliverable - Assign the most relevant existing label to each issue (per `@rules/compound-engineering/general.mdc` *Assign the most relevant existing label when creating a tracker issue*) ### 4. Output - Return list of created issues with URLs --- ## Issue Structure Use the template defined in `templates/issue-structure.md`. --- ## EPIC parent & sub-issues Use this when the assignment is a **cross-cutting mix of requirements spanning multiple parts of the application** (e.g. backend + frontend + mobile, or schema + API + UI). Instead of a flat list of peer issues, build a parent → children tree so the whole effort is trackable from one place. 1. **Pick (or create) the parent.** When the assignment already has a tracker item, that item becomes the EPIC parent. When the assignment is a described task with no tracker item, create the parent issue first, carr