gaia-action-items

Action item triage before sprint planning works by loading your action-items.yaml tracker, applying escalation rules for aging items, grouping open items by priority, and routing each item by type to the designated owner.

Escalating aging backlog items during sprint prep involves applying automated escalation rules to your open action items, which groups them by priority and flags aging entries to ensure nothing slips into the next sprint unnoticed.

Routing action items by type during backlog grooming assigns clarification items to an assignee agent, implementation and automation items to the Scrum Master, and process items to a user, ensuring every entry has clear ownership.

Yes, you can create stories from resolved action items through a controlled handoff that enforces a classification gate, ensuring only properly categorized implementation and automation items are passed to the Scrum Master for story creation.

Recording reasoning when resolving open action items avoids silent closures and provides explicit rationale for every decision, maintaining a clear historical log within the action-items.yaml tracker for future backlog reference.

Yes, the triage workflow requires an action-items.yaml tracker to load and process open entries, applying priority grouping and type-based routing to prepare items for sprint planning.