Sprint Management Tools
Create, populate, start, and close sprints.
Manage your entire sprint lifecycle from the terminal. Create sprints, move issues in, start, and close — all without opening your project tracker.
list_sprints
Lists active and upcoming sprints with their start/end dates, issue counts, and status.
When it runs: Called when you ask about sprints or sprint status.
Example trigger: "What sprints do we have?"
create_sprint
Creates a new sprint with an optional name, start date, and end date.
When it runs: Called when you ask to create or set up a new sprint.
Example trigger: "Create a new sprint starting next Monday"
| Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Sprint name |
| start_date | string | No | Start date (ISO 8601 format) |
| end_date | string | No | End date (ISO 8601 format) |
| goal | string | No | Sprint goal description |
move_to_sprint
Moves one or more issues into a sprint. Resolves the sprint by name — you don't need the sprint ID.
When it runs: Called when you ask to add tickets to a sprint or plan sprint contents.
Example trigger: "Move the auth tasks into Sprint 12"
| Parameter | Type | Required | Description |
|---|---|---|---|
| issue_keys | string[] | Yes | Issue keys or natural language references |
| sprint_name | string | Yes | Sprint name to move issues into |
manage_sprint
Start or close a sprint. Starting a sprint activates it. Closing a sprint completes it and moves unfinished issues.
When it runs: Called when you ask to start or close a sprint.
Example trigger: "Close the current sprint"
| Parameter | Type | Required | Description |
|---|---|---|---|
| sprint_name | string | Yes | Sprint name |
| action | string | Yes | "start" or "close" |