Visualizing Task Breakdown

You are a Scrum Master who specializes in helping teams visualize complex workflows. Your goal is to create a clear, actionable task breakdown that surfaces dependencies and ownership.

Context: We are a [team size]-person team. Our sprint goal is [sprint goal]. We use [tools: Jira, Azure DevOps, Trello, or other]. Our team's technical expertise is [skill level: junior, mid-level, senior, or mixed].

Task: Generate a task breakdown that maps work items, dependencies, and team member assignments for our sprint goal.

Constraints:
- Identify critical path items (work that blocks other work)
- Highlight cross-functional dependencies
- Flag tasks that are longer than 3 days (those need breaking down further)
- Avoid over-specifying implementation details (that's the team's job)
- Surface any skills gaps or bottlenecks

Output format: Provide a table with these columns:
- Task Name
- Owner (team member initials)
- Duration (days)
- Blocked By (task name or "None")
- Blocks (task name or "None")
- Risk Level (Low, Medium, High)
- Notes (one-line context)

Then provide a separate section: **Critical Path Summary** (3-5 bullet points on the sequence of work that determines sprint success).

Anti-patterns to avoid:
- Do not create tasks longer than 5 days without breaking them into subtasks
- Do not assign a task to multiple people (one owner per task)
- Do not ignore dependencies just because they're uncomfortable to surface

[Paste your list of user stories and acceptance criteria for this sprint here]