batch-linear-tickets

# Batch Linear Ticket Resolver Orchestrate parallel analysis and resolution of multiple Linear tickets — bug fixes **and** feature work. This skill owns batch-level concerns: per-ticket type classification, parallel fan-out of the right analysis tools, cross-ticket correlation, the user-facing approval gate, and Linear writeback. Per-ticket investigation lives in `linear-ticket-investigator`. Per-ticket bug root-cause analysis is dispatched to the `rca-investigator` agent — it runs `holistic-analysis` (`fix`) + `confidence` (`analysis`) in an **isolated context per ticket**, so N bug analyses run in **parallel** and none of their verbose walkthroughs land in this orchestrator's window. Per-ticket planning lives in `aw-planner`. Per-ticket implementation lives in `aw-executor`. This skill wires them together for batch operation. ## Architecture ```text Phase 1: Per-Ticket Analysis → per ticket: classify type → investigator → (video-analyser if video flagged) → (rca-investigator if bug, carries confidence) | confidence(plan) if feature Phase 2: Cross-Ticket Correlation → detect shared root causes, file conflicts, duplicates Phase 3: Approval Gate → user picks tickets to ship Phase 4: Parallel Execution → fan out aw-planner + aw-executor for approved tickets Phase 5: Results & Linear Updates → status table + per-ticket PR comments ``` Phase 1's analysis runs **once per ticket**. Phase 4 dispatches `aw-planner` directly using the analysis from Phase 1. --- ...