backlog-workflow

Backlog planning across multiple sessions is coordinated by maintaining context through notes, assignees, and dependency tracking to synchronize contributors. You create parent epics to group related work and decompose them into tasks with explicit owner assignments for traceable handoffs.

To avoid duplicate tasks in backlog management, apply a search-first protocol that mandates searching for existing tasks before creating new ones. This standardized approach minimizes redundant work and ensures all team members reference the same tracked items.

Structure epics and sprints by organizing work as single tasks or nested epics to coordinate across sessions and team members. Apply consistent scope assessment criteria to determine task granularity, acceptance criteria, and lifecycle before assigning dependencies and owners.

To ensure backlog tasks are properly closed with traceable handoffs, apply quality checks that verify deliverables, attach references, and enforce closure protocols. This standardizes task lifecycle completion and maintains synchronization across all contributing sessions.

Yes, nested epics support scoping and synchronizing work across both human contributors and automated sessions. You maintain context through dependency tracking, notes, and assignee assignments to coordinate cross-session collaboration effectively.

Assess task scope and granularity during initial backlog planning by applying consistent criteria to determine acceptance criteria and lifecycle. This ensures proper task decomposition before work starts and enables routine cross-session status reviews.