tickets

Analyze and prioritize tickets — tech lead perspective: effort, priority matrix, dependencies, risks

Input: $ARGUMENTS — ticket IDs, a file path, or pasted ticket content.

Apply the dog:ticket-analysis skill to analyze tickets from a tech lead perspective.

Input handling:

  • IDs (numbers like "5184, 5190"): fetch via available tools, or ask user to paste content
  • File path: read the file and extract ticket content
  • Pasted content: parse directly
  • Empty: ask user to provide tickets

The skill will:

  1. Score effort using Fibonacci (1–8 pts) with the ">2min to estimate = needs refinement" rule
  2. Apply priority matrix: URGENT×IMPACT → P0 🔴 / P1 🟡 / P2 🟠 / P3 ⚪
  3. Flag per ticket: 🔄 Dep, 🏗️ Arch, ⚠️ Risk, 🌀 Vague, ✂️ Split, 🔬 Spike
  4. Map dependency chains and identify blockers
  5. Generate executive summary: sprint recommendation, team capacity estimate, risks

Output in PT-BR unless user specifies otherwise.