implement-issueslisted

# Implement Issues Turn a set of GitHub issues into open PRs via parallel, worktree-isolated lanes. One lane per issue: its own worktree, its own branch, its own PR. This skill orchestrates and composes `branch`, `commit`, and `pr` — it **never merges**. Hand-off to `babysit-pr` / `babysit-pr --merge` for shepherding and merge. ## Invocation - `/implement-issues #12 #14 #17` — implement exactly these issues. - `/implement-issues` (bare) — triage the backlog (`gh issue list`), prefer self-contained, file-disjoint issues, **propose a set and confirm before spawning** any lane. - `--sequential` — run one lane at a time (still one worktree/branch/PR each). ## Inputs & readiness - **Load repo context first.** At start, from the target repo checkout root, read `AGENTS.md` and/or `CLAUDE.md` if present. **Precedence:** `AGENTS.md` is authoritative when both exist — do not also apply conflicting `CLAUDE.md` instructions; if only one exists, use that file; if both conflict in a blocking way, stop and ask. Record which filename is authoritative (e.g. `AGENTS.md` or `CLAUDE.md`) and treat its house standards, operating agreement, and standing constraints as **binding** for every lane. Pass that chosen filename into each lane prompt so lanes do not re-pick. See the `stand-general` skill's **Per-repo agent context** section for the expected file shape. Missing the file is fine — fall back to chat instructions and `stand-*` skills. - Take issues from the args,