What is sprint-planning?

A guide for preparing a sprint, a short development work period, by reviewing tasks, estimating effort, setting priorities, assigning people, and publishing the plan. It uses T-shirt sizes such as S, M, and L for rough estimates and MoSCoW labels for priority.

Use it to plan the next sprint, split or prioritize backlog items, assign work, create Jira issues and sprints, and publish the plan in Confluence.

It turns an unfinished backlog into a concrete set of planned work and makes the reasons for priorities and estimates visible. For analysis projects, it also turns findings into Jira improvement stories.

sprint-planning — Skill for Claude Code and Codex by omnigentx

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 omnigentx/jarvis --skill sprint-planning

Clone the repo

git clone --depth 1 https://github.com/omnigentx/jarvis

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/omnigentx/jarvis/sprint-planning.svg)](https://agentmods.dev/skills/omnigentx/jarvis/sprint-planning)

Your own site

<a href="https://agentmods.dev/skills/omnigentx/jarvis/sprint-planning"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/sprint-planning.svg" alt="Measured on agentmods" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 746 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00746
Opus 5	$0.00015	$0.00373
Sonnet 5	$0.00006	$0.00149
Haiku 4.5	$0.00003	$0.00075

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

Security

Grade A, and why

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 8d 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.

backend/.fast-agent/skills/sprint-planning/SKILL.md · 87 lines

How it starts

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

SPRINT PLANNING

Process

Review backlog: Read list of incomplete tasks/features
Estimate effort: Use T-shirt sizing (S/M/L/XL)
- S: < 30 min, 1 member
- M: 1-2 hours, 1-2 members
- L: 3-5 hours, 2-3 members
- XL: > 5 hours, must be split
Prioritize: MoSCoW method (Must/Should/Could/Won't)
Assign: Select needed members (see team-roster)
Output: Sprint plan on Confluence + Jira issues

Backlog Creation (for Analysis projects)

When the team is doing analysis/evaluation, the backlog IS the deliverable:

Collect inputs from team members (BA gap analysis, SA architecture review, Dev code analysis)
Create Jira stories for each improvement item:
- Summary: [IMPROVEMENT] <concise title>
- Description: Problem statement, proposed solution, expected impact
- Priority: Must/Should/Could/Won't
- Estimate: S/M/L/XL
- Acceptance Criteria: Definition of Done
Create sprint: jira_create_sprint(board_id, name), move prioritized items in
Publish sprint plan: confluence_create_page with full overview + priority rationale

Sprint Plan Template

Publish to Confluence (NOT workspace MD file):

# Sprint [N] Plan
## Goal: [Sprint objective]
## Duration: [Start date] → [End date]

| # | Task | Priority | Size | Assigned | Jira Key | Status |
|---|------|----------|------|----------|----------|--------|
| 1 | ...  | Must     | M    | Minh - Dev | JAR-xx | TODO   |

Visualizing the sprint

When the sprint timeline or task dependencies need to be reviewed by stakeholders, embed a Mermaid diagram alongside the table — the dashboard renders it inline.

Gantt for the timeline:

gantt
    title Sprint [N] Timeline
    dateFormat  YYYY-MM-DD
    section Must-have
    Task A          :a1, 2026-05-01, 2d
    Task B          :a2, after a1, 3d
    section Should-have
    Task C          :b1, 2026-05-04, 2d

Flowchart when tasks have ordering / dependency:

Read the full file on GitHub · 87 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.

8d ago First seen · 87 lines · 29 tokens per session scan A c28ff1520a31

Subscribe to this mod's changes

sprint-planning is a skill published in the GitHub repository omnigentx/jarvis (37 stars, last pushed 12d ago), licensed MIT. It adds 29 tokens to every session and 746 once invoked, about $0.0001 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-08-30.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens