Some work is too big for one task: a new onboarding flow, a move to a new API, a module with several screens. An epic holds that goal. CodeLynq proposes the tasks it takes, works out which ones depend on which, and - once you have approved them - runs them in that order. Every task still gets its own pull request, so you review the work in pieces you can follow.
Create an epic
- Open the project and go to the Epics tab.
- Click New Epic.
- Enter an Epic title and a Goal. Describe the goal as fully as you can: what should exist when it is done, who uses it, and anything that is out of scope.
- Click Create Epic.
Epics are always created from a project. The Epics page in the sidebar lists the epics of all your projects, with their status and a progress bar (tasks done out of the total).
Let CodeLynq propose the breakdown
Open the epic and click Plan with AI. While the status shows Planning…, the goal is split into tasks. This usually takes 10 to 20 seconds, and the page updates by itself.
When the status changes to Planned, the epic lists the proposed tasks. A task that has to wait for others shows them as after: …. The tasks are ordinary tasks in the project: you can open, edit and refine each of them like any other task.
Approve the tasks
Nothing runs until every task is approved. Open each task from the list and take it through its normal flow: check the technical design (the spec) and approve it. See Technical design and approval.
If a task needs to wait for another one, open it and click Add next to Dependencies to pick the task it depends on.
Run the epic
Click Start. If a task has not been approved yet, the epic does not start and tells you so - approve the remaining tasks and click Start again.
While the epic is Running, CodeLynq starts each task's run as soon as the tasks it depends on are done. The task currently in progress is highlighted. Each run opens its own pull request; review and merge them in your git host as usual.
- Pause stops the epic from starting new tasks. Runs that are already working finish.
- Resume continues where it left off. A paused epic also shows up in your Inbox, with Resume right there.
When every task is done, the epic is Completed: a pull request has been created for each task, in dependency order.
Run tasks in parallel
Under Parallel execution, choose how many tasks may run at the same time: At most plan limit (default), 1 - strictly sequential, or a fixed number. Tasks whose dependencies are met then run side by side, so the epic takes about as long as its longest chain of dependent tasks.
- Your plan's limit on runs at the same time still applies as a ceiling.
- A change takes effect at the next step. Tasks that are running are never interrupted.
- Parallel pull requests can conflict once the first one is merged. With the CI feedback loop turned on, CodeLynq updates the other pull requests to resolve that.
Statuses
Draft (not planned yet), Planning…, Planned, Running, Paused, Completed and Failed.
Delete an epic
Click Delete on an epic that is not running. The epic is removed; the tasks created for it stay in the project.
Good to know
- A project built from scratch also ends in an epic: the build plan becomes an epic whose tasks you approve in the same way.
- Tasks in an epic follow the same rules as any other run, including spend approval and your plan's limits.