From atlassian-suite
This skill should be used when the user asks for "sprint status", "current sprint progress", "where are we in the sprint", "sprint health check", or runs `/atlassian-suite:sprint-status`. Produces a concise sprint progress report with completed/in-progress/blocked breakdown, scope changes, and burndown signal.
npx claudepluginhub acendas/acendas-marketplace --plugin atlassian-suiteThis skill is limited to using the following tools:
Produce a one-screen sprint health report.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Produce a one-screen sprint health report.
$1 = Board ID, board name, or empty (interactive). $2 = Sprint ID/name, or empty (defaults to active sprint).
Resolve the board.
$1 is numeric → use as board ID.$1 is a string → call mcp__acendas-atlassian__jira_get_agile_boards and fuzzy-match.Resolve the sprint. Call mcp__acendas-atlassian__jira_get_sprints_from_board filtered by state=active (or by name match if $2 is provided). If multiple active sprints exist, ask the user.
Pull sprint issues. Call mcp__acendas-atlassian__jira_get_sprint_issues for the sprint. Group by status category: Done, In Progress, To Do, plus a separate Blocked group if any issue has the flagged field set.
Compute deltas. Compare current scope vs initial commitment (look for issues added after sprint start using created > sprintStartDate heuristic via mcp__acendas-atlassian__jira_search). Count story points if the field is populated.
Render the report in this exact shape:
Sprint: {name} ({startDate} → {endDate}, {days_remaining}d left)
Board: {board_name}
Done {n} issues | {points} pts
In Progress {n} issues | {points} pts ({assignees_summary})
To Do {n} issues | {points} pts
Blocked {n} issues | {points} pts ⚠ if > 0
Scope changes: +{added} / -{removed} since sprint start
Velocity signal: {percent_done}% complete with {percent_time_elapsed}% of time elapsed
Highlight risks. Append a Risks section listing any blocked issues by key + summary, plus issues with no assignee or no recent activity (>3 days).
JIRA_PROJECTS_FILTER), the active sprint may not be visible — fall back to asking the user for the sprint name.