Skills sprint-planner

📦

sprint-planner

Name: sprint-planner
Author: shubhamsaboo

v1.0.0 Content revision r1 Safe ⚙️ External commands

Plan Agile Sprints With Clear Capacity

Sprint planning often stalls when scope, estimates, and capacity are unclear. This skill guides Claude, Codex, and Claude Code to create sprint goals, backlog tables, risks, and done criteria.

Supports: Claude Codex Code(CC)

🥈 80 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "sprint-planner" from https://skillstore.io/skills/shubhamsaboo-sprint-planner.md and its manifest at https://skillstore.io/api/skills/shubhamsaboo-sprint-planner/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/shubhamsaboo-sprint-planner.md Signed manifest GET /api/skills/shubhamsaboo-sprint-planner/manifest Signed lockfile GET /api/skills/shubhamsaboo-sprint-planner/lockfile

Test it

Using "sprint-planner". Plan Sprint 12 for a team with 48 available focus hours and five prioritized stories.

Expected outcome:

Sprint 12 includes a measurable goal, 21 committed points, a backlog table with owners, two dependency risks, and a definition of done checklist.

Using "sprint-planner". Review this backlog and reduce scope for a team member on vacation.

Expected outcome:

The plan lowers capacity, removes the least critical 8-point story, keeps the sprint goal intact, and lists the deferred work.

Using "sprint-planner". Create a sprint plan for a release hardening sprint.

Expected outcome:

The output prioritizes bug fixes, validation work, staging readiness, risk mitigation, and product owner approval before release.

Security Audit

Safe

v2 • 7/7/2026 Open versioned report

The only static finding is a false positive caused by a markdown code fence in SKILL.md lines 35-57. I found no executable code, command instructions, network use, environment access, prompt injection, or data exfiltration intent in the reviewed file.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:35-57

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/shubhamsaboo-sprint-planner/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/shubhamsaboo-sprint-planner/security.svg)](https://skillstore.io/skills/shubhamsaboo-sprint-planner?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/shubhamsaboo-sprint-planner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shubhamsaboo-sprint-planner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/shubhamsaboo-sprint-planner.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

shubhamsaboo. (2026). sprint-planner security audit report (audit version 2) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/shubhamsaboo-sprint-planner/audits/2

BibTeX citation

@techreport{shubhamsaboo-shubhamsaboo-sprint-planner-2026,
  author = {shubhamsaboo},
  title = {sprint-planner security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/shubhamsaboo-sprint-planner/audits/2},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "sprint-planner security audit report (audit version 2)"
version: "1.0.0"
type: report
authors:
  - name: "shubhamsaboo"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/shubhamsaboo-sprint-planner/audits/2"
identifiers:
  - type: other
    value: "skillstore:shubhamsaboo-sprint-planner:audit:2"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare Sprint Planning

Create a structured plan with capacity, candidate backlog items, dependencies, and a clear sprint goal.

Align Scope With Goals

Turn product priorities into a sprint-ready backlog that supports a specific business outcome.

Balance Team Load

Compare estimated work with team capacity before the team commits to sprint scope.

Try These Prompts

Create a Basic Sprint Plan

Plan a two-week sprint for this backlog. Include a sprint goal, capacity, committed points, sprint backlog table, risks, and definition of done.

Estimate and Select Stories

Review these user stories, suggest Modified Fibonacci point estimates, and select a realistic sprint backlog based on our team capacity.

Resolve Capacity Constraints

Our team has reduced availability this sprint. Calculate practical capacity, flag overcommitment risks, and recommend which backlog items to defer.

Build a Risk-Aware Sprint Commitment

Create a sprint plan for these prioritized stories. Account for dependencies, recent velocity, delivery risks, mitigation actions, and acceptance readiness.

Best Practices

Provide team size, sprint dates, focus factor, recent velocity, and known time off.
Include story IDs, acceptance criteria, dependencies, and priority when requesting a sprint plan.
Use the generated plan as a facilitation aid and confirm commitments with the team.

Avoid

Do not use the skill to force commitments without team agreement.
Do not treat point estimates as exact delivery guarantees.
Do not omit dependencies, blocked work, or planned absences from the planning input.

Frequently Asked Questions

What does this skill help plan?

It helps plan agile sprints with goals, capacity, story estimates, backlog scope, risks, and definition of done.

Does it connect to Jira or other tools?

No. It works from information provided in the prompt and does not connect to external systems.

Can it estimate story points?

Yes. It uses a Modified Fibonacci scale and can suggest estimates when story details are provided.

What inputs improve the result?

Provide team availability, sprint length, recent velocity, backlog items, priorities, dependencies, and acceptance criteria.

Can it choose the final sprint commitment?

It can recommend a commitment, but the team and product owner should confirm the final scope.

Is it suitable for non-scrum teams?

It is best for scrum-style sprint planning, but kanban or hybrid teams can adapt the structure.

Developer Details

Author

shubhamsaboo

License

MIT

Author version

v1.0.0

Skillstore revision

Repository

https://github.com/shubhamsaboo/awesome-llm-apps/tree/main/awesome_agent_skills/sprint-planner

Ref

412e23e39ccd9729546286287b96bb41707397cf

Maintenance freshness

7/18/2026

Usage

1 downloads · 0 views

File structure

📄 SKILL.md