diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 21546863..8a20588a 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -48,7 +48,7 @@ { "name": "bitwarden-atlassian-tools", "source": "./plugins/bitwarden-atlassian-tools", - "version": "2.2.3", + "version": "2.3.0", "description": "Read-only Atlassian access via MCP server with deep Jira issue research skill, JQL search, Confluence pages, CQL search, and attachments" }, { diff --git a/README.md b/README.md index 0ce8d35b..0fc3bb86 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ A curated collection of plugins for AI-assisted development at Bitwarden. Enable | ------------------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------- | | [bitwarden-tech-lead](plugins/bitwarden-tech-lead/) | 2.1.1 | Tech lead for technical planning, architecture coherence, and surfacing patterns to Technical Strategy Ideas | | [bitwarden-shepherd](plugins/bitwarden-shepherd/) | 1.0.0 | Champion of a technical strategy — shepherds a TSI through evaluation into the funnel, then through to adoption | -| [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/) | 2.2.3 | Read-only Atlassian access via MCP server with deep Jira issue research skill | +| [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/) | 2.3.0 | Read-only Atlassian access via MCP server with deep Jira issue research skill | | [bitwarden-code-review](plugins/bitwarden-code-review/) | 1.11.0 | Autonomous code review agent following Bitwarden engineering standards with GitHub integration | | [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/) | 1.1.0 | Delivery lifecycle skills: initiative funnel navigation, work transitions, commits, PRs, preflight checks, labeling | | [bitwarden-devops-engineer](plugins/bitwarden-devops-engineer/) | 0.1.3 | DevOps engineering assistant: workflow compliance linting, action security auditing, and org-wide CI/CD remediation | diff --git a/plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json b/plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json index 0cdb9774..81a26267 100644 --- a/plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json +++ b/plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "bitwarden-atlassian-tools", - "version": "2.2.3", + "version": "2.3.0", "description": "Read-only Atlassian access via MCP server with deep Jira issue research skill, JQL search, Confluence pages, CQL search, and attachments", "author": { "name": "Bitwarden" diff --git a/plugins/bitwarden-atlassian-tools/CHANGELOG.md b/plugins/bitwarden-atlassian-tools/CHANGELOG.md index 7b64c508..2b3704b5 100644 --- a/plugins/bitwarden-atlassian-tools/CHANGELOG.md +++ b/plugins/bitwarden-atlassian-tools/CHANGELOG.md @@ -5,6 +5,12 @@ All notable changes to the Bitwarden Atlassian Tools plugin will be documented i The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [2.3.0] - 2026-05-19 + +### Changed + +- Expand `researching-jira-issues` skill extraction targets to include Tech Breakdown sections, bug reproduction steps, and divergences between supporting documentation and the ticket's specification of work + ## [2.2.3] - 2026-04-15 ### Changed diff --git a/plugins/bitwarden-atlassian-tools/skills/researching-jira-issues/SKILL.md b/plugins/bitwarden-atlassian-tools/skills/researching-jira-issues/SKILL.md index 3a834152..83e4a5e7 100644 --- a/plugins/bitwarden-atlassian-tools/skills/researching-jira-issues/SKILL.md +++ b/plugins/bitwarden-atlassian-tools/skills/researching-jira-issues/SKILL.md @@ -1,6 +1,6 @@ --- name: researching-jira-issues -description: Use whenever the user mentions a Jira issue key and wants more than a surface-level lookup — "Read PROJ-123", "What's PROJ-123 about?", "Give me context on PROJ-123", "Deep dive PROJ-123", "What's blocking PROJ-123?", "Summarize PROJ-123 and its dependencies", "I need to work on PROJ-123, what should I know?", or any request to understand an issue's purpose, scope, or requirements. Thoroughly researches and synthesizes a Jira issue including all linked issues, sub-tasks, blocked dependencies, and supporting Confluence documentation. +description: This skill should be used when the user mentions a Jira issue key and wants more than a surface-level lookup — "Read PROJ-123", "What's PROJ-123 about?", "Give me context on PROJ-123", "Deep dive PROJ-123", "What's blocking PROJ-123?", "Summarize PROJ-123 and its dependencies", "I need to work on PROJ-123, what should I know?", or any request to understand an issue's purpose, scope, or requirements. Thoroughly researches and synthesizes a Jira issue including all linked issues, sub-tasks, blocked dependencies, and supporting Confluence documentation. --- # Researching Jira Issues @@ -20,6 +20,7 @@ Extract and note: - Current status and priority - Assignee and reporter - Key fields relevant to understanding the work (labels, components, sprint, etc.) +- Tech Breakdown (custom field, when present — the technical implementation plan written and refined by the team) - Comments that provide important context (clarifications from stakeholders, technical decisions, implementation guidance) - **Custom fields**: Surface all non-null custom fields from the Additional Fields section of the response. The `names` expansion maps field IDs to human-readable display names automatically. @@ -128,6 +129,7 @@ Organize all gathered information into a comprehensive understanding: - Technical decisions or constraints from comments/documentation - Risks or concerns mentioned - Important historical context (why was this cloned, what was superseded, etc.) +- Divergences between supporting documentation and the specification of work in the ticket ### Context Budget