sprint-brief
The sprint-brief skill generates a structured, team-readable sprint overview document from sprint data, goals, and ticket lists. Use this skill when a product manager or team lead needs to create a sprint brief, document sprint scope and goals, or produce a clear summary that engineers, designers, and stakeholders can scan in under three minutes. The output includes sprint goal, rationale, work grouped by theme, critical path items, flagged risks with mitigations, carry-over items, and definition of done criteria.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/sprint-brief && cp -r /tmp/sprint-brief/plugins/pm-delivery/skills/sprint-brief ~/.claude/skills/sprint-briefSKILL.md
# Sprint Brief Skill Produce a clear, scannable sprint brief that every team member — engineer, designer, PM — can read in under three minutes and understand exactly what we're doing and why. ## Required Inputs Ask the user for these if not provided: - **Sprint name and number** - **Sprint goal** (1-2 sentences — flag if too vague) - **Ticket list with owners** (or a description of the work) - **Known dependencies or blockers** - **Carry-over items from previous sprint** (if any) ## Process 1. Read sprint goal and check it's specific and measurable — flag if it's too vague 2. Group tickets by theme or feature area 3. Identify the critical path — which tickets must complete for the sprint goal to be met? 4. Flag risks: tickets with unclear acceptance criteria, missing designs, unresolved dependencies 5. Note carry-over items and whether they affect this sprint's goal 6. **Validate** — Confirm the sprint goal is achievable given the ticket scope and capacity. If the critical path items alone would fill the sprint, flag it as overloaded. ## Output Structure ### Sprint [Number] Brief — [Dates] **Sprint Goal:** [1-2 sentences — specific and measurable] **Why This Sprint Matters:** [Connect to quarterly OKR in 2-3 sentences] **What We're Building:** - [Theme 1]: [tickets and owners] - [Theme 2]: [tickets and owners] **Critical Path:** [The 2-3 tickets everything else depends on] **Risks to Flag:** - [Risk 1 + mitigation] - [Risk 2 + mitigation] **Carry-over from Last Sprint:** [List + impact on current goal] **Definition of Done:** [Specific, agreed criteria for sprint success] ## Quality Checks - [ ] Sprint goal is specific enough to score pass/fail at the end of the sprint - [ ] Critical path items are named — not just "the important ones" - [ ] Every risk has a mitigation or owner (not just "this is a risk") - [ ] Carry-over items are connected to their impact on this sprint's goal - [ ] Definition of Done is agreed criteria, not a task list ## Anti-Patterns - [ ] Do not write a sprint goal as a task list — the goal must be a single outcome-focused statement that can be scored pass/fail - [ ] Do not leave the critical path unnamed — "the important tickets" is not a critical path - [ ] Do not list risks without a mitigation or owner — a risk without a response is just a worry list - [ ] Do not ignore carry-over items' impact on this sprint's capacity and goal - [ ] Do not write a Definition of Done that mixes task completion with outcome criteria — they must be observable and agreed before the sprint starts
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.