implement

Implement a Jira Ticket

Fetch a Jira ticket, check for an existing plan, set up a branch, and implement with lint+test verification before committing.

Announce at start: "Implementing : "

Checklist

1. Fetch ticket — get Jira ticket details and any existing plan
2. Assess readiness — is this ready to implement, or does it need /plan first?
3. Set up branch — create worktree or branch
4. Read project conventions — CLAUDE.md, learnings, relevant package docs
5. Implement — follow the plan or work from the ticket description
6. Verify — make lint && make test (or project equivalent)
7. Commit — conventional commit referencing the ticket
8. Report — summary with next steps (PR creation)

Jira Authentication

Before any Jira call, test connectivity by calling getAccessibleAtlassianResources(). If it fails or returns an auth error, stop and prompt the user:

"Jira is not authenticated. Please run /plugin and authenticate the Atlassian plugin, then try again."

Do not proceed with Jira operations until auth is confirmed.

Phase 1: Fetch Ticket

Extract the ticket key from the argument (e.g., IN-945 from /implement IN-945 or from a URL).

1a. Get Jira details (also serves as auth check):

getAccessibleAtlassianResources() -> cloudId  (if this fails, follow Jira Authentication section)
getJiraIssue(cloudId, issueKey, fields=["summary","description","priority","labels","status","parent"], responseContentFormat="markdown")

1b. Check for existing local plan (parallel):

ls docs/plans/<ticket-key>-*.md 2>/dev/null

If a plan file exists, read it — this is the primary implementation guide.

If no plan file exists, use the ticket description's Approach section as the guide.

Phase 2: Assess Readiness

Check if the ticket has enough detail to implement:

• Ready: Has clear What/Why/Approach or an existing plan file -> proceed
• Needs planning: Description is vague, scope is unclear, or estimate was XL -> recommend /plan <ticket-key> first