Release-first planning for small dev teams: scope the version, track the work, and keep feedback tied to what ships.
Start with the release, patch, or milestone you want to ship. Set the target, keep the active release visible, and let every task point back to a clear plan.
GitHub PR linking, PDF export, and team collaboration features.
Signup, projects, task board, releases, areas, and real-time updates.
Move work through To Do, In Progress, and Done, then filter by release, area, type, or assignee when the board gets busy.
Auto-link commits and PRs to tasks using FB-123 references. Show status badges on task cards.
Add header/footer options, custom branding, and better table layouts for exported reports.
Fix card preview offset when dragging on boards with horizontal scroll.
Push updates via WebSocket so team members see changes instantly without refresh.
Add burndown and velocity graphs to the release detail view.
Kanban columns for To Do, In Progress, and Done with smooth reordering.
Create releases with targets, define areas, and assign tasks to both.
Invite members via email, assign roles, and control project access.
Create areas like Auth, API, Billing, or Frontend, then see how each part of the product is tracking inside a release. You can also use areas for business work like Marketing, Support, or Launch when a release needs more than code.
Endpoints, webhooks, background jobs, and third-party integrations.
Subscriptions, usage limits, invoicing, and payments.
Reference tasks in your commits, see PRs in task details, close tasks when you merge.
Use #123 in commit messages to link tasks
PRs show up in task details with status
Use Fixes #123 to close tasks when PR merges
The Frostbyte MCP server is hosted — no downloads, no local processes. Connect Claude, Cursor, or any MCP-compatible agent with a URL and an API token, so agents can read and update project data. Ask them to triage tasks, summarise a release, or create a bug without leaving your editor.
Invite your team, assign work, and see project activity as it happens. Everyone can tell what changed, who changed it, and what still needs attention.
Users can report bugs, suggest features, or leave general feedback without seeing your private backlog. Review each submission, accept the useful ones, and send them to the active release or backlog.
Something isn't working as expected
Share ideas for improvements
General comments or suggestions
Flag tasks as public and share a live roadmap. Users see progress as it happens, so they stop asking "when is X coming?"
Get notifications in Slack when tasks move or comments are added.
Publish a clear summary of what changed when a release goes live.
Weekly summary of project activity sent to your inbox.
Auto-link pull requests to tasks using FB-123 references in commits.
Better contrast and reduced eye strain for late-night coding sessions.
Invite team members, assign tasks, and work together in real-time.
Group tasks into releases with target dates and track progress.
Download your tasks as a spreadsheet for reporting or backup.
Export a release board as a PDF for stakeholder updates, or pull task data as CSV for spreadsheet analysis. Filter by release or export everything.
Visual board layout for presentations and stakeholder updates
Basic plan +Raw task data for spreadsheets and custom analysis
All plansFrostbyte stays focused on planning and shipping software, with the everyday details handled.
From the blog
Guides on shipping features cleanly, scoping releases, and turning feedback into work that actually ships.
The messy middle between raw input and structured execution is where most good ideas die. Here's how to fix that.
Backlogs often become storage. Releases create momentum because they tie work to an actual shipping outcome.
Feedback living in DMs, emails, and Slack threads never gets acted on. Insight only becomes valuable when it's visible and connected to decisions.
Your next release is waiting
No credit card. Free stays free.
Create your first project, add a release, and see whether the workflow fits.