jira-magister
Project approved DR/SRS and Use Case contracts into a reviewable Jira backlog, and format or persist a single already-specified Jira item. Use whenever a user asks to create, decompose, refine, synchronize, or update Jira Epics, User Stories, or technical Tasks — from a PRD, DR/SRS, Use Case, JTBD, acceptance check, RFC, or requirements document, or from one item the user has already specified. Propose multiple cohesive Epics that fit a few sprints, write actor-facing Stories sized for one two-week sprint, separate enabling work into Tasks, preserve source traceability, and require explicit confirmation before Jira mutations.
Pinned to revision 20a030d74b73, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/jira-magister/SKILL.md
- skills/jira-magister/evals/evals.json
- skills/jira-magister/references/issue-contract.md
- skills/jira-magister/references/persistence.md
Every link opens the file at its source, pinned to the revision this page describes.