Sprint Tools

Three tools for sprint management: create, update, and complete. All require Team Lead+ role.

Sprint Lifecycle

Sprints follow a strict lifecycle:

Planned (0) → Active (1) → Completed (2)

• A project can have only one active sprint at a time
• Sprints can be moved from Planned to Active via update-sprint
• Completing a sprint must use complete-sprint (not update-sprint)
• Incomplete issues can be moved to a target sprint or unassigned on completion

create-sprint

Create a new sprint in a project.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project to create the sprint in
title	string	Yes	Sprint title (max 255 characters)
start	date	Yes	Start date (ISO 8601, e.g., 2026-04-01)
end	date	Yes	End date (ISO 8601, e.g., 2026-04-14). Must be after start.

Behavior

• Created with Planned status (0)
• Returns sprint with ID, title, dates, status, and issue count

Example Prompt

Create a two-week sprint called "Sprint 12" in the kendo project starting next Monday

update-sprint

Update an existing sprint's title, dates, or status.

Parameters

Parameter	Type	Required	Description
sprint_id	integer	Yes	The sprint to update
title	string	No	New title (max 255 characters)
start	date	No	New start date (ISO 8601)
end	date	No	New end date (ISO 8601). Must be after start.
status	integer	No	0 Planned, 1 Active. Cannot set to 2 Completed — use complete-sprint.

Behavior

• Only provided fields are updated
• Date validation uses merged values (new dates combined with existing ones)
• Cannot change status to Completed — use complete-sprint instead, which handles incomplete issue reassignment

Example Prompt

Activate Sprint 12, we're starting it today

complete-sprint

Complete the active sprint in a project, with optional reassignment of incomplete issues.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project whose active sprint to complete
sprint_id	integer	No	Target sprint for incomplete issues. If omitted, incomplete issues become unassigned from any sprint.

Behavior

• Finds the currently active sprint in the project
• Issues in the Done lane (last lane) are considered complete
• Incomplete issues (not in Done) are either:
  • Moved to the target sprint (if sprint_id is provided)
  • Unassigned from any sprint (if sprint_id is omitted)
• The sprint is marked as Completed
• Throws an error if no active sprint exists

Example Prompt

Complete the current sprint in the kendo project. Move anything that's not done into Sprint 13.

See Also

• Resources — Read sprint data via kendo://projects/{id}/sprints
• Sprints Guide — Understanding sprint lifecycle and planning
• Sprints API — REST endpoints for sprint management