aped-course

To change product scope mid-sprint without breaking parallel worktrees, you need a managed course correction that validates pipeline state, updates upstream artifacts like PRDs and epics, and detects stale locks before applying changes.

A course correction pivot in a parallel sprint pipeline is a controlled scope change mechanism that validates state integrity, updates PRDs, epics, and stories, and forces explicit user confirmation before destructive effects occur.

Updating PRD and epics when requirements change mid-stream requires assessing whether the change is a minor feature adjustment or a major architecture pivot, then applying schema-based corrections and invalidating epic context caches.

Reordering priorities in an APED pipeline without losing ticket sync is possible by applying state validation, recording ticket sync context, appending corrections via state schema v2, and safely releasing upstream locks.

Stale scope-change detection matters for pipeline state integrity because it prevents parallel-sprint worktrees from silently drifting by identifying outdated locks and forcing explicit validation before any artifact updates proceed.

Mid-pipeline architecture pivots require state integrity validation and upstream locking rules, meaning they cannot proceed silently and must invalidate epic context caches, record sync logs, and obtain explicit user confirmation before destructive changes.