sprintflint/agent-skills

Overview

This skill manages SprintFlint projects, sprints, issues, and comments through the SprintFlint REST API. It helps automate common ticketing tasks like creating projects, starting sprints, creating or updating issues, and tracking sprint progress. Authentication uses an X-API-Token supplied via the SPRINTFLINT_API_TOKEN environment variable.

How this skill works

The skill issues REST calls to the SprintFlint API base URL (https://sprintflint.com/api/v1) to list, create, update, and delete projects, sprints, issues, and comments. It sends the X-API-Token header for authentication and handles standard HTTP responses and validation errors. Responses map to Project, Sprint, Issue, and Comment schemas so you can read counts, story points, status, timestamps, and identifiers for automation and reporting.

When to use it

• Create or update projects and project metadata.
• Create, activate, complete, or delete sprints and manage sprint dates.
• Create, update, move, or delete issues (tickets) within a sprint.
• Add, edit, or remove comments on issues and retrieve discussion history.
• Automate sprint progress tracking, velocity calculation, and reporting.

Best practices

• Set SPRINTFLINT_API_TOKEN in the environment before calling the API and verify token permissions.
• Validate required fields (name/title, start/end dates for sprints) before sending requests to avoid 422 errors.
• Use status values exactly as defined: backlog, todo, in_progress, done, cancelled.
• Paginate or filter lists if you expect many projects, sprints, or issues to avoid large responses.
• Handle 401/403/404/422 responses explicitly and present clear user guidance on missing permissions or validation failures.

Example use cases

• Create a new project, add an initial sprint, create backlog issues, then activate the sprint programmatically.
• Update issue story points and status during daily standups to keep sprint metrics accurate.
• List sprints for a project and compute velocity from total and completed story points for reporting.
• Add a comment to an issue to log decisions or link to external resources.
• Delete or archive test sprints and issues as part of cleanup or environment resets.