create-issueslisted

# Create Issues Use GitHub as the single source of truth for work tracking. This skill turns roadmaps, PRDs, and SPEC files into stable, linked, verifiable GitHub Issues. If the repository is not on GitHub or `gh` is not authenticated, stop and invoke `/create-agent-harness` first. ## When to Use - Converting `ORCHESTRATOR-ROADMAP.md` or `.specs/SPEC-*.md` into GitHub Issues. - Slicing an Epic into small, vertical, trackable Issues. - Creating a new batch of Issues from a release plan or PRD. - Keeping roadmap, Epics, and GitHub Issues in sync. - User asks or mentions this skill in English (e.g., "use /create-issues", "run create-issues"). - O usuário pede ou menciona esta skill em português (ex.: "use /create-issues", "execute create-issues"). ## When NOT to Use - Do not use when the only task is to close or modify existing Issues — use GitHub directly. - Do not use when GitHub access is not confirmed. ## Prerequisites - `gh` CLI installed and authenticated. - Remote `origin` pointing to the correct GitHub repository. - `ORCHESTRATOR-ROADMAP.md` or `.specs/SPEC-*.md` with the work to track. Check access with: ```bash gh auth status gh repo view ``` ## Epic Traceability Contract Every Epic must have: 1. A stable identifier in the format `E10`, `E11`, `E12`. 2. A matching GitHub Issue. 3. A direct link to that Issue in the roadmap or spec. 4. Description, state, and success criteria kept in sync with the Issue. Required roadmap format: ```markdown ## Epics - [