sprint-prep

Audit Jira tickets and draft Slack-ready sprint plan messages.

3|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill sprint-prep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-prep
Source: https://github.com/dimagi/dimagi-claude-workflows/tree/main/plugins/commcare-tech/skills/sprint-prep
Command: npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill sprint-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers quickly prepare a clear, Slack-ready sprint plan by auditing Jira boards, surfacing highlights and at-risk work, and drafting both a short channel TLDR and a detailed thread update so updates are consistent and easy to post.

Core Features & Use Cases

  • Discover active and future Platform and Product sprints in the SAAS project and identify current and next sprint assignments for a specified engineer.
  • Aggregate ticket status internally, group completed work into highlight categories, identify carryovers with explicit reasons, and summarize next-sprint items and upcoming challenges.
  • Conduct an interactive four-question dialog with the engineer to collect human-selected highlights, carryover explanations, next-sprint priorities, and risks, then produce a two-part Slack-ready message (TLDR + full thread) formatted for posting.
  • Use case: an engineer uses the skill before sprint planning to auto-generate the standard sprint update message for #commcare-tech-sprint-grooming-and-planning, calling out blockers that need attention.

Quick Start

Run the sprint-prep skill with an engineer name or omit the argument to self-assign, for example: /sprint-prep Graham.

Frequently Asked Questions about sprint-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint planning update from Jira tickets for Slack?

To generate a sprint planning update, the skill audits your Jira tickets, groups completed work into highlights, identifies carryovers, and drafts a Slack-ready sprint plan message for posting.

What is the best way to surface at-risk work and carryovers before a sprint planning meeting?

Surface at-risk work and carryovers by running the skill to audit current Jira board statuses, which identifies incomplete tickets and prompts you interactively to explain carryover reasons and risks.

Can I use this skill to auto-post sprint highlights to a Slack channel?

Yes, the skill optionally posts a two-part sprint update message containing a channel TLDR and a detailed thread to a configured Slack channel while maintaining strict read-only access to Jira.

Does generating a sprint plan require write access to modify Jira tickets or sprints?

No, generating a sprint plan requires only read-only Jira access with the provided cloud ID to query sprints and issues, enforcing strict safety rules against modifying tickets or sprints.

How do I draft a sprint status update for a specific engineer's assigned issues?

Draft a sprint status update by passing an engineer's name to the skill, which fetches their assigned Jira issues and conducts an interactive Q&A to collect next-sprint items and upcoming challenges.

What information do I need to provide when preparing a sprint plan for the CommCare Tech project?

Preparing a sprint plan requires providing human-selected highlights, carryover explanations, next-sprint priorities, and risks during an interactive four-question dialog with the skill.