User Story Refinement Agent

When stories are unclear, the team builds the wrong thing or stops mid-sprint to ask questions. Before each refinement session, this agent pulls the queued stories, linked designs and the team's definition of ready. It checks each story for a clear user and value, testable acceptance criteria, named dependencies and a size that fits one sprint. It drafts missing acceptance criteria from the story's intent and lists vague phrases as questions for the product owner. When a story is too large, it proposes a split into smaller stories that each deliver value. It then checks that every blocking dependency has an owner, and if one is missing it adds a question and checks again. It never marks a story ready on its own; the product owner approves each refined story. Edge case: a story that hides two different user needs is flagged for splitting by need, not just by size.