Getting started

Create a project immediately, optionally generate a starter plan with AI, and begin your first focused release.

Set up the minimum structure first. Refine it once real work starts moving through.

1. Create a project

Sign up at getfrostbyte.dev and click New project. Use the product, client, or codebase name your team already uses, short and recognisable.

Choose visibility and the current product stage, then create the project. Frostbyte opens the dashboard immediately. GitHub is optional and can be connected later.

The free tier gives you one project, one collaborator, and 100 active tasks. Enough to validate the workflow before committing to a paid plan.

2. Choose whether to generate a starter plan

On a fresh dashboard, Frostbyte offers an optional AI setup. Add one context reply and generate a starter plan, or skip it and configure the project manually.

The reply is prefilled from your project description. Add useful detail about who the product is for, what already exists, and what you want to build next. Successful generation inserts starter areas, releases, and tasks immediately.

3. Add three to five areas

Areas are the systems you maintain, the things that don't change much release to release. A common starting set:

  • Auth, login, signup, password reset.
  • Billing, Stripe wiring, invoices, subscription state.
  • API, public endpoints and integrations.
  • UI, frontend components and pages.

Add areas inline from a task dropdown, or via the Areas tab. Rename, recolour, or archive them later as the codebase grows.

4. Create your first release

A release is what you're shipping next. Name it concretely: v1.0, MVP, Beta, or a date. Frostbyte offers smart name suggestions based on your previous release (semver, calver, dates, sprint numbers).

Set it as active. Frostbyte enforces a single active release per project, so the team always knows what "now" means.

5. Add tasks

Each task describes one change. Title, type (feature / bug / improvement), area, release, priority, that's it. New tasks default to the active release, so you don't have to set it every time.

Drag-and-drop between status columns (To Do / In Progress / Done) as work moves. Inline-edit titles directly on the board. Subtasks live inside each task as a checklist.

6. Review the scope

After 24 hours of normal work, look at your release. Does it feel achievable? If yes, keep going. If it's bloated, move lower-priority tasks to the next release or to a parking-lot release named "Later".

What's next

Last updated