jira-agile_skill

Overview

This skill automates Epic creation, sprint lifecycle, backlog management, and story point estimation for JIRA Agile boards. It provides CLI commands to create epics and subtasks, manage sprints, move issues between backlog and sprints, and calculate velocity. Use it to streamline planning and keep epic-level work visible and organized.

How this skill works

The skill exposes a set of jira-as CLI commands that interact with JIRA Agile APIs to list and modify epics, sprints, backlog and estimates. You can create epics, link issues to epics, create subtasks, move issues into sprints or backlog, and set story points individually or in bulk. Read-only commands (list/get) are safe; modifying operations support dry-run previews where available.

When to use it

• When you need to create and manage epics to organize large features.
• During sprint planning to create sprints, set dates/goals, and move issues into a sprint.
• To view and rank the backlog or group it by epic for planning sessions.
• When assigning or updating story point estimates for single or multiple issues.
• To calculate team velocity from completed sprints for capacity planning.

Best practices

• Always run destructive or large updates with --dry-run first to preview changes.
• Create epics before creating child stories so hierarchy and reporting stay consistent.
• Use board or project scoping flags (--board or --project) to avoid moving issues on the wrong board.
• Validate estimates against your agreed Fibonacci sequence and update consistently.
• Prefer read-only list/get commands for discovery; use targeted move/add commands for changes.

Example use cases

• Create an epic for a new feature and link existing stories to it for roll-up reporting.
• During sprint planning, create a sprint with start/end dates and move prioritized issues into it.
• Bulk-set story points for a group of issues returned by a JQL query before planning.
• View backlog grouped by epic to identify scope gaps and re-rank high-priority items to the top.
• Calculate average velocity from the last 3–5 completed sprints to inform next sprint capacity.