story-breakdown

Breaking down large stories into actionable work items involves decomposing multi-component epics into discrete tasks queued in .agent/queue/ with defined statuses, priorities, assignees, and dependencies to enable staged execution.

Managing cross-functional dependencies requires creating work items with explicit BlockedBy and Blocks fields, allowing specialists to coordinate staged execution based on task priority and dependency status.

Queueing work items in .agent/queue/ creates structured entries containing Title, Status, Priority, Assignee, Blocks, BlockedBy, Description, and Success Criteria fields to track and coordinate execution across specialists.

Story breakdown is designed specifically for multi-component epics, decomposing scope into discrete work items tagged with responsible roles and dependencies to enable cross-functional collaboration and staged execution.

Work items created for cross-functional project management include Title, Status, Priority, Assignee, Blocks, BlockedBy, Description, and Success Criteria fields to support dependency tracking and coordinated execution.

Decomposing stories into queued work items is necessary when large epics span multiple components requiring coordination across specialists, explicit dependency management, and staged execution through a structured queue.