Jira Todo - Daily Work Prioritization

Analyzes assigned tickets and recommends what to work on next, based on actual Jira data. Complements the jira-cli skill (general command reference) and jira-daily (yesterday's standup recap): this skill is for forward-looking prioritization.

Phase 1: Verify Jira CLI Works

Before anything else, confirm the CLI is installed and authenticated:

jira me

If that fails (command not found, not authenticated, any error), STOP here. Do not proceed to Phase 2 or any later phase, and do not simulate, infer, or fabricate ticket data to produce a plan anyway. Tell the user:

The jira CLI isn't available or isn't authenticated in this environment. Install and configure it from https://github.com/ankitpokhrel/jira-cli, then re-run this skill.

This gate exists because an agent that can't reach real Jira data will otherwise write a plausible-looking report from imagined tickets and present it as a real daily plan. Every ticket ID, priority, status, and story point anywhere in this skill's output must come from a jira command actually run this session: never a hardcoded fixture, a "simulated" placeholder, never mention a blocker that wasn't explicitly marked (label or blocking-link field) in that output, and never a helper script that was written but not executed. If a command returns no results, say so plainly rather than inventing tickets to fill out the report sections.

Phase 2: Determine Project Key