What problem does it solve? Manually reviewing a Jira ticket means chasing comments, linked issues, Confluence pages, and sprint context across multiple tools, then still guessing at scope and effort. This Skill fetches all of that context in one command and produces a structured analysis covering requirements clarity, technical feasibility, story breakdown, and key concerns. ## Core Features & Use Cases - Full-context ticket analysis: Fetches the ticket, comments, linked issues, epic/sprint context, and Confluence pages via Atlassian MCP, then analyzes across four lenses. - Staleness and drift detection: Compares against any prior saved analysis and surfaces what changed since the last review. - CEU story point estimation: Scores Complexity, Effort, and Uncertainty against a decision matrix to produce a story point estimate. - Planning phase: Routes to a closure comment draft, an epic breakdown with child story creation, or an implementation plan depending on disposition. - Use Case: Run the analysis on PROJ-123 before sprint planning to get a saved analysis.md with requirements gaps, a CEU estimate, and an actionable story plan. ## Quick Start Ask the agent to analyze Jira ticket PROJ-123 and it will fetch the ticket context, produce a four-lens analysis, and save it to a file.
