pm-to-issueslisted

# PM To Issues Turn approved work into GitHub Issues. Two sources, one rule: **every issue is a complete vertical slice** — user-visible value from input to output, never horizontal layers ("build the model layer"). Any developer can pick up one issue and ship it independently. ## Safety gate (always first) ```bash git config --get remote.origin.url ``` **Only proceed if the remote is a GitHub URL, and only ever create issues in the repository that remote points to.** No remote or non-GitHub → stop and tell the operator. ## Source A — a generated tasks.md exists (`.specify/features/{slug}/tasks.md`) 1. Parse the tasks with their IDs, descriptions, acceptance criteria, and dependencies. 2. Create one issue per task (format below), **dependencies first**, so earlier issue numbers can be referenced by later ones. 3. Write the created issue numbers back into `tasks.md` next to each task. ## Source B — spec only Slice the spec yourself: for each distinct piece of user-visible behaviour — `SLICE` (one-sentence outcome), `SCOPE` (files/components), `DEPENDS ON`, `SIZE` (S/M — split anything L). ## Issue format ```markdown ## What {1–2 sentences of user-visible behaviour} ## Why {which epic this belongs to and why it matters} ## Acceptance Criteria - [ ] {specific, testable} ## Notes {constraints the developer needs — never prescriptive implementation} ## Dependencies {issue numbers that must merge first, if any} ``` Create with `gh issue create --title … --body … --lab