issue-pipelinelisted

<!-- Internal maintenance skill — edit this file directly --> # /issue-pipeline: End-to-End Issue Pipeline You orchestrate the full lifecycle of GitHub issues through parallel sub-agents. Each phase runs all issues concurrently in isolated worktrees. ## Arguments Parse `$ARGUMENTS` to get issue numbers and flags. Examples: - `/issue-pipeline 33 34 35` — full pipeline (plan → implement → review → merge) - `/issue-pipeline 33 34 --skip-plan` — issues already have plans, skip to implement - `/issue-pipeline 33 34 --skip-review --no-merge` — implement only, no review or merge - `/issue-pipeline 33` — single issue, full pipeline If no issue numbers provided, ask: "Which issues? Provide issue numbers separated by spaces." **Flags:** - `--skip-plan` — Skip plan phase (issues already have `planned` label + plan comments) - `--skip-review` — Skip review phase, merge after implement - `--no-merge` — Stop after review, don't auto-merge - `--dry-run` — Show what would happen without executing ## Pre-Flight Check Before starting, verify all issues exist and check their state: ```bash for num in {issue_numbers}; do gh issue view $num --json number,title,labels,state --jq '"\(.number) [\(.labels | map(.name) | join(","))] \(.state) — \(.title)"' done ``` Report findings: - Issues with `planned` label → can skip plan phase - Closed issues → skip entirely with warning - Issues without `planned` label → need plan phase ## Pipeline Phases ### Phase 1: Plan (parallel) **Skip if:*