← ClaudeAtlas

sprint-lifecyclelisted

Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project
mulhamna/jira-commands · ★ 40 · Web & Frontend · score 67
Install: claude install-skill mulhamna/jira-commands
Manage the full sprint lifecycle for a Jira scrum board using `jirac`. Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Identify the operation: - **List**: `jirac issue sprints -p <PROJECT>` - **Create**: `jirac issue sprint-create -p <PROJECT> --name '<NAME>' [--board-id <ID>] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]` - **Start**: `jirac issue sprint-start <SPRINT_ID>` - **Complete**: `jirac issue sprint-complete <SPRINT_ID>` - **Update**: `jirac issue sprint-update <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]` - **Delete**: `jirac issue sprint-delete <SPRINT_ID>` (destructive — confirm intent) 3. Run `jirac issue sprints -p <PROJECT>` first when the user does not give a sprint ID — the list shows IDs and current state (future / active / closed). 4. Confirm intent before `sprint-start`, `sprint-complete`, and `sprint-delete` — these change visible board state for the whole team. Notes: - A board can only have **one active sprint** at a time. `sprint-start` will fail if another sprint is already active. - `sprint-complete` closes the sprint; any unfinished issues should be moved to a future sprint **before** completing. - `sprint-delete` permanently removes a sprint and detaches its issues from the sprint field — irreversible. - For a snapshot of work in a sprint (without changing