Stats
Actions
Tags
From astravue
Plans sprints by analyzing backlog, overdue tasks, and dependencies in Astravue. Useful when organizing upcoming work or reviewing the backlog.
How this skill is triggered — by the user, by Claude, or both
Slash command
/astravue:sprint-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Scope the project**
Scope the project
Ask which project to plan for. Use astravue_list_projects if needed.
Gather backlog state
astravue_list_project_tasks — all tasks with status and priorityastravue_list_overdue_tasks — urgent carry-oversastravue_list_dependencies — blocking relationshipsastravue_get_task_counts — status distributionPrioritize
Rank tasks by:
Present the sprint plan
Show a prioritized list with reasoning. Ask the user to confirm, adjust, or remove items before making changes.
Apply changes
After confirmation, use astravue_bulk_update_tasks to update priorities or statuses. Never modify tasks without explicit approval.
npx claudepluginhub astravueorg/astravue-mcp-server --plugin astravueReviews overdue and at-risk tasks in Astravue, identifies why each is slipping, and proposes reschedule, reassign, deprioritize, or close actions before applying them with user approval.
Epic creation and sprint management - create epics, manage sprints, view backlog, estimate with story points. TRIGGERS: 'create an epic', 'create epic', 'new epic', 'show the backlog', 'view backlog', 'add to sprint', 'move to sprint', 'set story points', 'sprint planning', 'epic for', 'link to epic', 'sprint list', 'active sprint', 'velocity', 'create subtask'. NOT FOR: bugs/tasks/stories without epic context (use jira-issue), field ID discovery (use jira-fields), searching issues by JQL (use jira-search), transitioning issues through workflow (use jira-lifecycle).
Plans sprints by estimating capacity from velocity and availability, selecting backlog stories, mapping dependencies, identifying risks, and outputting a summary with goal. Use for sprint prep.