start-sprint

start-sprint is a command for Claude Code from ParkerM2/create-claude-workflow. It costs 40 tokens per session (14,887 once invoked), scanned A, original, MIT.

A sprint kickoff coordinator that collects Jira tickets, has research agents examine them, rates their difficulty from 1 to 5, and prepares plans for easier tickets. Jira is a tool for tracking software work.

In plain words
What is it for?
Use it to create a sprint overview, investigate tickets in parallel, plan low-to-medium difficulty work, and flag difficult tickets.
Why use it?
It reduces the manual sorting and initial investigation needed at the start of a sprint, while sending the hardest tickets for human review.

Command for Claude Code

Part of the claude-workflow plugin — 10 skills, 25 commands, 3 agents, 6 hooks shipped together

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.

agentmods
npx agentmods add commands/parkerm2/create-claude-workflow/start-sprint
Clone the repo
git clone --depth 1 https://github.com/ParkerM2/create-claude-workflow

Made for: Claude Code.

Or install claude-workflow, the plugin that ships this one along with the rest of its 10 skills, 25 commands, 3 agents, 6 hooks.

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 start-sprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/start-sprint.svg)](https://agentmods.dev/commands/parkerm2/create-claude-workflow/start-sprint)
Your own site
<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/start-sprint"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/start-sprint.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 14,887 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.14887
Opus 5 $0.00020 $0.07444
Sonnet 5 $0.00008 $0.02977
Haiku 4.5 $0.00004 $0.01489

Measured 4d ago against content hash 880c95d86096, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start-sprint 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.

.claude/commands/start-sprint.md · 1,772 lines

How it starts

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

/start-sprint — Sprint Kickoff Orchestration

Team Leader agent that orchestrates a full sprint kickoff: fetches all Jira tickets, spawns parallel research agents, assesses difficulty, and generates implementation plans for Level 1-3 tickets. Level 4-5 tickets are flagged for human review. You do NOT perform research — you only orchestrate.

COMMAND OVERVIEW

The /start-sprint command is the central orchestration hub for sprint kickoff. It acts as a Team Leader agent that:

  1. Fetches all tickets from the active Jira sprint
  2. Spawns research agents in parallel to deeply analyze each ticket
  3. Assesses difficulty of each ticket based on research findings
  4. Generates plans in parallel for tickets rated LOW-MEDIUM difficulty
  5. Produces a sprint summary dashboard with actionable next steps

The command never performs research itself — it only orchestrates, collects results, and synthesizes summaries.


PHASE 1: SPRINT INTAKE

1.1 Memory System & Sprint Context

Before starting, verify or establish sprint context:

# .claude/.memory/sprint-context.json (managed by memory system)
{
  "active_sprint_id": "SPRINT-42",
  "active_sprint_name": "Q1 2026 Sprint 2",
  "jira_board_id": "123",
  "jira_project_key": "DEV",
  "confluence_space_key": "DEV",
  "start_timestamp": "2026-03-27T09:00:00Z",
  "agent_team_size": 0,  # Updated as agents spawn
  "max_parallel_agents": 20
}

Action: If sprint context missing, prompt user to:

  • Run /connect-atlassian to link Jira
  • Provide Jira board ID and project key
  • Select active sprint from available sprints list

1.2 Identify Active Sprint (CRITICAL: Sprint Scope Filtering)

You MUST identify and filter to the active sprint. Never fetch the full backlog or future sprint tickets.

Step 1: Fetch all sprints for the board and identify the ACTIVE one:

jira_get_sprints_from_board(boardId: <board_id>)

From the response, find the sprint where state == "active". If multiple active sprints exist (rare), present them to the user and ask which one. If NO active sprint exists, check for the next future sprint and ask if they want to kick off that one.

Read the full file on GitHub · 1,772 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 · 1,772 lines · 40 tokens per session scan A 880c95d86096

Subscribe to this mod's changes

start-sprint is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 14,887 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-08-31.