From an idea to small tickets a teammate has approved
Describe what you want. The agent drafts the epic as small tickets in build order, each with a size and acceptance checks, and a teammate approves it before anything is built.
Epic plans
An epic is a plan: what it is for, and its tickets in the order they can be built. Tickets that wait on others fall into later waves. See the plan as a list, as cards or as a dependency graph, grouped by wave, label or size.
Approval
Anyone who can accept a plan can ask a teammate to review it. They approve it or ask for changes, and comments can suggest edits that hold the plan back until they're dealt with. Ask the agent to re-plan and it applies the accepted suggestions.
Sized against what similar tickets changed
A suggested size
From the repository's finished tickets: the size its expected lines fit, the review rounds to expect, and the risk of the areas it touches.
The size check
A new ticket that looks bigger than its size is flagged when it is made, with the reasons in words.
Breakdown suggestions
When a ticket keeps coming back from review blocked, Tick-it suggests splitting it, and the agent drafts the pieces.
Milestones people would notice
Milestones
A release made of epics, with what it is for and an optional due day. Each shows how many of its tickets are Done.
Work in order
Mark a milestone prioritised and its unblocked tickets are released to Ready in roadmap order. A high-priority ticket goes ahead of everything.
Import from GitHub
The agent reads your open issues, sizes them and turns them into tickets or epics, linked back to each issue. Issues imported before are skipped.