📋Skill + MCP
Linear sprint setup
Creates a Linear sprint from a goal, sized to team velocity, with labels and estimates.
- Surfaces
- skill · mcp
- Complexity
- intermediate
- Trigger
- natural
- Est. tokens
- 5,600
- Requires MCP
- linear
What It Does
Turns a one-line sprint goal into a fully populated Linear cycle. The skill pulls team velocity from recent completed cycles, breaks the goal into 3–8 right-sized issues, and creates them with labels and estimates summing to 90% of velocity.
When It Triggers
- ▸"Plan our next sprint"
- ▸"Set up the Q2 sprint in Linear"
- ▸"Create tasks for sprint X in Linear"
Prerequisites
- ▸Linear MCP connected (Settings → Extensions → Linear)
- ▸Team has at least 3 completed cycles for velocity inference
SKILL.md
markdown
---
name: linear-sprint-setup
description: Creates a sprint in Linear with prioritized tasks based on a goal. Uses Linear MCP to fetch team velocity and create issues. Use when user says "plan this sprint", "set up sprint", or "create Linear sprint".
---
# Linear Sprint Setup
## Requires
- Linear MCP connected (Settings → Extensions → Linear)
## Steps
1. Fetch team via `linear_getTeam`
2. Fetch recent velocity via `linear_listIssues` with filters for completed cycles
3. Ask the user for sprint goal and duration if not provided
4. Break the goal into 3–8 issues with estimates summing to velocity × 0.9
5. Create each issue via `linear_createIssue` with labels and estimates
6. Return a checklist with links to each created issue
Gotchas
- ▸First sprint for a team will lack velocity data — pass an explicit capacity in the prompt.
- ▸Labels are team-specific; the skill auto-discovers them via linear_listLabels.
- ▸Commit to 90% of velocity, not 100% — leaves room for unplanned work.