Skip to content

Update Jira skill to consider gaps in requirements #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
trmartin4 wants to merge 4 commits into
base: main
Choose a base branch
from
+12 −4
Open

Update Jira skill to consider gaps in requirements #123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c6ee81b
Suggestions for improved Jira skill
trmartin4 May 19, 2026
e268e0c
Updated version based on review feedback.
trmartin4 May 19, 2026
b6bef43
Format
trmartin4 May 19, 2026
e561f1e
Removed local config.
trmartin4 May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
},
{
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand Down
2 changes: 1 addition & 1 deletion plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
Expand Down
6 changes: 6 additions & 0 deletions plugins/bitwarden-atlassian-tools/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 3 additions & 1 deletion plugins/bitwarden-atlassian-tools/skills/researching-jira-issues/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.

@SaintPatrck SaintPatrck May 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ This change seems out of place. Is it intentional?

---

# Researching Jira Issues
Expand All @@ -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.

Expand Down Expand Up @@ -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

Expand Down
Loading