Mid-Sprint Health Check
Mid-sprint diagnosis from your board: burn vs time, added scope, aging work, review queues, and the smallest fix or exact cut.
Before & after
Same prompt, same agent — the only difference is the skill.
You'd need to look at a few things like story point velocity, how many bugs came up, whether the team is blocked, and if the release is at risk. You might check burn-down charts and see if the team is on pace. You could also ask about blockers and team morale. I'd suggest comparing against your baseline velocity and flag if you're significantly behind. Do you have data on what you planned vs what you've completed so far?
SPRINT HEALTH DASHBOARD: Sprint 27 OVERALL HEALTH SCORE: 7/10 (Yellow — at risk) VELOCITY Planned: 42 points | In progress: 39 points | Completed: 18 points (43% of sprint) Trend: -8% below 4-sprint average (46 points); watch Tuesday refresh RISK FLAGS RED: Backend performance issue discovered day 4 → 3-day fix; ripples to 4 frontend stories YELLOW: QA capacity bottleneck; 8 stories waiting sign-off GREEN: No team departures; morale stable BUG RATE Incoming bugs: 6 (critical: 1, high: 3, medium: 2) Ratio vs. story points: 14% — acceptable (baseline 12%) BLOCKERS (3) 1. Design asset feedback loop 48h+ (owns progress on 2 frontend stories) 2. Staging environment flaky; 4-5 deploys per day failing 3. One engineer out sick, backfill in progress RECOMMENDATION Do NOT commit new scope. Pick 3 mid-sprint priorities; defer rest. Tuesday reset meeting with product to re-baseline.
About this skill
Find out whether this sprint will land while there is still time to change it. The check reads your board, looks past points completed to the leading indicators, and recommends the smallest move that fixes the trajectory.
What it does
- Compares done work to time elapsed and separates added scope from normal ticket splitting
- Flags items in progress longer than the team's typical cycle time
- Spots growing review or QA queues, too much work started, and blocked or unowned items
- Judges the sprint goal, not just the ticket count
- Recommends the smallest corrective action first, and names exactly what to cut if needed
What you get
An on track, at risk, or off track verdict with the signals behind it, ranked actions, optional cut list, and data gaps.
Best for
Scrum masters, engineering managers, and tech leads mid-sprint, or anyone writing a sprint status update.
SKILL.md preview
---
name: mid-sprint-health-check
description: Diagnose an in-progress sprint from its board or ticket export - expected vs actual burn, scope added since day one, work-in-progress aging against normal cycle time, review and QA queues, blocked and unowned tickets, and too much started at once - then call it on track, at risk, or off track and recommend the smallest corrective move, including exactly what to cut if needed. Use mid-sprint when someone asks "are we on track?", "day 6 of 10, how's the sprint?", "should we cut scope?", "what's stuck?", "sprint status for stakeholders", or pastes a Jira/Linear board and asks how it looks.
---
# Mid-Sprint Health Check
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.