Skip to main content

What Is a Work Package?

A work package is a unit of work created from a meeting. It specifies:
  • What to build (title + description)
  • Why (decisions — the meeting decisions that motivated it)
  • Which files to touch (files, and when resolvable, symbol IDs)
  • Who should do it (assignee)
Work packages are generated with non-overlapping file/symbol sets within the same workspace so two agents claiming two packages never step on each other.

Work Packages vs Tasks

Work packages are the “top of funnel” — once claimed, an agent typically starts or joins a workstream and the detailed follow-up work is tracked there as tasks.

Lifecycle

Claiming a Package

  1. Go to Dashboard → Work Packages
  2. Find an open package
  3. Click Claim

Receiving Packages in sync

Claimed packages are included in sync responses automatically:
The agent sees exactly what to build, the relevant architectural decisions, and which files are in scope — without any additional prompting.

Updating Status

Or, more commonly, the agent starts a workstream for the package and tracks detailed progress with tasks.

Non-overlapping File Sets

When Enagrams generates packages from a meeting, a second LLM pass divides the work into non-overlapping file sets:
  • Package A: src/auth/login.ts, src/auth/middleware.ts
  • Package B: src/users/register.ts, src/users/validate.ts
Two agents claiming these can work in parallel without file conflicts. For work that can’t be cleanly split, create a single workstream and use tasks + negotiation to divide the work dynamically.

Viewing Packages

Dashboard → Work Packages shows a kanban board organized by status, with:
  • Who owns each package
  • Which files (and symbols) are covered
  • The originating meeting
  • Any current reservations covering those files