specrail-implement-queue

# SpecRail Implement Queue Use this skill for approved-spec implementation queues. For one small issue, route to `skills/specrail-implement/SKILL.md` instead. ## Startup 1. Run the SpecRail workflow startup: - read `AGENTS.md`, `AGENT_USAGE.md`, `workflow.yaml`, `states.yaml`, `labels.yaml`, and `skills/specrail-workflow/SKILL.md` when present - select the locale - identify the `implement` route and human gates 2. Fetch current remote state before mapping the queue. 3. List open issues, open PRs, local branch, dirty files, and worktrees. 4. For each candidate issue, read: - the GitHub issue - `docs/specs/GH<issue-number>/product.md` - `docs/specs/GH<issue-number>/tech.md` - `docs/specs/GH<issue-number>/tasks.md` 5. Map existing PRs before creating replacement PRs. 6. Collect duplicate-work evidence before opening an implementation lane: ```sh python3 checks/github_duplicate_evidence.py --github-repo <owner/repo> --issue <issue-number> --json > duplicate-work-evidence.json python3 checks/route_gate.py --repo . --route implement --issue <issue-number> --state ready_to_implement --duplicate-evidence duplicate-work-evidence.json --json ``` If duplicate evidence is missing, the implementation route needs human input. If it shows an open PR for the issue, the route is blocked. If it shows only a matching remote branch, an ownership decision is needed before creating a competing branch or PR: in `auth_mode: review`, stop and ask; in `auth_mode: auto`, ...