sprint-lifecycle SKILL.md skillB
sprint-lifecycle from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mulhamna/jira-commands/sprint-lifecycle@git:20261029.f79e226Pins git:20261029.f79e226 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mulhamna/jira-commands
- Path
plugin/skills/sprint-lifecycle/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261029.f79e226, committed Oct 29, 2026
- First version recorded
- May 21, 2026
- Size
- 2,716 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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 -p <PROJECT> --sprint <SPRINT_ID> --end-date YYYY-MM-DD` - **Complete**: `jirac issue sprint-complete -p <PROJECT> --sprint <SPRINT_ID>` - **Update**: `jirac issue sprint-update -p <PROJECT> --sprint <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]` - **Delete**: `jirac issue sprint-delete -p <PROJECT> --sprint <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). …
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/sprint-lifecycle@sha256:667327f0150ef134The line at the top of this page pins the label git:20261029.f79e226, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ezgqagwdku3dr3er)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 21, 2026 and Oct 29, 2026, about one every 161 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.f79e226 latest | 2026-10-29 | f79e226 | 2,716 B | B | view · diff |
| git:20260521.f34ad5e | 2026-05-21 | f34ad5e | 2,268 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2716 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
mulhamna/jira-commands · 54 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ezgqagwdku3dr3er GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/sprint-lifecycle GET https://markdownregistry.com/api/v1/blob/667327f0150ef1341935888eb849079a9587cb83fc7d1559961030d78669b82d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.