From atlassian-suite
This skill should be used when the user asks to "manage sprint", "create a sprint", "add issues to sprint", "start/close sprint", "list sprints", or runs `/atlassian-suite:jira-sprint`. Handles sprint lifecycle on a Scrum board (list/create/start/close, add/remove issues).
npx claudepluginhub acendas/acendas-marketplace --plugin atlassian-suiteThis skill is limited to using the following tools:
Run sprint lifecycle actions on a Scrum board.
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.
Run sprint lifecycle actions on a Scrum board.
$1 = Board ID or name.
$2 = Action (list, create, start, close, add, remove).
$3+ = Action-specific args.
Resolve board (numeric ID or fuzzy match via mcp__acendas-atlassian__jira_get_agile_boards).
Branch on action:
list → call jira_get_sprints_from_board. Render: {id} {name} {state} {start→end}.
create → ask for name, start date, end date, optional goal. Confirm, then jira_create_sprint.
start → require sprint id, start/end dates. jira_update_sprint with state=active.
close → require sprint id. jira_update_sprint with state=closed. Warn that incomplete issues will move to backlog.
add → require sprint id + issue keys (comma-separated). jira_add_issues_to_sprint.
remove → use jira_add_issues_to_sprint against the backlog sprint (sprint id 0 or the project's backlog), since Jira's API removes issues by re-assigning. If the API rejects this, explain the workaround (move via another sprint).
Confirm before any write. Sprint state changes are visible to the whole team — surface the impact before acting.