sprint-planning

sprint-planning is a skill for Claude Code, Codex from pilotspace/pilot-space. It costs 17 tokens per session (524 once invoked), scanned A, original, Apache-2.0.

A sprint-planning workflow for selecting unassigned backlog work and placing a prioritized checklist into the current project note. A sprint is a short, fixed work period for completing selected tasks.

In plain words
What is it for?
Use it to prepare a sprint checklist with issue references, suggested assignees, priorities, and the sprint end date.
Why use it?
It helps teams choose concrete work from the backlog and make ownership, priority, and deadlines visible. This avoids starting a sprint with an unstructured list of issues.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a sprint checklist with issue references, suggested assignees, priorities, and the sprint end date.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pilotspace/pilot-space/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 pilotspace/pilot-space --skill sprint-planning
Clone the repo
git clone --depth 1 https://github.com/pilotspace/pilot-space

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.

agentmods badge for sprint-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/sprint-planning/github.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/sprint-planning)
Your own site
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/sprint-planning"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/sprint-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sprint-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/sprint-planning"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/sprint-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 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.00017 $0.00524
Opus 5.5 $0.00007 $0.00210
Sonnet 5.5 $0.00003 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured 2mo ago against content hash 775659f7300f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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/src/pilot_space/ai/templates/skills/sprint-planning/SKILL.md · 66 lines

What it actually says

Sprint Planning Skill

You are helping the user plan a sprint. Follow these steps:

Steps

  1. Gather context: Use get_project to understand the current project scope and priorities.
  2. Find candidates: Use search_issues to find issues in Backlog or Todo state that are unassigned to a cycle.
  3. Generate checklist: Create a Smart Checklist (taskList) with the top priority items for the sprint.
  4. Insert into note: Use insert_block to add the checklist to the current note.

Output Format

Insert a taskList block with items structured as:

  • Each taskItem should have:
    • checked: false (not started)
    • assignee: suggested team member (if known from project context)
    • priority: mapped from issue priority
    • dueDate: sprint end date
    • Text: issue title with [PS-XX] reference

Example

For a 2-week sprint starting Feb 15:

{
  "type": "taskList",
  "content": [
    {
      "type": "taskItem",
      "attrs": { "checked": false, "priority": "high", "dueDate": "2026-02-28" },
      "content": [{ "type": "paragraph", "content": [{ "type": "text", "text": "[PS-42] Implement user authentication" }] }]
    },
    {
      "type": "taskItem",
      "attrs": { "checked": false, "priority": "medium", "dueDate": "2026-02-28" },
      "content": [{ "type": "paragraph", "content": [{ "type": "text", "text": "[PS-43] Add role-based access control" }] }]
    }
  ]
}

Rules

  • Maximum 15 items per sprint checklist
  • Prioritize by: urgent > high > medium > low
  • Include effort estimates if available from issues
  • Flag any items that have unresolved dependencies
  • If no issues found in backlog, suggest the user creates issues first
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. 2mo ago First seen · 66 lines · 17 tokens per session scan A 775659f7300f

Subscribe to this mod's changes

sprint-planning is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 524 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 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

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

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens