---
title: "Coordinate a Multi-PR Epic | Agent Barn"
canonical: "https://agentbarn.dev/guides/multi-pr-epic-delivery"
pubDate: "2026-08-25T00:00:00.000Z"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Keep cross-ticket delivery state accurate without replacing feature docs, ADRs, or the issue tracker."
tags: [Engineering guide, Epic owners and reviewers, Agent Barn]
categories: [Guides]
---

# Coordinate a Multi-PR Epic

An epic changelog records what has landed, temporary transition state, the next safe slice, and blockers. It is a coordination artifact, not the source of current product invariants or backlog ownership.

## Guide details

- Reference: GD-17
- Type: Engineering guide
- Audience: Epic owners and reviewers

## Create the coordination artifact

Before the first implementation PR, add `docs/features/<epic-slug>/CHANGELOG.md` with status, epic link, related context, current state, and newest-first changes. Every PR in the epic updates it.

## Record observed state

Delivered describes behavior already safe to depend on. In transition names temporary compatibility or migration state. Next and Blockers describe what is actually unblocked or constrained. Link tickets and PRs rather than copying full requirements.

## Preserve authoritative boundaries

Feature and architecture docs own current behavior. ADRs own consequential rationale. The issue tracker owns acceptance criteria, ownership, and backlog state. A changelog cannot substitute for updates to those sources when a contract changes.

## Close cleanly

Mark the epic completed, move durable facts into authoritative docs, resolve remaining work in the issue tracker, and retain the changelog only when its migration or compatibility history remains useful.