creating qa skill based on retro feedback

.claude-plugin/marketplace.json

@@ -48,7 +48,7 @@
     {
       "name": "bitwarden-atlassian-tools",
       "source": "./plugins/bitwarden-atlassian-tools",
-      "version": "2.6.0",
+      "version": "2.7.1",
       "description": "Atlassian access via MCP server with deep Jira issue research skill, JQL search, Confluence pages, CQL search, attachments, and opt-in Jira write tools"
     },
     {

.cspell.json

@@ -116,6 +116,7 @@
     "pyproject",
     "pytest",
     "remotelink",
+    "reprompt",
     "Rescope",
     "resolutiondate",
     "retarget",

README.md

@@ -4,24 +4,32 @@ A curated collection of plugins for AI-assisted development at Bitwarden. Enable
 
 ## Available Plugins
 
-| Plugin                                                              | Version | Description                                                                                                                                                 |
-| ------------------------------------------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [bitwarden-ai-telemetry](plugins/bitwarden-ai-telemetry/)           | 1.1.0   | Claude Code hooks emitting metadata-only AI-usage telemetry (identity, git-linkage, MCP) via OTLP                                                           |
-| [bitwarden-tech-lead](plugins/bitwarden-tech-lead/)                 | 3.0.1   | Tech lead for technical planning, architecture coherence, and surfacing patterns to Technical Strategy Ideas                                                |
-| [bitwarden-shepherd](plugins/bitwarden-shepherd/)                   | 1.0.1   | 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.6.0   | Atlassian access via MCP server with deep Jira issue research skill and opt-in Jira write tools                                                             |
-| [bitwarden-code-review](plugins/bitwarden-code-review/)             | 1.14.0  | Autonomous code review agent following Bitwarden engineering standards with GitHub integration                                                              |
-| [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/)       | 3.1.0   | Delivery lifecycle skills: initiative funnel navigation, work transitions, architectural judgment, commits, PRs, preflight, labeling, Jira ticket filing    |
-| [bitwarden-designer](plugins/bitwarden-designer/)                   | 0.1.0   | Product designer persona: Code of Conduct and 30/60/90 critique, critique facilitation; dispatches into bitwarden-design-tools                              |
-| [bitwarden-design-tools](plugins/bitwarden-design-tools/)           | 0.1.0   | Design toolkit: content style guide, Figma Dev Mode MCP, Bitwarden brand application, handoff prep, Design System governance, Product and Design Jira       |
-| [bitwarden-devops-engineer](plugins/bitwarden-devops-engineer/)     | 0.3.0   | DevOps engineering assistant: workflow compliance linting, action security auditing, and org-wide CI/CD remediation                                         |
-| [bitwarden-init](plugins/bitwarden-init/)                           | 1.2.2   | Initialize and enhance CLAUDE.md files with Bitwarden's standardized template format                                                                        |
-| [bitwarden-product-analyst](plugins/bitwarden-product-analyst/)     | 0.1.6   | Product analyst agent for creating comprehensive Bitwarden requirements documents from multiple sources, and writing user-facing release notes              |
-| [bitwarden-security-engineer](plugins/bitwarden-security-engineer/) | 1.3.0   | Application security engineering: vulnerability triage, threat modeling, and secure code analysis                                                           |
-| [bitwarden-software-engineer](plugins/bitwarden-software-engineer/) | 1.0.0   | Software engineer agent for a Bitwarden product team. Implements stories, tasks, and bugs with code quality, performance, security, and team comms in mind. |
-| [bitwarden-testing-tools](plugins/bitwarden-testing-tools/)         | 1.1.0   | Testing tools for analyzing and improving test quality across Bitwarden's repositories.                                                                     |
-| [claude-config-validator](plugins/claude-config-validator/)         | 2.0.2   | Validates Claude Code configuration files for security, structure, and quality                                                                              |
-| [claude-retrospective](plugins/claude-retrospective/)               | 1.1.1   | Analyze Claude Code sessions to identify successful patterns and improvement opportunities                                                                  |
+| Plugin                                                    | Version | Description                                                                                                     |
+| --------------------------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------- |
+| [bitwarden-ai-telemetry](plugins/bitwarden-ai-telemetry/) | 1.1.0   | Claude Code hooks emitting metadata-only AI-usage telemetry (identity, git-linkage, MCP) via OTLP               |
+| [bitwarden-tech-lead](plugins/bitwarden-tech-lead/)       | 3.0.1   | Tech lead for technical planning, architecture coherence, and surfacing patterns to Technical Strategy Ideas    |
+| [bitwarden-shepherd](plugins/bitwarden-shepherd/)         | 1.0.1   | Champion of a technical strategy — shepherds a TSI through evaluation into the funnel, then through to adoption |
+
+<<<<<<< HEAD
+| [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/) | 2.7.1 | Atlassian access via MCP server with deep Jira issue research skill and opt-in Jira write tools |
+| [bitwarden-code-review](plugins/bitwarden-code-review/) | 1.13.1 | Autonomous code review agent following Bitwarden engineering standards with GitHub integration |
+| [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/) | 3.0.0 | Delivery lifecycle skills: initiative funnel navigation, work transitions, architectural judgment, commits, PRs, preflight, labeling |
+=======
+| [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/) | 2.6.0 | Atlassian access via MCP server with deep Jira issue research skill and opt-in Jira write tools |
+| [bitwarden-code-review](plugins/bitwarden-code-review/) | 1.14.0 | Autonomous code review agent following Bitwarden engineering standards with GitHub integration |
+| [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/) | 3.1.0 | Delivery lifecycle skills: initiative funnel navigation, work transitions, architectural judgment, commits, PRs, preflight, labeling, Jira ticket filing |
+
+> > > > > > > main
+> > > > > > > | [bitwarden-designer](plugins/bitwarden-designer/) | 0.1.0 | Product designer persona: Code of Conduct and 30/60/90 critique, critique facilitation; dispatches into bitwarden-design-tools |
+> > > > > > > | [bitwarden-design-tools](plugins/bitwarden-design-tools/) | 0.1.0 | Design toolkit: content style guide, Figma Dev Mode MCP, Bitwarden brand application, handoff prep, Design System governance, Product and Design Jira |
+> > > > > > > | [bitwarden-devops-engineer](plugins/bitwarden-devops-engineer/) | 0.3.0 | DevOps engineering assistant: workflow compliance linting, action security auditing, and org-wide CI/CD remediation |
+> > > > > > > | [bitwarden-init](plugins/bitwarden-init/) | 1.2.2 | Initialize and enhance CLAUDE.md files with Bitwarden's standardized template format |
+> > > > > > > | [bitwarden-product-analyst](plugins/bitwarden-product-analyst/) | 0.1.6 | Product analyst agent for creating comprehensive Bitwarden requirements documents from multiple sources, and writing user-facing release notes |
+> > > > > > > | [bitwarden-security-engineer](plugins/bitwarden-security-engineer/) | 1.3.0 | Application security engineering: vulnerability triage, threat modeling, and secure code analysis |
+> > > > > > > | [bitwarden-software-engineer](plugins/bitwarden-software-engineer/) | 1.0.0 | Software engineer agent for a Bitwarden product team. Implements stories, tasks, and bugs with code quality, performance, security, and team comms in mind. |
+> > > > > > > | [bitwarden-testing-tools](plugins/bitwarden-testing-tools/) | 1.1.0 | Testing tools for analyzing and improving test quality across Bitwarden's repositories. |
+> > > > > > > | [claude-config-validator](plugins/claude-config-validator/) | 2.0.2 | Validates Claude Code configuration files for security, structure, and quality |
+> > > > > > > | [claude-retrospective](plugins/claude-retrospective/) | 1.1.1 | Analyze Claude Code sessions to identify successful patterns and improvement opportunities |
 
 ## Usage
 

plugins/bitwarden-atlassian-tools/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "bitwarden-atlassian-tools",
-  "version": "2.6.0",
+  "version": "2.7.1",
   "description": "Atlassian access via MCP server with deep Jira issue research skill, JQL search, Confluence pages, CQL search, attachments, and opt-in Jira write tools",
   "author": {
     "name": "Bitwarden"

plugins/bitwarden-atlassian-tools/CHANGELOG.md

@@ -5,6 +5,21 @@ 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.7.1] - 2026-08-26
+
+### Fixed
+
+- `evaluating-qa-readiness` no longer reports "no PR or build is linked" as a settled fact. `get_issue_remote_links` cannot see Jira's native Development panel (the GitHub/Bitbucket integration that links most PRs via smart commits or branch naming), so an empty result is now reported as "not found in the sources this check can search" with a pointer to check the Development panel manually, instead of a confident negative.
+- `evaluating-qa-readiness`'s feature-flag criterion and developer-ask draft no longer demand an explicit on/off state when only one flag is named — "enable to test" is now the assumed default unless the ticket gives a real reason the state is ambiguous.
+- `evaluating-qa-readiness`'s drafted developer ask now names the gap without dictating exhaustive step-by-step detail (exact queries, seed data, timing) that a competent tester doesn't need.
+- README's `## Usage` examples used the unscoped `mcp__bitwarden-atlassian__<tool_name>` prefix; corrected to the plugin-scoped `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__<tool_name>` form that Claude Code actually resolves.
+
+## [2.7.0] - 2026-08-06
+
+### Added
+
+- Added the `evaluating-qa-readiness` skill, which checks a Jira ticket for the information QA needs before testing (testing instructions, implementation notes, feature-flag state, acceptance criteria, affected clients, and a linked PR/build) via the read-only Atlassian MCP and drafts a ready-to-paste developer comment for any gaps
+
 ## [2.6.0] - 2026-08-04
 
 ### Added

plugins/bitwarden-atlassian-tools/README.md

@@ -140,13 +140,13 @@ A leaked write token permits more than these two tools use: `write:comment:jira`
 
 ## Usage
 
-The MCP tools are available as `mcp__bitwarden-atlassian__<tool_name>`. Examples:
+The MCP tools are available as `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__<tool_name>`. Examples:
 
-- Read an issue: `mcp__bitwarden-atlassian__get_issue` with `issueIdOrKey: "PROJ-123"`
-- Search with JQL: `mcp__bitwarden-atlassian__search_issues` with `jql: "project = PROJ AND status = Open"`
-- Read a Confluence page: `mcp__bitwarden-atlassian__get_confluence_page` with `pageId: "123456789"`
-- Search Confluence: `mcp__bitwarden-atlassian__search_confluence_cql` with `cql: "space = EN AND text ~ \"search term\""`
-- Preview a ticket before creating it: `mcp__bitwarden-atlassian__create_issue` with `project: "PM"`, `issueType: "Story"`, `summary: "Add CSV export to the item list"` — omit `dryRun` (defaults to `true`) to get the payload back without creating anything
+- Read an issue: `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue` with `issueIdOrKey: "PROJ-123"`
+- Search with JQL: `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__search_issues` with `jql: "project = PROJ AND status = Open"`
+- Read a Confluence page: `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page` with `pageId: "123456789"`
+- Search Confluence: `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__search_confluence_cql` with `cql: "space = EN AND text ~ \"search term\""`
+- Preview a ticket before creating it: `mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__create_issue` with `project: "PM"`, `issueType: "Story"`, `summary: "Add CSV export to the item list"` — omit `dryRun` (defaults to `true`) to get the payload back without creating anything
 
 ## Skills
 
@@ -175,6 +175,28 @@ Features:
 
 Live creation requires `ATLASSIAN_JIRA_WRITE_TOKEN`; without it the skill can still draft and preview.
 
+### `assessing-jira-issue-relevance`
+
+Determines whether a Jira issue still applies to the current codebase by fetching the ticket, locating the code path it describes, and comparing current behavior against the ticket's description. Triggered by questions about whether a ticket is still relevant (e.g., "Is PM-123 still pending?", "Has this been fixed?", "Can we close this?").
+
+Features:
+
+- Fetches ticket, comments, and remote links as evidence, then verifies against the current codebase rather than trusting ticket status
+- Returns a verdict (still applicable / fixed / stale) backed by cited evidence
+- Assesses one ticket at a time; invoke iteratively for multiple tickets
+
+### `evaluating-qa-readiness`
+
+Checks a Jira ticket for the concrete, objectively-verifiable information QA needs before testing starts — testing instructions, implementation notes, feature-flag state, acceptance criteria, affected clients, and a linked PR/build — then drafts a developer comment for any gaps. Triggered by requests to check QA readiness (e.g., "Is PROJ-123 ready for QA?", "QA-check PROJ-123") or proactively when a ticket is being moved to Ready for QA.
+
+Features:
+
+- Reads description, custom fields, comments, and remote links as evidence, since developers often drop testing notes or flag names in a comment rather than the description
+- Distinguishes blocking gaps (testing instructions, implementation notes, feature flag) from non-blocking ones (acceptance criteria, affected clients, linked PR/build) so the verdict reflects how stuck a tester actually is
+- Drafts a targeted, collegial ask addressing only the gaps found
+
+This skill is read-only: it drafts the developer comment but cannot post it to the ticket.
+
 ## Requirements
 
 - Claude Code with MCP support