sprint-context-loader·integration·active

Sprint Context Loader

Pulls sprint metadata — name, dates, team, release tag, prior trend data — directly from connected issue trackers via MCP.

ARIAtrigger · mcp⌘ MCP · Atlassian

Pulls sprint metadata — name, dates, team, release tag, prior trend data — directly from connected issue trackers via MCP.

When this skill fires

·An ARIA report is generated and needs to identifywhich sprint

·Trend Detector needs the prior 4–6 sprints' data for comparison

·An engineer runs ARIA without specifying a sprint context (it auto-detects from the active sprint)

What gets loaded

Current sprint

·Sprint name + ID

·Start date, end date

·Team or squad

·Release tag (if one is associated)

·Total story points / issue count

·Goal statement (the team's stated objective)

Historical sprints

·Last 4–6 sprints by the same team

·Issue counts, story points, completion rate

·Aggregated agent metrics from prior runs (test counts, pass rates, finding counts)

People

·Sprint participants (for attribution in retros)

·Active reviewers (for routing remediation PRs)

Why metadata matters

→A quality report without sprint context is just a snapshot. A quality reportwith sprint context can compare to the prior 4 sprints, identify trends, and tell the team"this is your worst test pass rate in 6 weeks" — which is what makes the report actionable instead of decorative.

Connector specifics

This skill uses the Jira MCP by default but adapts to the connected tracker:

·Jira — sprint API, agile board API

·Azure DevOps — iteration API, work item links

·Linear — cycle API

·GitHub Projects — iteration field on the project, custom fields for sprint association

If multiple trackers are connected, ARIA picks the one tagged primary. If none is, it asks the engineer once and remembers.

Caching + freshness

Sprint metadata is cached for 5 minutes. Trend data (prior sprints) is cached for 1 hour. The cache is invalidated when the sprint dates change or when the engineer passes --refresh.

→Stale sprint data has caused at least one ARIA report to compare to the wrong baseline. The 5-minute current-sprint cache is the result of that lesson.

What it produces

A context object passed to all downstream ARIA skills:

·current_sprint — name, dates, team, release tag, goal

·prior_sprints — array of N prior sprints' metadata + agent metrics

·participants — engineers active in the sprint

·tracker_links — direct URLs back to the tracker for everything cited

The tracker links are what make ARIA reports drill-down friendly. Every claim has a hyperlink to the source.

MCP server endpoint

mcp://jira.atlassian.com

vendor · Atlassian

Related · integration

Jira MCP

mcp-jira

Bidirectional Jira connector. TARA pulls stories from sprints; ARIA pushes findings, recommendations, and quality reports back as issues, comments, or sprint reviews.

TestRail MCP

mcp-testrail

Pulls existing test cases and execution history; pushes EVAN-generated tests and run results back as cases, runs, and milestone reports.

Azure DevOps MCP

mcp-ado

Pulls work items + repos; pushes test plans, suites, and runs. Handles ADO test points and outcome states with full bi-directional sync.

GitHub MCP

mcp-github

Reads PRs, issues, code search; opens PRs containing EVAN-generated automation, SARA remediation patches, and ARIA-recommended changes.

Confluence MCP

mcp-confluence

Reads PRDs and ACs from Confluence pages as TARA input. Publishes ARIA's quality reports back as Confluence pages with embedded charts.

Slack MCP

mcp-slack

Real-time notifications when SARA finds Critical issues, LEO breaches an SLO, or ARIA's trend detector flags a regression. Routed to the right channel by component.