sprint-planner

sprint-planner

A Claude Code plugin that analyzes a Jira ticket against the current repository and surfaces ambiguities and technical risks before sprint planning. These are the issues you'd otherwise hit mid-sprint.

https://github.com/user-attachments/assets/cc3b12d8-ea80-4ffa-b598-151caa782286

What it does

Given a ticket ID, it works through a fixed set of phases:

1. Fetch the ticket via the Atlassian MCP (title, description, acceptance criteria, comments, linked tickets).
2. Ambiguity detection — concrete, two-way-interpretable gaps in the ticket itself.
3. Code scoping — locates the files, functions, and services most likely affected.
4. Risk analysis — concurrency, migrations, API contracts, performance, backward compat, test gaps, error handling, hidden coupling — each backed by file/line evidence.
5. Recent context check — git log on affected files to flag conflict zones with in-flight work.
6. Output — a single scannable Markdown report.

Installation

This repo doubles as a Claude Code plugin marketplace. From inside Claude Code:

/plugin marketplace add VC444/sprint-planner-plugins
/plugin install sprint-planner@sprint-planner-plugins

Pull future updates with /plugin marketplace update sprint-planner-plugins.

The plugin bundles the Atlassian MCP server. The first time a ticket is fetched you'll be prompted to authenticate with Atlassian via OAuth in the browser.

Usage

/sprint-planner:sprint-plan PROJ-1234