Scans Jira for stale issues, duplicates, and missing fields, then fixes what the user approves. Use when the user says the board is a mess, asks for a backlog grooming pass, wants to clean up Jira, or asks about stale/duplicate tickets before sprint planning.
The front door to this plugin. Listens to what the user needs right now — vague or specific — and routes them to the right skill. Trigger whenever the user asks "what can you do," "help me with the team/board/sprint," "what should I focus on," or any open-ended project-management request that doesn't clearly match a single skill.
Update, create, or reprioritize the team's roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from Jira epics.
Closes out a 2-week sprint — reconciles planned vs. completed scope, flags spillover and scope creep, writes a retro-ready summary, and gives a heads-up on the next sprint's readiness. Use when the user says the sprint is ending, asks for a sprint report, wants retro prep, or asks what's carrying over to next sprint.
Plan the next 2-week sprint — scope work from the Jira backlog, estimate team capacity (accounting for PTO), set a sprint goal, and draft a sprint plan. Use when kicking off a new sprint, sizing the backlog against team availability, deciding what's P0 vs. stretch, or handling carryover flagged by `sprint-close`.
Generates a one-page weekly status brief from Jira — sprint burndown, what shipped, what's blocked, and the week ahead. Built for a Scrum team running 2-week sprints. Use when the user asks for a status update, standup summary, sprint check-in, or "what's the team working on."
Scores open Jira tickets by urgency, staleness, and priority to produce a ranked "work these first" list with context, drafts status-update comments, and flags unassigned or overdue issues. Use when the user asks what to work on next, wants a triage pass on the backlog, or asks "what's most urgent" or "what's overdue."
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or ticket request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec ready to become Jira epics and stories.