How do I install the Lisa Jira Claim skill?

Run npx skillmds@latest add codyswanngt/lisa-jira-claim in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lisa Jira Claim safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lisa Jira Claim?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lisa Jira Claim free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lisa Jira Claim?

codyswanngt (@codyswanngt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lisa Jira Claim by codyswanngt — Agent Skill

Name: Lisa Jira Claim
Author: codyswanngt

Lisa Jira Claim

Idempotently claims one live Jira leaf ticket for direct Lisa work. Reuses jira-build-intake Phase 3b semantics through lisa-atlassian-access: configured ready-to-claimed transition, assign-only-if-unassigned, stable managed comment, and post-write verification.

codyswanngt Updated Sep 17, 2026

File contents

Claim Jira Ticket: $ARGUMENTS

Claim exactly one canonical Jira key. All Jira access goes through lisa-atlassian-access; do not call MCP tools or acli directly. This is the reusable direct-session counterpart of lisa-jira-build-intake Phase 3b.

Resolve merged atlassian.cloudId, jira.project, and jira.workflow values from local-over-global config. Require the key's project prefix to equal the configured Jira project. Resolve ready, claimed, review, environment, and terminal roles from config; do not hardcode status decisions.
Invoke lisa-jira-read-ticket <key> immediately before mutation. Reject a resolved/terminal ticket, active blocker, repo:<other> ticket, any item with open children/subtasks, or an Epic per repo-scope-split and leaf-only-lifecycle.
Inspect the live workflow role:
- Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set claim_outcome: reused.
- Ready or an unlaned backlog leaf -> invoke lisa-atlassian-access operation: transition key: <key> to: <configured-claimed> and require success. This is the idempotency lock.
- Terminal/resolved -> reject; never regress completed work.
If and only if the ticket is unassigned, assign it to the authenticated account through lisa-atlassian-access (prefer the identity-probed account id / @me semantics documented by Jira build intake). Leave an existing assignee untouched.
Post this stable comment once through lisa-atlassian-access operation: comment, deduped against all existing comments:
```
[lisa-tracker-claim] Claimed by Lisa. Starting implementation.
```
Invoke lisa-jira-read-ticket <key> again. Success requires an unresolved, current-repo leaf in claimed or a later non-terminal role. An unreachable transition or failed verification is a hard failure and must not authorize a binding.
Return tracker_provider: jira, canonical work_item_ref: <KEY>, claim_outcome: claimed|reused, assignee outcome, and the post-write status evidence.

Never create a ticket here. Never bypass lisa-atlassian-access.

---name: lisa-jira-claimdescription: Idempotently claims one live Jira leaf ticket for direct Lisa work. Reuses jira-build-intake Phase 3b semantics through lisa-atlassian-access: configured ready-to-claimed transition, assign-only-if-unassigned, stable managed comment, and post-write verification.---# Claim Jira Ticket: $ARGUMENTSClaim exactly one canonical Jira key. All Jira access goes through `lisa-atlassian-access`; do not call MCP tools or `acli` directly. This is the reusable direct-session counterpart of `lisa-jira-build-intake` Phase 3b.1. Resolve merged `atlassian.cloudId`, `jira.project`, and `jira.workflow` values from local-over-global config. Require the key's project prefix to equal the configured Jira project. Resolve ready, claimed, review, environment, and terminal roles from config; do not hardcode status decisions.2. Invoke `lisa-jira-read-ticket <key>` immediately before mutation. Reject a resolved/terminal ticket, active blocker, `repo:<other>` ticket, any item with open children/subtasks, or an Epic per `repo-scope-split` and `leaf-only-lifecycle`.3. Inspect the live workflow role: - Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set `claim_outcome: reused`. - Ready or an unlaned backlog leaf -> invoke `lisa-atlassian-access operation: transition key: <key> to: <configured-claimed>` and require success. This is the idempotency lock. - Terminal/resolved -> reject; never regress completed work.4. If and only if the ticket is unassigned, assign it to the authenticated account through `lisa-atlassian-access` (prefer the identity-probed account id / `@me` semantics documented by Jira build intake). Leave an existing assignee untouched.5. Post this stable comment once through `lisa-atlassian-access operation: comment`, deduped against all existing comments: ```text [lisa-tracker-claim] Claimed by Lisa. Starting implementation. ```6. Invoke `lisa-jira-read-ticket <key>` again. Success requires an unresolved, current-repo leaf in claimed or a later non-terminal role. An unreachable transition or failed verification is a hard failure and must not authorize a binding.7. Return `tracker_provider: jira`, canonical `work_item_ref: <KEY>`, `claim_outcome: claimed|reused`, assignee outcome, and the post-write status evidence.Never create a ticket here. Never bypass `lisa-atlassian-access`.

Frequently asked questions