From ai-pm-assistant
Generates a structured Sprint Scope of Work document with goal, timeline, team table, deliverables by theme, out-of-scope list, and definition of done checklist. Supports Confluence, Google Drive, and Notion output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-pm-assistant:sprint-sow <sprint goal, dates, team, and ticket list><sprint goal, dates, team, and ticket list>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
$ARGUMENTS
$ARGUMENTS
If no input is provided above, ask: "Please share the sprint details - sprint number, goal, start and end dates, team members and roles, and the ticket list with assignees."
You produce sprint SOW documents that match the team's exact Confluence format. The output is a clean, structured markdown document ready to be pasted into Confluence or saved as a file.
Prepared By: [Name]
Date: [Date]
Link to the Jira Board: [URL]
A single-sentence blockquote capturing the purpose of the sprint.
## Sprint Goal
> [One punchy sentence describing what the sprint achieves and why it matters.]
2-4 sentences of plain English explaining what this sprint delivers (or doesn't), and why it exists in the context of the product.
## Overview
[Plain English explanation. What is being built. What is NOT being built. Why this sprint matters for future sprints.]
## Sprint Timeline
* Sprint Start: [Date]
* Sprint End: [Date]
A markdown table with columns: Team Member | Role | Assigned Tickets
Ticket references use Jira-style links: [TICKET-1](url)
## Sprint Team
| Team Member | Role | Assigned Tickets |
| --- | --- | --- |
| [Name] | [Role] | [TICKET-1](url), [TICKET-2](url) |
This is the core section. Group tickets into named themes. Each theme gets:
### N. Theme Name headingTicket | Deliverable | Description | Assignee--- divider after each theme tableRules:
--- after each theme block## Deliverables by Theme
### 1. [Theme Name]
[One sentence describing what this theme establishes and why.]
| Ticket | Deliverable | Description | Assignee |
| --- | --- | --- | --- |
| [TICKET](url) | [Short noun phrase] | [Plain English description of what it does.] | [Name] |
---
### 2. [Theme Name]
...
Typical themes (adapt to actual sprint content):
A bulleted list of items explicitly NOT in this sprint. Be specific - name deferred tickets and target sprints where known.
## Out of Scope - Sprint [N]
The following are explicitly excluded from this sprint and will be addressed in subsequent sprints:
* [Item]
* [Item - deferred to Sprint N ([TICKET](url))]
A checklist of binary, testable completion criteria. Each item must be objectively verifiable.
## Definition of Done
Sprint [N] is considered complete when all of the following conditions are met:
- [ ] [Testable condition]
- [ ] [Testable condition]
[TICKET-?](url) as a placeholder if not provided..claude/CLAUDE.md - ask where to save before writing anything. Default local path: clients/CLIENT/sprint-artefacts/YYYY-MM-DD-sprint-N-sow.md.claude/CLAUDE.md.npx claudepluginhub erica-j-01/ai-pmProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.