name: sprint-planner
description: Facilitate sprint planning, estimation, sprint goals, and sprint review using your backlog.

Sprint Planner Skill

An agile planning skill that helps you select backlog items, define sprint goals, estimate work, and review progress.

When to use this skill

Use this skill when you say things like:
- “Plan the next sprint from this backlog.”
- “Estimate these stories.”
- “Draft a sprint goal for these items.”
- “Review how the current sprint is going.”

Inputs this skill uses

Provide:
- Backlog context: Asana project / board, CSV export, or pasted list of candidate stories.
- Capacity signals: team size, holidays, planned time off, historical velocity (if you know it).
- Constraints: fixed dates, must-ship items, cross-team dependencies.

Core behaviors

A. Start Sprint Planning (SP)

• Clarify:
• Sprint length and dates.
• Team members and any time off.
• Historical velocity or a rough capacity guess.
• Check "Definition of Ready" for candidates (clear owner, ACs, design ready, dependencies known).
• Propose a draft sprint scope:
• Select items that fit capacity and align with current goals.
• Flag risky / unclear items for later.
• Output:
• Short sprint goal options (1–3 candidates).
• List of planned items with rough effort and owner.

B. Estimate Backlog Items (EB)

• Help break down large stories into smaller tasks when needed.
• Suggest an estimation scheme:
• Story points (e.g., Fibonacci) or hours.
• For each item:
• Ask for complexity, uncertainty, and dependencies.
• Suggest an estimate and let you adjust.
• Summarize:
• Total estimated effort.
• Distribution by assignee / area.

C. Create Sprint Goal (CG)

• Given a set of candidate items (from Asana, CSV, or your list):
• Identify the dominant theme(s): outcome, user segment, metric.
• Draft 1–3 concise sprint goals that are:
  • Clear, measurable, and achievable in one sprint.
  • Framed as outcomes, not activity lists.
• Let you refine wording and pick the final goal.

D. Review Sprint Status (RS)

• For an in-flight sprint:
• Summarize completed vs in-progress vs not-started work.
• Highlight blocked items and at-risk goals.
• Compare planned vs actual so far.
• Suggest adjustments:
• De-scope, swap items, or adjust expectations.

Output format

• Always return:
• Short summary: one or two sentences.
• Bullet list or table for items and estimates.
• Clear next-step suggestions (e.g., “Move these 2 stories to next sprint”, “Confirm this sprint goal wording”).** End Patch```} /}