codexkit-backlog-refiner

To write INVEST-compliant user stories for backlog refinement, transform raw items by applying the INVEST criteria, generating acceptance criteria in Given/When/Then format, and providing story point estimates with rationale. This clarifies items and prepares them for sprint estimation.

Decomposing epics into sprint-ready user stories involves breaking down large items into smaller, actionable units that meet INVEST criteria. This process surfaces dependencies and flags oversized items for splitting, ensuring each story is manageable for the upcoming sprint.

Formatting acceptance criteria using Given When Then for user stories involves structuring conditions into a clear scenario format. This skill automatically produces Given/When/Then acceptance criteria to define test conditions explicitly and verify story completeness.

Yes, you can estimate story points and flag dependencies during pre-sprint planning. Feeding raw backlog items and goals into this skill yields story point estimates with rationale and explicitly surfaces dependencies or risks to streamline your sprint planning.

You should split oversized backlog items before sprint estimation because large items complicate effort estimation and sprint execution. This skill flags oversized items for splitting and refines them into smaller, sprint-ready stories that adhere to INVEST principles.

Backlog grooming works for clarifying raw items before estimating effort by transforming them into structured user stories. Applying INVEST criteria during grooming clarifies the scope and prepares the items with reliable story point estimates for upcoming sprints.