Tasks

A board that knows why each task exists.

Every task carries its type, area, release, and the feedback that asked for it. When you pick what to build next, the evidence is already there.

Used by developers at

Sky Enterprise Filmatic Rollcall MyPacks Volvox NextGame Switchboard
What a task holds

Enough structure to plan with.

A task is one piece of committed work: what kind of work it is, which part of the product it touches, which release it ships in, and who asked for it.

01

Kanban board

To Do, In Progress, Done. Drag and drop, filter by feature, bug, or the active release, and it syncs live if a teammate is on the board too.

02

Typed and placed

Every task is a feature, bug, or improvement, with a priority and an area for the part of your product it belongs to.

03

Evidence attached

Tasks accepted from signals keep the link: who asked, what they said, and how many people voted for it.

04

GitHub linked

Connect the GitHub App and commits, pull requests, and issues attach to the task, with assignees synced both ways.

05

CSV in and out

Import an existing backlog with a review step before anything commits, and export your tasks any time. No lock-in either direction.

06

Bring the team

Share one invite link and people join the project, see the board live, and get assigned work. Every change lands in the activity trail.


How it works

From accepted idea to shipped work.

The backlog holds possible work. A release holds committed work. Tasks are how things move between them without losing their reason.

01

Work enters with a reason.

Create a task yourself, accept it from a signal, or let your coding agent file it over MCP. It lands typed and traceable either way.

02

Shape it.

Set the type, area, and priority, break it into subtasks, and assign it if you're not working alone.

03

Commit it to a release.

New tasks default to the active release, so planning is one decision. Everything else waits in the backlog.

04

Ship it and it shows.

Done tasks move the release forward, and anything on your public roadmap flips to shipped for the people who asked.


FAQ

Common questions about Tasks.

Which plans include the task board?
Every plan, including Free. Free covers one project and 100 active tasks, enough to run a real product. Paid plans lift the caps.
What's the difference between a task and a signal?
A signal is an input waiting for a decision: feedback, a bug report, an idea. A task is work you've committed to. Signals become tasks only when you decide they deserve building.
Can my coding agent work the board?
Yes. Over MCP, Claude Code, Codex, or Cursor reads the task and the feedback behind it, updates status as it works, and files new tasks it discovers. MCP is Indie and above.
How does the GitHub integration work?
Install the Frostbyte GitHub App and reference a task from a branch or PR. The commits, pull requests, and issues show up on the task, and assignees stay in sync. Indie and above.

Plan the work

Give your backlog a reason to exist.

No credit card. Free stays free.
Import your backlog or start clean in minutes.