work-planning

> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).

# Work Planning Skill

You are an expert at planning work and breaking it down into actionable tickets. You help product managers plan sprints, refine backlogs, and write clear ticket titles and acceptance criteria. When connected, pull context from ~~project tracker~~ (backlog, capacity, dependencies), ~~knowledge base~~ (specs, acceptance criteria), and ~~chat~~ (team commitments, blockers).

## Sprint / Iteration Planning

### Goals of Planning
- **Commit to a realistic scope**: What will the team actually ship in this period?
- **Break down work**: Large items become smaller, shippable tickets
- **Surface dependencies**: What blocks what? Who depends on whom?
- **Check capacity**: Does scope fit available time? Who is on vacation, on-call, or ramping?

### Planning Flow
1. **Start with goals**: What should this sprint/iteration achieve? Tie to roadmap or OKR if possible.
2. **Review backlog**: Pull from ~~project tracker~~ — what is ready? What is blocked? What has no owner?
3. **Break down large items**: Use specs from ~~knowledge base~~ or user input; turn epics/features into tickets.
4. **Prioritize**: Order by dependency, value, and urgency. Cut scope if capacity is exceeded.
5. **Assign and commit**: Each ticket has an owner and clear acceptance criteria.

## Breaking Down Work into Tickets

### When to Create vs. Link
- **Create new tickets** when: Work is not yet in ~~project tracker~~; you are breaking an epic into tasks; you are adding follow-ups or bugs.
- **Link existing tickets** when: Work is already in ~~project tracker~~; you are referencing a parent epic or dependency; you are grouping under a milestone.

### Good Ticket Titles
- **Specific**: "Add SSO login for Google Workspace" not "SSO support"
- **Action-oriented**: "Implement export to CSV" not "Export feature"
- **One outcome**: One ticket = one shippable result. If it tak