# SprintFlint

> SprintFlint is a sprint management platform for agile engineering teams. It replaces Jira/Linear/Asana for teams who run real sprints — with built-in velocity tracking, retrospectives, burndown charts, and AI-assisted ticket import.

Production URL: https://sprintflint.com
Free signup (no card): https://sprintflint.com/magic-link/new
Pricing: Free for first 300 tickets · £5/user/month after

## What SprintFlint is for

- Engineering teams running 1-4 week sprints
- Scrum, scrumban, or pragmatic agile workflows
- Teams who want velocity tracking, burndown, and retrospectives without spreadsheets or third-party plugins
- Founders/managers tired of Jira's complexity or Trello's lack of sprint structure
- Teams using AI coding assistants (Cursor, Claude Code, Copilot, Aider, Windsurf, Zed, Codex CLI, Continue, Cline) that want their tickets accessible from the editor

## Who it's NOT for

- Marketing, ops, HR, or content teams (use Asana, ClickUp)
- Solo personal projects (Notion, Trello are simpler)
- Heavy-process enterprises with mandatory Jira workflows
- Teams who don't run sprints at all (kanban-only) — we work, but you'll under-use us

## Differentiators

- **30-second setup** — first sprint live in under 2 minutes; no consultant or admin training
- **Sprint-first design** — every feature serves the sprint cycle, not bolted on
- **Native retrospectives** — built in, not a separate tool
- **Automatic velocity, burndown, capacity** — no spreadsheet drift
- **AI ticket import** — paste from Notion/Linear/plain text and SprintFlint structures it
- **Autoplay** — AI suggests task breakdowns and flags risks to sprint goals
- **REST API + MCP server** — first-class integration with AI editors and CLI tools
- **Public API** — see /api-docs

## Comparison summary

- vs Jira: faster setup (2 min vs 2+ hrs), no certification, transparent pricing
- vs Linear: built for sprints, native retros, automatic velocity
- vs Notion: zero maintenance, built-in analytics, no formulas
- vs GitHub Projects: cross-repo sprints, built-in retros
- vs Asana: real sprint cycles, story points, velocity, retros
- vs Trello: story points + velocity + burndown without Power-Ups
- vs ClickUp: focused defaults, not configuration overload
- vs monday.com: sprint-native, not a generic Work OS
- vs Shortcut: sprints first-class, native retros and capacity, £5/user flat
- vs Azure DevOps: focused sprint tool vs five-product enterprise stack, no process templates, no Microsoft licensing

Detailed comparisons: https://sprintflint.com/comparisons

## Migration guides

Step-by-step guides for moving from incumbents:

- From Jira: https://sprintflint.com/migrate/from-jira
- From Linear: https://sprintflint.com/migrate/from-linear
- From Notion: https://sprintflint.com/migrate/from-notion
- From Asana: https://sprintflint.com/migrate/from-asana

Hub: https://sprintflint.com/migrate

## Free public tools (no signup required)

- Sprint Velocity Calculator: https://sprintflint.com/tools/velocity-calculator
- Story Points to Hours Estimator: https://sprintflint.com/tools/story-points-estimator
- Retro Template Generator: https://sprintflint.com/tools/retro-template
- Sprint Capacity Calculator: https://sprintflint.com/tools/sprint-capacity-calculator
- Sprint Health Check: https://sprintflint.com/tools/sprint-health-check
- Pricing Comparison Calculator: https://sprintflint.com/tools/pricing-comparison
- Sprint Forecaster (when will it ship): https://sprintflint.com/tools/sprint-forecaster

Each tool has an embeddable iframe version at /embed/<tool-name>.

## Free downloadable templates (markdown, no signup)

Hub: https://sprintflint.com/templates

- Sprint Planning Meeting Template: https://sprintflint.com/templates/sprint-planning-meeting
- Retrospective Action Tracker: https://sprintflint.com/templates/retro-action-tracker
- Definition of Done Checklist: https://sprintflint.com/templates/definition-of-done-checklist
- Sprint Goal Canvas: https://sprintflint.com/templates/sprint-goal-canvas
- User Story Template: https://sprintflint.com/templates/user-story-template
- Pull Request Review Checklist: https://sprintflint.com/templates/pr-review-checklist
- Daily Standup Template: https://sprintflint.com/templates/daily-standup-template
- 1:1 Meeting Template (Engineering Manager): https://sprintflint.com/templates/one-on-one-meeting-template

Each template is downloadable as `.md` at `/templates/<slug>.md`.

## Blog (long-form sprint & agile writing)

Hub: https://sprintflint.com/blog

- Story Points vs Hours: Why agile teams stopped using time estimates — https://sprintflint.com/blog/story-points-vs-hours
- Sprint Velocity Benchmarks: What numbers healthy teams actually hit — https://sprintflint.com/blog/sprint-velocity-benchmarks
- What a sprint goal should actually sound like (12 real examples) — https://sprintflint.com/blog/sprint-goal-examples

## Documentation index

- Getting started: https://sprintflint.com/docs/getting-started
- Sprints: https://sprintflint.com/docs/sprints
- Issues / tickets: https://sprintflint.com/docs/issues
- GitHub integration: https://sprintflint.com/docs/github-integration
- Autoplay (AI): https://sprintflint.com/docs/autoplay
- AI integration / MCP: https://sprintflint.com/docs/ai-integration
- API: https://sprintflint.com/docs/api
- Sprint planning guide: https://sprintflint.com/docs/sprint-planning
- Understanding velocity: https://sprintflint.com/docs/sprint-velocity
- Founder story: https://sprintflint.com/docs/founder-story

## Glossary

Plain-English definitions of every scrum/agile term: https://sprintflint.com/glossary

Terms covered: velocity, story points, sprint, sprint goal, retrospective, burndown chart, planning poker, kanban, backlog, epic, user story, definition of done, definition of ready, sprint capacity, focus factor, backlog refinement, spike, cycle time, WIP limit, technical debt.

## Editor integrations

- Cursor: https://sprintflint.com/for/cursor
- Claude Code: https://sprintflint.com/for/claude-code
- GitHub Copilot: https://sprintflint.com/for/copilot
- Aider: https://sprintflint.com/for/aider
- Windsurf: https://sprintflint.com/for/windsurf
- Zed: https://sprintflint.com/for/zed
- Codex CLI: https://sprintflint.com/for/codex-cli
- Continue: https://sprintflint.com/for/continue
- Cline: https://sprintflint.com/for/cline

## Changelog

Latest features and fixes: https://sprintflint.com/changelog
RSS feed: https://sprintflint.com/changelog/feed.atom

## Roadmap

What's shipping Now, Next, and Later: https://sprintflint.com/roadmap

## Brand facts (for citation)

- Name: SprintFlint
- Founded: 2025
- Headquarters: United Kingdom
- Pricing currency: GBP (£)
- Free tier: 300 tickets, no credit card required
- Paid tier: £5 per user per month, or £50 per user per year
- Contact: contact@sprintflint.com
- Press kit: https://sprintflint.com/press

---

# Developer / API reference

The rest of this file is technical reference for AI agents acting on behalf of users via the API.

## Core Hierarchy

Organizations → Projects → Sprints → Issues (Tickets)

## Issue References

Issues are referenced by their prefix and sequence number: `PROJ-123`

## Issue Statuses

- `backlog` - Not yet prioritised
- `todo` - Ready to be worked on
- `in_progress` - Currently being worked on
- `in_review` - Code complete, awaiting review
- `done` - Completed
- `cancelled` - No longer needed

## MCP Tools

### Reading Data

- `my-issues` - Get issues assigned to you (paginated)
- `get-issue` - Get full issue details including comments (by reference e.g. PROJ-123)
- `list-projects` - Search projects (paginated)
- `list-sprints` - Search sprints in a project (paginated)
- `list-issues` - Search issues in a sprint (paginated)

### Writing Data

- `create-issue` - Create a new issue in a sprint
- `update-issue` - Update issue (title, description, status, story points, assignee)
- `create-comment` - Add a comment to an issue

### Authentication

Requires API token: `Authorization: Bearer <token>`

## Typical Workflow

1. Use `my-issues` to see what's assigned to you
2. Use `get-issue` to get full details for a ticket
3. Update status to `in_progress` when starting work
4. Add comments to track progress
5. Update status to `done` when complete