Write scannable sprint briefs
sprint-briefskillsetup L1★327
mohitagw15856/pm-claude-skills ↗What it does
Produce scannable sprint briefs teams understand in <3 minutes
Best for
Mixed teams (eng, design, PM) needing a single source of truth that every role can scan before standup.
Inputs
- · Sprint name and number
- · Sprint goal (1-2 sentences)
- · Ticket list with owners
- · Known dependencies or blockers
- · Carry-over items from previous sprint
Outputs
- · Sprint brief with goal, themes, critical path, risks, and definition of done
- · Risk flags with mitigations
- · Carry-over impact analysis
Preconditions
- · Sprint goal articulated (or flagged as too vague)
- · Ticket ownership assigned
- · Clarity on sprint dependencies
Failure modes
- · Sprint goal is too vague (flagged but not fixed)
- · Critical path tickets not named specifically
- · Risks listed without mitigations
- · Overloaded sprint not detected until execution
Trust signals
- · Validation: sprint goal must be specific and measurable enough to score pass/fail
- · Critical path explicitly named (not vague)
- · Risk assessment tied to capacity and critical path
- · Definition of done is criteria, not a task list