Sprints without the spreadsheet
Break features down, mark what's blocked, estimate and track time, and see pull requests on the task they close. Your coding assistant can read and update the same board.
Dependencies
Blocked-by links show what's waiting on what.
Estimates and timers
Track time against an estimate without a separate tool.
GitHub pull requests
Mention TSK-12 in a PR and it shows on the task.
MCP and REST API
Claude Code, Cursor, and your scripts work from the same tasks.
The challenge
Standups ran long because nobody could see what was blocked, estimates lived in a spreadsheet that drifted from the board, and nobody could tell which pull request closed which ticket without asking.
Plan the sprint on the board
Start from the Development sprint template (Backlog, To do, In progress, In review, Done) with Frontend, Backend, Bug, and Chore labels. Every task gets a key like TSK-128, so it can be referenced in commits, pull requests, and chat.
- Subtasks for each piece of a feature, each with its own owner.
- Blocked-by links: open a task to see what it's waiting on and what it's holding up.
- A task limit on In progress turns the count red when the team takes on too much.
- Table view shows assignees, priority, due dates, tracked time against estimates, and custom fields such as story points.
Pull requests on the task
Add Taskeni's webhook to a repository and mention a task key in a pull request's title, branch, or description. The pull request shows on that task with its state. Turn on Mark tasks done when a linked PR merges and merged work moves to the completion list by itself.
Your coding assistant, on the same board
Connect Claude Code or Cursor to Taskeni's MCP server and ask it to read the task it's working on, tick off checklist items, or file the follow-up bugs it found. It acts as you, sees only what you can see, and can't delete anything. For scripts and CI, use the REST API with a personal token, or subscribe to signed webhooks.
Keyboard first
Press ? for the shortcut sheet and ⌘K for the command palette. Select several tasks with X or ⇧-click and move, assign, label, or reschedule them in one go. ⌘Z undoes it.
How the workflow runs
- 1
Break work down
Each feature gets subtasks and blocked-by links, so waiting work is written down before standup.
- 2
Estimate and track
Engineers log time against an estimate with the built-in timer. Table view shows tracked against estimated.
- 3
Cap work in progress
A task limit on In progress turns the count red when the team takes on too much.
- 4
Link pull requests
Branch names like tsk-128-fix-login link the PR to the task; merging can close it.
- 5
Let the assistant help
Claude Code or Cursor reads the task over MCP and files follow-up bugs on the board.
- 6
Review the sprint
Home's This week review shows what was done, what slipped, and what's due next; reports add cycle time (Pro).
Common questions
Does Taskeni integrate with GitHub?
Yes. A repository webhook links pull requests to tasks whose key (like TSK-12) appears in the PR's title, branch, or description, and can mark tasks done when the PR merges. See integrations.
Can I use Claude Code or Cursor with Taskeni?
Yes. Add Taskeni's MCP server with claude mcp add --transport http taskeni <server URL> or in .cursor/mcp.json. Setup steps are in Settings → API & AI agents. See MCP.
Does Taskeni support story points?
There's no built-in story point field, but you can add a number custom field to any board and see it in Table view. Time estimates are built in.
Is there a GitLab or Bitbucket integration?
Not yet. The REST API and webhooks work with any tool that can make HTTP requests.
Is it free for a small engineering team?
Yes. The Free plan covers up to 10 members with subtasks, dependencies, time tracking, GitHub, the MCP server, the REST API, and webhooks. Automations and reports are on Pro and Business. See pricing.