Create your account
Sign up with email and password, or continue with Google. Takes about ten seconds.
Go to the login page
Navigate to /login or click Sign in from the landing page.
Choose your auth method
Enter your email and password to create a new account, or click Continue with Google for one-click setup.
Land on the dashboard
After signing in you are redirected to your dashboard. It will be empty — time to create your first project.
Create your first project
A project is the container for all your goals. Give it a name, a slug, and optionally a repo URL.
Click “+ New Project”
On the dashboard, click the + New Project button in the top-right area. A dialog will open.
Fill in the details
Pick a domain (engineering, health, learning, etc.), give your project a name and a slug (URL-friendly identifier). Optionally add a description and repository URL.
/dashboard/my-app. Keep it short and lowercase.Open the board
Your new project appears on the dashboard. Click it to open its board — it will be empty until you generate a plan.
Generate a plan from a prompt
Describe your goal in plain language. An LLM breaks it into phased, structured goals — complete with priorities, estimates, dependencies, and acceptance criteria.
Open the generate dialog
On your project board, click the Generate Plan button. A dialog opens with a large text area.
Describe the outcome
Write one paragraph describing what you want to achieve. Include constraints, deadlines, context — whatever you have. No templates, no required fields.
Example prompt: "Build a REST API for a recipe sharing app. Needs auth, CRUD for recipes, image upload, and a search endpoint. Ship in 3 weeks. Stack: Node.js + PostgreSQL."
Review the generated goals
The LLM creates goals across three phases:
Each goal gets a ticket ID (e.g. RCP-003), type, priority, effort estimate, and acceptance criteria. Goals land on your board ready to work.
Navigate the board
The board is a kanban view of all goals in your project. Goals move through columns as they progress.
Goal statuses
Phase bars at the top
Three colored bars show progress per phase. Click a phase bar to filter the board to that phase only.
Goal cards
Each card shows the ticket ID, title, type, priority, assignee (human or agent), and acceptance-criteria count. Click a card to open the full goal detail view — you can edit fields, update status, and view the acceptance criteria checklist.
Assignees
Goals can be assigned to you (a human) or to an agent. Agent-assigned goals show a blue chip with ▶ agent. You can reassign goals at any time from the goal detail view.
Connect Claude Code
SprintBoard exposes an MCP server that Claude Code connects to over HTTP. No extra installs needed.
Generate your API key
Go to Dashboard → Connect MCP. Click Generate API Key to create a personal key scoped to your account.
Add to Claude Code settings
Add the MCP server config to your .claude/settings.json (per-project) or ~/.claude/settings.json (global):
{
"mcpServers": {
"sprintboard": {
"type": "url",
"url": "https://your-sprintboard-url/api/mcp",
"headers": {
"x-agent-key": "your-api-key"
}
}
}
}Verify the connection
Open Claude Code and ask: “List my SprintBoard projects.” If you see your projects, you are connected.
Agent workflow
Once Claude Code is connected, agents can pick up goals, execute them, and submit for review — all from the CLI.
Create goals via MCP
Describe your goal to Claude Code. It uses the create_tasks MCP tool to generate and upload a phased plan directly to your board.
# In Claude Code: "Create a task plan for building user authentication with JWT tokens"
Pick up and start a goal
The agent calls get_next_task to fetch the highest-priority assigned goal, then start_task to mark it as in progress.
# Agent flow: get_next_task → returns task details start_task → status becomes in_progress
Complete or fail
After making changes, the agent calls complete_task with the commit SHA. If something goes wrong, fail_task reverts the goal to assigned so it can be retried.
complete_task → status becomes in_review fail_task → status reverts to assigned
Available MCP tools
list_projectsList all your projectscreate_projectCreate a new projectcreate_tasksBulk create or upsert goalslist_tasksList goals with status / priority filtersget_taskGet goal details by ticket ID or UUIDget_next_taskFetch the next assigned goal by prioritystart_taskMark a goal as in progresscomplete_taskMark a goal as done with commit infofail_taskReport failure, revert to assignedsubmit_reviewSubmit a code review with approval or rejectionReview & re-plan
When an agent completes a goal, it moves to review. You approve, reject, or re-plan the remaining work.
Review completed goals
Goals that agents complete move to the In Review column. Open the goal detail to see the changes, commit info, and acceptance criteria. Approve to move it to Done, or reject to send it back.
Re-plan at any time
Click Re-planon the board header to regenerate the remaining goals. Goals that are already done stay untouched — only open goals get re-phased against the current state of the project.
Import goals manually
Use the Import Goals dialog to paste goals as JSON if you already have a structured plan from another tool or an LLM conversation.
Keyboard shortcuts
SprintBoard is keyboard-first. These shortcuts work from any board view.