plan-to-issues

# Plan → GitHub Issues Turn a plan already discussed in this conversation into a tracked set of GitHub issues. **No file input, no URL fetching** — the plan lives in the chat history above the invocation. Read it, split it, ship it. Repo is fixed: `corezoid/corezoid-ai-plugin` (this project). All `gh` commands run against the current repo — do not pass `--repo`. ## Non-negotiables - **English only.** Every issue — title, body, labels, milestone title and description — MUST be written in English, regardless of the language the plan was discussed in. Translate the plan as you split it. This is non-negotiable: never publish Russian, Ukrainian, or any other language to GitHub. If a term is a project-specific proper noun (node type name, file path, CLI flag, tool name) keep it verbatim; everything else is English prose. - **Create immediately.** The user has pre-authorised issue creation for this skill. Do not ask "shall I create these?" Do the work and report what was created. - **Every child issue is self-contained** — a coding agent must be able to open the issue and start work with zero extra context. That means: goal, motivation, files/areas, acceptance criteria, verification, and links to related tasks are all inside the body. - **Never invent tasks.** If the plan is vague on a point, mark it in the issue as `> ⚠ Assumption:` rather than silently filling gaps. - **Never post secrets or internal URLs** into issue bodies. Redact if the chat histor...