Step 5 — Group into an epic and rank
Epic-add, backlog ranking, and blocks links. Every ordering decision here is dev-declared — the skill never reorders on its own judgment.
Prompt
/mk:jira-agile epic-add AUTH-200 AUTH-201 AUTH-202 AUTH-203
/mk:jira-agile rank AUTH-202 --before AUTH-201 # session expiry blocks the redirect
/mk:jira-relationships link AUTH-201 blocks AUTH-203What happens behind the scenes
| Skill | Verb | Effect |
|---|---|---|
mk:jira-agile | epic-add | Sets the epic-link custom field on each child issue |
mk:jira-agile | rank | Calls /rest/agile/1.0/issue/rank to reorder backlog |
mk:jira-relationships | link | Creates a "blocks" issue link (visible on both tickets) |
Decision point
Ranking is dev-declared, not inferred
The agent did not read "blocks" from the spec — you told it. The spec analyst can suggest dependencies in its report, but the actual ranking is always your call. The skill never reorders based on its own judgment.
Previous: Step 4 — Create the Jira tickets · Next: Step 6 — Refine and estimate · All steps
Step 4 — Create the Jira tickets (your decision)
One verb, one issue — no bulk creation. The Confluence URL carried in the description is the only sync mechanism between the spec and the tickets.
Step 6 — Refine and estimate
mk:jira-evaluator grades ACs, complexity and contradictions; mk:jira-estimator chains off it to suggest story points with an uncertainty annotation. Both are read-only.