Skip to content

Expecho/Agent42 / .agentic/optional-skills/jira-implement

jira-implement

Unverified

Implement a Jira ticket end-to-end - read the ticket, clarify, plan via /plan, execute via /execute-plan, create the MR, and comment the MR link back on the ticket.

Implement a Jira ticket end-to-end

Slimmed from the workspace /jira-implement (493 → this). OPTIONAL: lives in .agentic/optional-skills/; onboarding copies it into .claude/skills/ only when the team works from Jira. Requires the Atlassian/Jira MCP server. Composition over duplication: planning and execution are delegated to /plan and /execute-plan — this skill only adds the ticket lifecycle around them.

Jira base URL: TODO e.g. https://yourorg.atlassian.net

Step 1 — Fetch & parse

jira_get_issue for the key (epics: also jira_get_epic_children). Extract the acceptance criteria verbatim — they seed the plan's AC→test mapping table. Transition the ticket to In Progress (resolve the transition ID first; never guess IDs).

Step 2 — Scope guardrails (stop and confirm with the user when any hit)

  • Story points > 8, or the change clearly spans multiple repos.
  • A bug with no reproduction path.
  • Auth/security-touching work.
  • Ambiguous or contradictory acceptance criteria.

Step 3 — Clarify, then plan

Mandatory interview (3–7 questions, max 2 rounds) about intent and scope — not about things the code answers. Then run /plan with the ticket content; name the spec plan-<issue-key>-<slug>.md. Iterate until the user explicitly approves. --plan-only stops here.

Step 4 — Execute & deliver

  • /execute-plan on the approved spec (branch: feature/<issue-key>-<slug>).
  • After the MR exists: jira_add_comment with the MR link and a 2–3 line summary.
  • Ticket transition after MR: TODO — e.g. "none: In Review happens on staging deploy" or "transition to In Review"
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 107kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 107kUpdated Claude CodeCodexVerifiedInstall