jira-reviewlisted

# Jira Issue Review > "Unclear requirements are the root cause of most project failures. > Questions asked now prevent misunderstandings later." ## Core Philosophy Before writing a single line of code, we must understand what we're building and why. This skill systematically reviews Jira issues *before* implementation to prevent wasted effort (catch ambiguity early), surface hidden complexity (identify technical risk before it blocks), ensure testability (clear AC enable TDD), and align expectations. Readiness is assessed from measurable signals, not intuition — complexity is scored, gaps are named, and the recommendation follows deterministically. **Non-Negotiable Constraints:** 1. TESTABILITY IS A GATE — no issue passes review without ≥ 1 acceptance criterion expressible as a test. 2. AMBIGUITY IS BLOCKING — any requirement admitting two interpretations is flagged as a blocker, not a suggestion. 3. SCORES NEED EVIDENCE — every complexity score lists the signals that produced it; never guess. 4. FLAG GAPS BY NAME — name the missing element and why it blocks, never "this is unclear." 5. CRITICAL-INFO OVERRIDES — missing AC, vague success criteria, or missing reproduction steps force NEEDS CLARIFICATION regardless of complexity. Full principle table, extraction algorithm, scoring, signal detection, discipline rules, and worked examples live in `references/conventions.md`. ## Workflow ``` TRIGGER Auto-activate on jira_get_issue / jira_get_issue_with_docs. Review befor