agile-sprint-planning

agile-sprint-planning is a skill for Claude Code from nicepkg/ai-workflow. It costs 44 tokens per session (1,838 once invoked), scanned A, original, MIT.

A guide for planning Agile sprints, which are short, time-limited work cycles. It covers sprint goals, user-story estimates, backlog priorities, team capacity, dependencies, and reviews.

In plain words
What is it for?
Use it to prepare sprint-planning checklists, select and estimate stories, account for holidays and absences, manage mid-sprint changes, and prepare reviews and retrospectives.
Why use it?
It gives a team a repeatable way to decide what fits into the next work cycle. This reduces unclear scope, missed dependencies, and poorly prepared planning meetings.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to prepare sprint-planning checklists, select and estimate stories, account for holidays and absences, manage mid-sprint changes, and prepare reviews and retrospectives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nicepkg/ai-workflow/agile-sprint-planning
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nicepkg/ai-workflow --skill agile-sprint-planning
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for agile-sprint-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicepkg/ai-workflow/agile-sprint-planning.svg)](https://agentmods.dev/skills/nicepkg/ai-workflow/agile-sprint-planning)
Your own site
<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/agile-sprint-planning"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/agile-sprint-planning.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01838
Opus 5 $0.00022 $0.00919
Sonnet 5 $0.00009 $0.00368
Haiku 4.5 $0.00004 $0.00184

Measured 4d ago against content hash a04ab486073a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

agile-sprint-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workflows/product-manager-workflow/.claude/skills/agile-sprint-planning/SKILL.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agile Sprint Planning

Overview

Agile sprint planning provides a structured approach to organize work into time-boxed iterations, enabling teams to deliver value incrementally while maintaining flexibility and responding to change.

When to Use

  • Starting a new sprint cycle
  • Defining sprint goals and objectives
  • Estimating user stories and tasks
  • Managing sprint backlog prioritization
  • Handling mid-sprint changes or scope adjustments
  • Preparing sprint reviews and retrospectives
  • Training team members on Agile practices

Instructions

1. Pre-Sprint Planning

# Sprint Planning Checklist

## 1-2 Days Before Planning Meeting
- [ ] Groom product backlog (ensure top items are detailed)
- [ ] Update user story acceptance criteria
- [ ] Identify dependencies and blockers
- [ ] Prepare estimates from previous sprints
- [ ] Review team velocity (average story points per sprint)
- [ ] Identify team availability/absences
- [ ] Prepare sprint goals draft

## Information to Gather
- Product Owner priorities
- Team capacity (working hours available)
- Previous sprint metrics
- Upcoming holidays or interruptions
- Technical debt items to address

2. Sprint Planning Meeting Structure

// Example sprint planning agenda and execution

class SprintPlanner {
  constructor(team, sprintLength = 2) {
    this.team = team;
    this.sprintLength = sprintLength; // weeks
    this.userStories = [];
    this.sprintGoal = '';
    this.capacity = 0;
  }

  calculateTeamCapacity() {
    // Capacity = available hours - meetings - buffer
    const workHours = 40; // per person per week
    const meetingHours = 5; // estimated standups, retros, etc.
    const bufferPercent = 0.2; // 20% buffer for interruptions

    const capacityPerPerson = (workHours - meetingHours) * (1 - bufferPercent);
    this.capacity = capacityPerPerson * this.team.length * this.sprintLength;

    return this.capacity;
  }

  conductPlanningMeeting() {
    return {
      part1: {
        duration: '15 minutes',
        activity: 'Product Owner presents sprint goal',
        deliverable: 'Team understands business objective'
      },
      part2: {
        duration: '45-60 minutes',
        activity: 'Team discusses and estimates user stories',
        deliverable: 'Prioritized sprint backlog with story points'
      },
      part3: {
        duration: '15 minutes',
        activity: 'Team commits to sprint goal',
        deliverable: 'Formal sprint backlog committed'
      }
    };
  }

  createSprintBacklog(stories, capacity) {
    let currentCapacity = capacity;
    const sprintBacklog = [];

    for (let story of stories) {
      if (currentCapacity >= story.points) {
        sprintBacklog.push({
          ...story,
          status: 'planned',
          sprint: this.currentSprint
        });
        currentCapacity -= story.points;
      }
    }

    return {
      goal: this.sprintGoal,
      backlog: sprintBacklog,
      remainingCapacity: currentCapacity,
      utilization: ((capacity - currentCapacity) / capacity * 100).toFixed(1) + '%'
    };
  }
}

Read the full file on GitHub · 289 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 289 lines · 44 tokens per session scan A a04ab486073a

Subscribe to this mod's changes

agile-sprint-planning is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 1,838 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.