Notre avis

Assistant de planification de sprint qui guide l'estimation de la capacité de l'équipe, la sélection des stories du backlog, la cartographie des dépendances et l'identification des risques, puis produit un résumé structuré du plan de sprint.

Points forts

Approche structurée étape par étape couvrant capacité, dépendances et risques.
Produit un objectif de sprint concret et un résumé clair.
Appuie les décisions sur la vélocité historique et un tampon de capacité.
Met en évidence le chemin critique et la concentration des connaissances.

Limites

Dépend fortement des données fournies par l'utilisateur ; sans elles, les hypothèses sont génériques.
Ne s'intègre pas aux outils de gestion de projet comme Jira ou Trello.
La qualité du plan dépend de la qualité du backlog et des informations de disponibilité.

Quand l'utiliser

Lors de la préparation d'une cérémonie de planification de sprint pour construire un backlog réaliste et conscient des risques à partir des données d'équipe et du backlog existant.

Quand l'éviter

Quand vous devez réellement mettre à jour des tickets dans un outil de gestion, ou quand aucun backlog ni donnée de disponibilité n'est disponible pour fonder le plan.

Analyse de sécurité

Sûr

Score qualité88/100

The skill only describes a sprint planning process and does not instruct any execution of commands, file modification, network access, or handling of sensitive data. The only file interaction suggested is reading user-provided backlog or velocity files, which is benign.

Aucun point d'attention détecté

Exemples

Plan sprint from backlog CSV

Plan the next 2-week sprint for our team of 5 developers using the attached backlog.csv and our velocity data from the last 3 sprints. Provide capacity, story selection, dependencies, and risks.

Capacity with PTO

Help me prepare for sprint planning: estimate our team capacity given two teammates are on PTO next week and our average velocity is 30 story points. Reserve a 15% buffer.

Create sprint plan from Jira export

Create a sprint plan from this Jira backlog export: select stories for the upcoming sprint, map dependencies, identify risks, and propose a sprint goal.

name: sprint-plan description: "Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity."

Sprint Planning

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Context

You are helping plan a sprint for $ARGUMENTS.

If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

Instructions

Estimate team capacity:
- Number of team members and their availability (PTO, meetings, on-call)
- Historical velocity (average story points per sprint from last 3 sprints)
- Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
- Calculate available capacity in story points or ideal hours
Review and select stories:
- Pull from the prioritized backlog (highest priority first)
- Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
- Flag stories that need refinement before committing
- Stop adding stories when capacity is reached
Map dependencies:
- Identify stories that depend on other stories or external teams
- Sequence dependent stories appropriately
- Flag external dependencies and owners
- Identify the critical path
Identify risks and mitigations:
- Stories with high uncertainty or complexity
- External dependencies that could slip
- Knowledge concentration (only one person can do it)
- Suggest mitigations for each risk

Create the sprint plan summary:

Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]

Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...

Risks:
- [Risk] → [Mitigation]