name: sprint-task-selector
description: Identifies the most important and "ready" tasks from a backlog to be moved into the next sprint. Use when preparing for sprint planning, refining a backlog, or deciding which tasks to tackle next based on impact, urgency, and readiness.

Sprint Task Selector

When This Skill Activates

Claude uses this skill when:
- Preparing for a sprint planning session
- Selecting tasks from a backlog for the next sprint
- Filtering tasks based on "Definition of Ready"
- Identifying high-priority candidates for implementation
- Working with the your team's Product Backlog project in Asana

Core Frameworks

1. Definition of Ready (DoR)

A task must meet these criteria before being selected for a sprint:
- Clear Requirement: Does it have a clear description and acceptance criteria?
- Design Ready: Are UX/UI designs complete (if applicable)?
- Feasibility: Has it been technically reviewed?
- Dependencies: Are all blockers resolved?
- Estimated: Does it have a rough effort estimate?

2. High-Value Selection (LNO Framework)

• Leverage (L): Tasks that move the needle significantly on core goals.
• Neutral (N): Necessary maintenance or secondary features.
• Overhead (O): Administrative or low-impact tasks.
  Goal: Maximize 'L' tasks in the sprint.

3. Asana Integration

When using the Asana MCP, prioritize tasks from the your team's Product Backlog project. Filter for tasks that are:
- In the "Backlog" or "Refinement" sections
- Have high priority custom fields (if available)
- Are unblocked

Action Templates

Template: Sprint Candidate Selection

# Sprint [Number] Candidate Selection

## 🎯 Top Leverage (L) Candidates
*High impact, goal-aligned tasks.*
1. **[Task Name]**
   - Rationale: [Why this matters now]
   - Readiness: [DoR status]
2. **[Task Name]**
   - Rationale: [Why this matters now]
   - Readiness: [DoR status]

## ⚖️ Neutral (N) & Maintenance
*Necessary but less strategic tasks.*
- [Task Name] ([DoR Status])
- [Task Name] ([DoR Status])

## ⚠️ Risks & Blockers
- [Task Name]: Blocked by [Dependency]
- [Task Name]: Missing Design

## Recommendation
- **Sprint Goal:** [Proposed Outcome]
- **Planned Capacity:** [X points/hours]

Quick Reference

🔍 Selector Checklist

Is it Ready?
- [ ] Requirements clear?
- [ ] Designs finished?
- [ ] No external blockers?
- [ ] Estimated?

Is it Important?
- [ ] Does it align with the current product goal?
- [ ] Is it a 'Leverage' task?
- [ ] Is there an upcoming deadline/milestone?

Key Quotes

Marty Cagan:

"Focus on outcomes, not just output."

The Agile Manifesto:

"Responding to change over following a plan."