Sprint Brief Skill

Produce a clear, scannable sprint brief that every team member — engineer, designer, PM — can read in under three minutes and understand exactly what we're doing and why.

Required Inputs

Ask the user for these if not provided:

• Sprint name and number
• Sprint goal (1-2 sentences — flag if too vague)
• Ticket list with owners (or a description of the work)
• Known dependencies or blockers
• Carry-over items from previous sprint (if any)