Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/auditor separation, evidence files, hook compliance are all binding.
End-to-end GitHub issue resolver — fetch, classify, branch, fix with TDD, Codex audit loop, test gate, docs-sync, version bump, PR, and post-merge close-gate finalizer. Use this skill whenever the user wants to fix a bug from a GH issue, asks 'fix issue #N', 'fix bug 115', 'work on issues #123 #456 #789', 'resolve this GH bug', or pastes a GH issue URL/number for resolution. Also handles `question`-labeled issues (inline answer + comment, no branch). REDIRECTS feature/enhancement issues to feature-workflow per rule 47. Supports both single-issue and multi-issue (worktree) pipelines.
Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.
Run a verification iteration — pick something that needs verifying, verify it CU-free, and complete its gate. Use this skill whenever the user wants to verify a shipped feature or bug fix, asks 'verify feature #N', 'verify bug #N', 'run device verification', 'work the verification backlog', or 'close the awaiting-device-verification issues' — and whenever the verify cron fires. Covers BOTH bug close-gate verification (awaiting-device-verification GH issues → closed) and feature Gate-5 verification (docs/features.md DONE → VERIFIED). Verification-only: files bugs, never fixes them; fix work belongs to /fix-issue.
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Drive the iOS Simulator when computer-use can't — for bypassing CU outages, not diagnosing them (use `/cu-diagnose` for diagnosis). Trigger when `mcp__computer-use__screenshot` returns `CU display unavailable`, when the user mentions "CU fallback", "CU substitute", or "drive sim without computer-use", or when continuing a verification that was previously blocked by a CU outage.
Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).