Plan

A board your agents can read too.

Your team and your coding agents work from the same tickets, epics, cycles and releases. Write each ticket the way you’d brief a colleague. Say what’s broken and how you’ll know it’s fixed.

The board

One board, sliced however you need.

Columns run from backlog to done, and saved views answer the questions you ask most.

  1. A view for each questionNeeds you, Running now, Stuck, Ready to ship, This cycle, Unowned, Blocked and Shipped this week come built in. Save your own next to them.
  2. Sub-ticketsBreak a big ticket into smaller ones, and its card shows how many are done.
Triage

Requests land in one place.

People ask from wherever they already are. It all waits in Triage until someone sorts it.

  1. From wherever people askEmail, Slack, Discord, Microsoft Teams, a public request form, or feedback sent from inside your app.
  2. Including what your agents findWhen an agent trips over a problem outside its ticket, it files a report, and the report lands in Triage with everything else.
Epics, milestones, cycles

Plan further ahead than tonight.

Group the work and put dates on it, then watch how far along it gets.

  1. Epics and milestonesAn epic holds the tickets for one piece of work. Milestones mark the stops along the way, and each one shows how far it’s got.
  2. Cycles, with a plannerPlan what goes into each cycle and see what’s left as it runs.
  3. Releases with readiness checksBefore it ships, a release checks for open tickets and pull requests, failing CI, migrations, release notes, the runbook and tests.
Bring your backlog

Keep the tracker you have, or move in.

Sync with Linear or Jira both ways, pull from them only, or import once. GitHub Issues and Asana can be imported too.

  1. Sync or importKeep Linear or Jira in step with By Dawn, or import once and move over. A sync can also stop on a date you set.
How it works

How a ticket moves

  1. It landsIn Triage, from email, chat, a form, your app or an agent.
  2. It’s plannedIt goes into an epic and a cycle, with a brief that says what done looks like.
  3. It’s builtMove it into Building and an agent picks it up as a mission.
  4. It shipsAs a pull request with its proof, then in a release.
Questions

Asked about planning.

Can my team keep using Linear or Jira?

Yes. Sync both ways, pull only, or import once. GitHub Issues and Asana import too.

Do agents see the whole board?

An agent works one ticket at a time, as a mission, with the docs and memory that ticket needs.

Next · PlanLark →The board agent. Ask it about the work, or have it draft changes for you to apply.
The waitlist

Plan it tonight. Ship it by dawn.

Free to join. One email to confirm, then only news about your place. What we keep

Proudly built in

Tampa, Florida.