Stats
Actions
Tags
From jira-orchestrator
Displays sprint dashboard with progress, velocity, burndown, stories, bugs, and tech debt. Supports plan, quality, and team subcommands for capacity, metrics, and workload.
How this command is triggered — by the user, by Claude, or both
Slash command
/jira-orchestrator:sprintThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /jira:sprint Consolidated command for sprint planning, metrics, quality tracking, and team management. ## Quick Usage ## Subcommands | Action | Description | Example | |--------|-------------|---------| | `metrics` | Real-time sprint dashboard (default) | `/jira:sprint metrics` | | `plan` | Capacity and velocity planning | `/jira:sprint plan --sprint-id 42` | | `quality` | Tech debt and code health | `/jira:sprint quality` | | `team` | Team capacity and workload | `/jira:sprint team --team platform` | ## Dashboard (Default) When run without arguments, displays: ## Sprint Planni...
Consolidated command for sprint planning, metrics, quality tracking, and team management.
# Show sprint dashboard (default)
/jira:sprint
# Sprint planning
/jira:sprint plan
# Quality metrics
/jira:sprint quality
# Team capacity
/jira:sprint team
| Action | Description | Example |
|---|---|---|
metrics | Real-time sprint dashboard (default) | /jira:sprint metrics |
plan | Capacity and velocity planning | /jira:sprint plan --sprint-id 42 |
quality | Tech debt and code health | /jira:sprint quality |
team | Team capacity and workload | /jira:sprint team --team platform |
When run without arguments, displays:
╔══════════════════════════════════════════════════════════════╗
║ SPRINT DASHBOARD: Sprint 42 - Feature Release ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ████████████░░░░░░░░ 62% ║
║ Days Left: 5 of 14 ║
╠══════════════════════════════════════════════════════════════╣
║ Stories: 12/20 done │ Bugs: 3/5 fixed │ Debt: 2 items ║
╠══════════════════════════════════════════════════════════════╣
║ Velocity: 34 pts (avg: 32) │ Burndown: On Track ✓ ║
╚══════════════════════════════════════════════════════════════╝
/jira:sprint plan [--sprint-id ID] [--team TEAM]
Shows:
/jira:sprint quality [ISSUE-KEY]
Displays:
/jira:sprint team [--team ID]
Shows:
This command consolidates:
/jira:sprint-plan → /jira:sprint plan/jira:metrics → /jira:sprint metrics/jira:quality → /jira:sprint quality/jira:team → /jira:sprint teamOld commands still work as aliases with deprecation notice.
npx claudepluginhub markus41/claude --plugin jira-orchestrator/sprint-planningPlans sprints by gathering context, analyzing Linear or GitHub backlog, and generating a markdown report with tasks, capacity, risks, and recommendations.
/sprintManages sprint lifecycle: plans sprints with capacity estimation and story selection, facilitates structured retrospectives, generates release notes from context.
/metricsAnalyzes team metrics like velocity tracking, cycle time, and performance for a specified metric-type and optional timeframe.
/retrospective-analyzerAnalyzes sprint retrospectives from Linear and GitHub data, generating metrics tables, performance trends, pattern recognition, and discussion topics for team facilitation.
/sprintOrchestrates autonomous multi-agent sprint workflow from specs through architecture, parallel implementation, QA/UI testing, review, and finalization. Resumes sprints or directs to setup/testing.