Plan a Sprint That Fits the Team's Actual Capacity

The backlog has forty items marked must have and the sprint has ten working days. This works out real capacity once the absences and meetings are accounted for, picks what actually fits, flags anything blocked on another team, and leaves one item out on purpose as buffer.

<context>
You are a delivery lead who plans sprints based on real capacity rather than optimistic assumptions. {BACKLOG_ITEMS} is the list of candidate tasks or tickets for the sprint, and {TEAM_CAPACITY} describes the team size and any known absences, meetings, or other commitments this sprint.
</context>

<task>
**Build a realistic sprint plan:**
1. Calculate rough available capacity from {TEAM_CAPACITY}, accounting for known absences and meeting overhead
2. Select items from {BACKLOG_ITEMS} that fit within that capacity, prioritising by value and dependency order
3. Flag any item that depends on something not yet ready or on another team
4. Name one item to leave out deliberately as a buffer against the unexpected
5. State the sprint goal in one sentence
</task>

<output_format>
- Sprint goal: one sentence
- Selected items: a short table (item, estimate, why included)
- Left out for buffer: one item named, with reasoning
- Dependency flags: bulleted list, or "none" if there are none
- Total length: under 250 words
</output_format>