velocity

Calculate team velocity from historical sprint data Arguments: <project> [--sprints <count>].

SKILL.md

GitHub

Velocity

Calculate team velocity from completed sprints and show trend analysis.

Arguments

Format: <project> [--sprints <count>]

  • project: Project name or identifier (required)
  • --sprints: Number of past sprints to analyze (default: 5)

Parse from "$ARGUMENTS".

Process

  1. Bootstrap connector — consult the connector-bootstrap skill. Probe ToolSearch for the Plane resource tools referenced below (project, cycle, workitem); their names are mcp__<server>__<resource>, never assume a specific MCP prefix. If multiple Plane instances are connected, ask the user which one to use. All formulas and rules come from the agile-fundamentals skill. Calls are written resource(action=..., ...).

  2. Resolve project:

    project(action=list)
    
  3. Get completed sprints:

    cycle(action=list, project_id, status=completed)
    

    Take last N completed cycles (sorted by end_date descending). Sprints that are already archived: cycle(action=list, project_id, archived=true) (status is ignored then).

  4. Calculate velocity per sprint: For each cycle:

    cycle(action=list_workitems, project_id, cycle_id, pql='stateGroup = "completed"', fields="id,point,estimate_point")
    cycle(action=list_workitems, project_id, cycle_id, fields="id,point,estimate_point")
    

    Sum point of the completed items (first call) and of all items (second call, total planned); if point is empty and the project has an estimate system (project_estimate(action=retrieve, project_id)), sum the value of each item's estimate_point instead (project_estimate(action=list_points, project_id, estimate_id) maps ids to values). Items finished per sprint for all completed cycles in one call: workitem(action=count, project_id, pql='cycle IN completedCycles() AND stateGroup = "completed"', group_by=cycle_id).

  5. Calculate aggregates:

    • Average velocity
    • Min/max range
    • Average completion rate
    • Trend (improving/stable/declining)
  6. Display velocity report:

    | Sprint | Planned | Completed | Rate |
    |--------|---------|-----------|------|
    | Sprint 11 | 40 | 36 | 90% |
    | Sprint 10 | 38 | 32 | 84% |
    | ...
    
    Average velocity: 33 pts/sprint
    Range: 28-36 pts
    Completion rate: 86%
    Trend: Stable
    Recommended next sprint: ~28 pts (velocity × 0.85 buffer)
    

Example Usage

/velocity "TaskFlow"
/velocity "My Project" --sprints 10