mkjira-agilelisted

# mk:jira-agile Forks to the `jira-agile` agent. Sprint operations require a numeric `--board-id`, not the project key. The agent resolves project name → board ID via `agile board list --name "..."` first. ## Triggers - "list sprints on board 'Team Alpha'" - "add PROJ-123, PROJ-124 to sprint 42" - "set 5 story points on PROJ-123" - "rank PROJ-123 before PROJ-456 in backlog" - "velocity for board 42" - "create epic 'Auth Rewrite' in PROJ" ## Examples - Sprint create: "create sprint 'Sprint 21' on board 'Team Alpha' from 2026-05-13 to 2026-05-27" - Epic populate: "add PROJ-123, PROJ-124, PROJ-125 to epic EPIC-1" - Subtask: "create subtask of PROJ-123 — 'write integration test'" ## Sprint commitment hooks (Agile-context-only — gated by `agile-sprint-commitment.md` 2/3 when loaded) When `tasks/contracts/sprint-state-{date}-sprint-{N}.md` exists with `status: active`, wrap these operations: ### `sprint add KEY` and `sprint remove KEY` (post-start) 1. Read newest sprint-state file matching the active sprint 2. **Acquire `flock` on the sprint-state file before any read-modify-write.** YAML frontmatter append is non-atomic across shells; lock is the only mitigation 3. Per `agile-sprint-commitment.md` 2: `AskUserQuestion` "Reason for mid-sprint scope change?" — required free-text 4. Append `{ ts: <ISO ts>, action: add|remove, ticket: KEY, reason: <text> }` to `amendments:` list 5. Release lock 6. Proceed with the underlying `jira-as agile sprint add|remove` call If sprint-st