mkjira-opslisted

# mk:jira-ops Forks to the `jira-ops` agent. Diagnostic surface only. ## Triggers - "jira cache status" - "clear jira cache" - "discover project context for PROJ" ## Examples - Cache check: "is the jira-as cache fresh?" - Cache clear: "clear the cache, my admin renamed a status" - Discovery: "what's the default issue type and mandatory field set for PROJ?" ## Power-User Note `cache-warm` is intentionally NOT exposed as a primary trigger. If a user explicitly needs it, they can invoke directly: ```bash bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh ops cache-warm --project PROJ ``` ## See also - Agent: `../../agents/jira-ops.md` - Shared: `../jira/references/{install-and-auth,cli-idioms,safety-framework}.md` - Domain refs: - `references/rate-limits.md` — Atlassian rate-limit ceilings + back-off behaviour - Peer leaves: any leaf hitting Atlassian-side throttling first lands here for diagnosis. `mk:jira-bulk` is the most common trigger for cache-warm + rate-limit awareness. ## Gotchas - (none yet)