Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

jira-agile-management

Étoiles41

Forks7

Mis à jour2 février 2026 à 00:04

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).

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

grandcamel

grandcamel/JIRA-Assistant-Skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Gestionnaires des services administratifsProfessions de direction et de gestion·SOC 11-3012

Explorateur de fichiers

13 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

jira-assistant

grandcamel/JIRA-Assistant-Skills

JIRA automation hub routing to 13 specialized skills for any JIRA task: issues, workflows, agile, search, time tracking, service management, and more.

2026-02-0241

jira-bulk-operations

grandcamel/JIRA-Assistant-Skills

Bulk operations for multiple issues at scale. TRIGGERS: 'bulk update', 'bulk close', 'bulk transition', 'bulk assign', 'transition N issues' (N >= 10), 'update all bugs', 'close 50 issues', 'mass transition', 'update multiple issues', quantities like '50 issues', '100 bugs', '20+ tickets'. Use for operations on 10+ issues. NOT FOR: single issue transitions (use jira-lifecycle), searching only without modifications (use jira-search), single issue field updates (use jira-issue).

2026-02-0241

jira-developer-integration

grandcamel/JIRA-Assistant-Skills

Git and developer workflow integration. TRIGGERS: 'generate branch name', 'create branch name', 'branch name for', 'write PR description', 'PR description for', 'link PR', 'link pull request', 'parse commit', 'extract issue from commit', 'smart commit', 'development panel'. Use for Git, GitHub, GitLab, Bitbucket integration with JIRA. NOT FOR: issue field updates (use jira-issue), searching issues (use jira-search), status transitions (use jira-lifecycle).

2026-02-0241

jira-custom-fields

grandcamel/JIRA-Assistant-Skills

Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield_', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA field metadata and discovery. NOT FOR: setting field values on issues (use jira-issue), setting story points (use jira-agile), searching by field values (use jira-search).

2026-02-0241

jira-issue-management

grandcamel/JIRA-Assistant-Skills

Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).

2026-02-0241

jira-operations

grandcamel/JIRA-Assistant-Skills

JIRA cache and performance operations. TRIGGERS: 'warm the cache', 'warm cache', 'cache status', 'clear cache', 'cache warm', 'cache for project', 'discover project', 'project discovery', 'cache hit rate', 'optimize performance', 'rate limit'. Use for JIRA API performance optimization and project context discovery. NOT FOR: project configuration/settings (use jira-admin), issue operations (use jira-issue), bulk issue modifications (use jira-bulk).

2026-02-0241

name	jira-agile-management
description	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).
version	1.0.0
author	jira-assistant-skills
license	MIT
allowed-tools	["Bash","Read","Glob","Grep"]

jira-agile

Agile and Scrum workflow management for JIRA - epics, sprints, backlogs, and story points.

Risk Levels

Operation	Risk	Notes
List sprints/epics	`-`	Read-only
Get backlog/velocity	`-`	Read-only
Create epic	`-`	Easily reversible (can delete)
Create subtask	`-`	Easily reversible (can delete)
Create sprint	`-`	Easily reversible (can delete)
Add issues to epic	`!`	Can move to different epic or remove
Move issues to sprint	`!`	Can move back to backlog
Set story points	`!`	Can update estimate
Start sprint	`!`	Sprint state change
Close sprint	`!`	Cannot undo - issues move to next sprint
Rank issues	`!`	Can re-rank

Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible

When to use this skill

Use this skill when you need to:

Create and manage epics for organizing large features
Link issues to epics for hierarchical planning
Create subtasks under parent issues
Track epic progress and story point completion
Create and manage sprints on Scrum boards
Move issues between sprints and backlog
Prioritize and rank backlog issues
Estimate issues with story points
Calculate team velocity from completed sprints

Do not use this skill when:

Creating individual stories/tasks without epic context (use jira-issue)
Searching issues by JQL (use jira-search)
Transitioning issues through workflow (use jira-lifecycle)
Managing time tracking/worklogs (use jira-time)
Discovering field configurations (use jira-fields)

See Skill Selection Guide for detailed guidance.

What this skill does

IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.

1. Epic Management

Create epics with Epic Name and Color fields, link stories/tasks to epics, and track epic progress with story point calculations.

See epic examples for detailed usage.

2. Subtask Management

Create subtasks linked to parent issues with automatic project inheritance and time estimate support.

3. Sprint Management

List and discover sprints for a project, create sprints with dates and goals, manage sprint lifecycle (start/close), move issues to sprints or backlog, and track sprint progress.

See sprint examples for detailed usage.

4. Backlog Management

View board backlog with epic grouping, rank issues by priority (before/after/top/bottom).

See backlog examples for detailed usage.

5. Story Points and Estimation

Set story points on single or bulk issues, validate against Fibonacci sequence, get estimation summaries grouped by status or assignee.

See estimation examples for detailed usage.

6. Velocity Tracking

Calculate team velocity from completed sprints. Shows average story points per sprint, trends, and historical data for planning.

Available Commands

Epic Management

jira-as agile epic create --project PROJ --summary "Mobile App MVP"
jira-as agile epic create --project PROJ --summary "MVP" --epic-name "Mobile MVP" --color blue
jira-as agile epic get PROJ-100 --with-children
jira-as agile epic add-issues --epic PROJ-100 --issues PROJ-101,PROJ-102
jira-as agile epic add-issues --epic PROJ-100 --jql "project = PROJ AND type = Story AND status = Open"
jira-as agile epic add-issues --epic PROJ-100 --issues PROJ-101 --dry-run  # Preview changes

Note: To remove issues from an epic, move them to a different epic or use jira-as issue update PROJ-103 --epic none to clear the epic link.

Subtask Management

jira-as agile subtask --parent PROJ-101 --summary "Implement login API"
jira-as agile subtask --parent PROJ-101 --summary "Task" --assignee self --estimate 4h

Sprint Management

jira-as agile sprint list --project DEMO                    # List all sprints for project
jira-as agile sprint list --project DEMO --state active     # Find active sprint
jira-as agile sprint list --board 123 --state closed        # List closed sprints
jira-as agile sprint list --board 123 --max-results 50      # Limit results
jira-as agile sprint get --board 123 --active               # Get active sprint details
jira-as agile sprint get 456 --include-issues               # Get sprint with issues
jira-as agile sprint create --board 123 --name "Sprint 42" --goal "Launch MVP"
jira-as agile sprint create --board 123 --name "Sprint 42" --start-date 2026-02-01 --end-date 2026-02-14
jira-as agile sprint move-issues --sprint 456 --issues PROJ-101,PROJ-102
jira-as agile sprint move-issues --sprint 456 --jql "project = PROJ AND sprint IS EMPTY"
jira-as agile sprint move-issues --backlog --issues PROJ-101,PROJ-102  # Move to backlog
jira-as agile sprint manage --sprint 456 --start
jira-as agile sprint manage --sprint 456 --close --move-incomplete-to 457
jira-as agile sprint manage --sprint 456 --name "Sprint 42 - Revised" --goal "Updated goal"

Backlog Management

jira-as agile backlog --board 123
jira-as agile backlog --board 123 --group-by epic
jira-as agile backlog --project PROJ                        # Use project instead of board
jira-as agile rank PROJ-101 --before PROJ-100
jira-as agile rank PROJ-101 --after PROJ-102
jira-as agile rank PROJ-101 --top --board 123               # Move to top (requires --board)
jira-as agile rank PROJ-101 --bottom --board 123            # Move to bottom (requires --board)

Story Points and Estimation

jira-as agile estimate PROJ-101 --points 5
jira-as agile estimates --project PROJ
jira-as agile estimates --sprint 456 --group-by assignee
jira-as agile estimates --epic "Mobile MVP" --group-by status  # Filter by epic name

Velocity Tracking

jira-as agile velocity --project PROJ                     # Last 3 sprints
jira-as agile velocity --project PROJ -n 5                # Last 5 sprints (-n is short for --sprints)
jira-as agile velocity --project PROJ --sprints 5         # Last 5 sprints
jira-as agile velocity --board 123 --output json          # JSON output

All commands support --help for full documentation.

Common options

All commands support:

--help - Show usage and examples

Most commands also support:

--output json - Output as JSON (query and creation commands)
--dry-run - Preview changes (where applicable)

See Options Reference for details.

Exit codes

Code	Meaning
0	Success
1	Error (validation, API, etc.)
130	Cancelled (Ctrl+C)

Integration with other skills

Skill	Integration
jira-issue	Create stories/tasks, then add to epics
jira-search	Find issues by JQL for bulk operations
jira-lifecycle	Transition epic children through workflow
jira-fields	Discover custom field IDs for your instance

Custom field IDs

Default Agile field IDs may vary by instance. See Field Reference for configuration.

Troubleshooting

See Troubleshooting Guide for common issues and solutions.

Best practices

For comprehensive guidance on sprint planning, estimation, and Agile workflows, see Best Practices Guide.