atlassian-toolkit

Plugin atlassian-toolkit from marketplace jumptothecloud-code-marketplace in JumpToTheCloud/claude-code. Commands read from the repo's manifest — 12 days ago.

Skills (13)

• confluence-create-component

  Bootstrap the Confluence side of a new component in the space JTTC - the component page under Components and its five children (Overview, PRDs, Decisions, Design, Runbooks), with the Overview summary table filled. The Jira Component must already exist: the skill checks it and refuses when it does no

• confluence-create-doc

  Create a document page in the Confluence space JTTC - a PRD, a Technical Plan, a Consistency Analysis, an ADR or a Runbook - from the template kept in this skill. Finds the right parent, builds the title from the naming pattern, checks that the title is unique, fills the summary table (with the stat

• confluence-sync-templates

  Maintenance skill. Regenerates the read-only Confluence mirrors of what the atlassian-toolkit plugin keeps as source of truth - the issue templates (Epic, Story, Task, Bug, Sub-task), the document templates (PRD, Technical Plan, Consistency Analysis, ADR, Runbook), the Component Template tree, the D

• confluence-update-doc

  Change an existing document page in the Confluence space JTTC - set rows of its summary table, replace a section, change its status (the status lozenge in the summary table: DRAFT, IN REVIEW, APPROVED, SUPERSEDED, or PROPOSED, ACCEPTED for an ADR), retire it (SUPERSEDED, pointer to the replacement,

• jira-create-bug

  Create one or more Bugs in the Jira project JTTC from a structured input (summary, environment, affects version, steps to reproduce, expected vs actual, impact and severity, component). Fills the Bug template, blocks creation when reproduction or impact is missing, leaves root cause and acceptance c

• jira-create-epic

  Create one or more Epics in the Jira project JTTC from a structured input (summary, expected outcome, out of scope, success criteria, component, PRD link). Fills the Epic template, blocks creation when a required field is missing, links the PRD and related ADRs as remote links, skips duplicates and

• jira-create-story

  Create one or more Stories in the Jira project JTTC from a structured input (summary, user story, source, out of scope, initial acceptance criteria, component, parent Epic). Fills the Story template, blocks creation when an entry-level field is missing, leaves the refinement sections marked `Pending

• jira-create-subtask

  Create one or more sub-tasks in the Jira project JTTC under a Story, Task or Bug, as one of five types - Development, Automation, Analysis, Architecture Design, Documentation. Each sub-task is self-contained (goal, context, exact files, steps, acceptance criteria covered, tests, estimate in hours up

• jira-create-task

  Create one or more Tasks in the Jira project JTTC - technical work with no user story - from a structured input (summary, outcome, done-when, component, parent Epic, source). Fills the Task template, blocks creation when an entry-level field is missing, leaves refinement sections marked `Pending ref

• jira-link-issues

  Create links on Jira issues in the JTTC project - blocks / is blocked by between issues (with a cycle check), relates, and remote links to Confluence pages or URLs (a PRD or ADR on an Epic, a pull request on a Story). Skips links that already exist, rejects a batch that would create a dependency cyc

• jira-transition-issue

  Move issues of the Jira project JTTC to another status and enforce the Definition of Ready and Definition of Done at the gates - Gate 1 (In refinement to Refined), Gate 2 (Refined to Ready, or Backlog to Ready for a small Task), the Definition of Done (In Review to Done) - using the criteria kept in

• jira-update-issue

  Update an existing Jira issue in the JTTC project - set Story Points, Size, Business Value, Risk, Mode, Priority, labels (including tdd), the Flagged marker, the original estimate of a sub-task, fill or replace sections of the description (removing the `Pending refinement` marker), and add a comment

• jttc-workspace

  Reference map of the Jump to the Cloud (JTTC) workspace in Atlassian - the Jira project JTTC (workflow, statuses, issue types, custom fields, boards, components) and the Confluence space JTTC (page tree, templates, Definition of Ready, Definition of Done, naming, labels), with the IDs needed to read

Subagents (1)

• atlassian-operator

  Use this agent to write to Jira and Confluence in the Jump to the Cloud workspace without filling the main session with API noise - creating Epics, Stories, Tasks, Bugs and sub-tasks, linking them, updating fields and description sections, and moving them through the workflow with the Definition of

MCP servers (1)

• atlassian

  connects to: https://mcp.atlassian.com/v2/mcp

Hooks (2)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/approve-read-only.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/approve-agent-writes.sh

Similar plugins