← ClaudeAtlas

sprint-operationslisted

Run the measurement and ceremony layer of a delivery team: the metric set, estimation and capacity, the five sprint ceremonies, and the sprint report and quarterly rollup. Use this skill whenever the user is acting as PMO or scrum lead, planning a sprint, running standup, refinement, review, or retro, measuring velocity, cycle time, or throughput, checking capacity, or reporting on how a team is doing. Triggers on PMO, sprint planning, plan the sprint, standup, refinement, backlog grooming, sprint review, retro, velocity, capacity, cycle time, lead time, throughput, WIP, burndown, carryover, sprint report, story points to hours, how is the team doing, delivery metrics, agent lanes. Also triggers when the user asks how much work fits in a sprint or whether a team is on track, even if they never say sprint or PMO.
rampstackco/claude-skills-pm · ★ 4 · AI & Automation · score 83
Install: claude install-skill rampstackco/claude-skills-pm
# Sprint Operations Run the measurement and ceremony layer of a delivery team so planning is grounded in history and reporting is derived from the tracker, not typed in. Tracker-agnostic: works with Jira, Linear, GitHub Issues, or your tracker of choice. --- ## When to use - Setting up the metric set for a new or inherited team - Planning a sprint and checking it against real capacity - Running standup, refinement, review, or retro with a consistent template - Answering "how is the team doing?" with numbers instead of adjectives - Writing the sprint report or the quarterly rollup - Deriving a points-to-hours ratio for finance - Measuring a team where some lanes are AI coding agents ## When NOT to use - Writing the tickets that go into the sprint (use `ticket-authoring`) - Writing the narrative of a retrospective or postmortem (use `after-action-report`) - Setting objectives and key results (use `okr-design`) - Deciding what ships this quarter (use `roadmap-planning`) - Writing the handoff for an agent lane (use `dispatch-authoring`) - Shaping the readout for executives (use `stakeholder-communication`) --- ## Required inputs - Tracker access or an export with created, started, done, reopened, and sprint fields per ticket - The team roster and planned availability for the sprint - The last three to six sprints of history, if they exist - The team's estimation scale (points, t-shirt sizes, or counts) - Finance requirements for hours, if the team capitalizes development