qa-defect-management
Defect management discipline (taxonomy, lifecycle, workflows): 3 reference skills (bug-lifecycle-reference, severity-vs-priority-reference, defect-taxonomy-istqb) + 4 platform-workflow skills (jira-bug-workflow-runner, linear-bug-workflow-runner, github-issues-bug-workflow, azuredevops-bug-workflow) + 1 build skill (bug-report-from-failure) + 4 agents (duplicate-defect-finder, bug-report-critic, ci-defect-filer, defect-fix-verifier). Distinct from qa-bug-repro which covers reproduction + clustering + trend narration; this covers triage workflow + taxonomy + severity classification, and closes the lifecycle with post-fix confirmation testing.
Install this plugin
/plugin install qa-defect-management@testland-qaPart of role bundles: qa-starter, qa-role-manual-tester, qa-role-leadership
qa-defect-management
Defect management discipline (taxonomy, lifecycle, workflows): 3 reference skills (bug-lifecycle-reference, severity-vs-priority-reference, defect-taxonomy-istqb) + 4 platform-workflow skills (jira-bug-workflow-runner, linear-bug-workflow-runner, github-issues-bug-workflow, azuredevops-bug-workflow) + 1 build skill (bug-report-from-failure) + 4 agents (duplicate-defect-finder, bug-report-critic, ci-defect-filer, defect-fix-verifier). Distinct from qa-bug-repro which covers reproduction + clustering + trend narration; this covers triage workflow + taxonomy + severity classification, and closes the lifecycle with post-fix confirmation testing.
Components
| Type | Name | Description |
|---|---|---|
| skill | bug-lifecycle-reference | ISTQB-canonical defect lifecycle states + tracker-vocabulary map for Jira/Linear/GitHub |
| skill | severity-vs-priority-reference | Two-axis defect classification; 5×5 matrix with worked examples |
| skill | defect-taxonomy-istqb | IEEE 1044-2009 + CTAL-TA + Chillarege ODC taxonomies |
| skill | jira-bug-workflow-runner | Jira Cloud REST API v3 create/transition/JQL search |
| skill | linear-bug-workflow-runner | Linear GraphQL issueCreate / issueUpdate / workflowStates |
| skill | github-issues-bug-workflow | GitHub Issues REST API v2022-11-28 + Projects v2 |
| skill | bug-report-from-failure | Turn JUnit/Allure/pytest failure records into tracker-agnostic bug specs |
| agent | duplicate-defect-finder | Search the tracker for likely duplicates; rank candidates by similarity |
| agent | bug-report-critic | Audit a bug report against required fields, severity-priority independence, reproduction quality |
| Agent | ci-defect-filer | One-step CI auto-filer: turns a test failure into a deduped bug filed in Jira / Linear / GitHub Issues. |
| Skill | azuredevops-bug-workflow | Author/triage/link bugs in Azure DevOps Boards via the Work Item Tracking REST API + WIQL. |
| Agent | defect-fix-verifier | Confirmation testing: re-runs a defect's reproduction after the fix merges, verdicts VERIFIED / NOT FIXED / BLOCKED, and transitions the tracker with evidence. |
Differentiation
This plugin scopes defect lifecycle + taxonomy + tracker workflow. Sibling neighbours:
Install
/plugin marketplace add testland/qa
/plugin install qa-defect-management@testland-qaSkills
azuredevops-bug-workflow
Authors and triages Bug work items in Azure DevOps Boards via the Work Item Tracking REST API (api-version 7.1) - Bug creation with JSON Patch, state transitions across New/Active/Resolved/Closed, WIQL queries for triage queues and duplicate detection, linking to PRs and builds via System.LinkTypes.Related and ArtifactLink relations, and the az boards CLI for scripted workflows. Use when programmatically managing Azure DevOps Bug lifecycle states: creating from CI failures, triaging open defect queues, transitioning states in bulk, or attaching traceability links to builds and pull requests.
bug-lifecycle-reference
Pure-reference catalog of defect lifecycle states and transitions. Defines the ISTQB-canonical states (new / open / assigned / in-progress / fixed / verified / closed / reopened / deferred / rejected / duplicate) and the transitions between them, distinguishes the ISTQB terms (error → fault / defect → failure), maps the lifecycle to the standard Jira / Linear / GitHub Issues workflows, and cites IEEE 1044-2009 and ISO/IEC/IEEE 29119-3 for the canonical anchors. Use as the lifecycle vocabulary for the bug-report-critic, duplicate-defect-finder, and the platform-workflow skills.
bug-report-from-failure
On-demand builder that converts a SINGLE test failure record (JUnit XML, Allure JSON, pytest --tb=short, Playwright HTML, Cypress mocha-junit) into a structured, tracker-agnostic bug SPEC: extracts test name, assertion, stack trace, environment, and artefacts, and proposes severity, defect type (IEEE 1044), and a root-cause hypothesis (ISTQB CTAL-TA), then hands the JSON spec to a jira/linear/github-issues-bug-workflow runner to file. Use when you already hold a failure artefact and want one classified, ready-to-file report. Distinct from ci-defect-filer (the event-driven CI orchestrator that triggers automatically on a pipeline failure and files in bulk) and from qa-bug-repro/bug-report-from-recording (screen-recording-driven); this is the on-demand, single-record spec builder.
defect-taxonomy-istqb
Pure-reference catalog of defect categorisation taxonomies. Covers the IEEE 1044-2009 anomaly classification (anomaly class, anomaly type, anomaly severity, root cause category), the ISTQB CTAL-TA root-cause taxonomy (requirements / design / implementation / interface / test-data / build-environment), and the Orthogonal Defect Classification (ODC) eight-attribute framework. Maps each taxonomy to a worked example showing how the same defect classifies under each. Use to categorise defects consistently across a team, drive root-cause analysis, and inform process-improvement decisions (where in the SDLC do we leak the most defects?).
github-issues-bug-workflow
Author and run GitHub Issues bug workflows via REST API v2022-11-28 - issue creation, state changes (open / closed with state_reason), label-based severity/priority classification, comment attachment, and Projects v2 status-column updates via GraphQL. Covers POST /repos/{owner}/{repo}/issues, PATCH for state_reason transitions (completed / not_planned / duplicate / reopened), label conventions for the impoverished GitHub state model, and the gh CLI for scripted workflows. Use when programmatically managing GitHub Issues bug lifecycle - GitHub's binary open/closed model requires label + Projects discipline.
jira-bug-workflow-runner
Jira Cloud bug workflow runner using the REST API v3: issue creation with an ADF description, runtime transition lookup and apply, JQL search for triage queues and duplicate detection, severity/priority field updates, label-based classification (severity/priority/regression), and idempotent CI-driven filing from JUnit XML test failures. Use when the target tracker is Jira Cloud and the task involves Jira lifecycle states (create, triage, transition, close). Distinct from ci-defect-filer, the platform-agnostic event-driven CI orchestrator, and from linear-bug-workflow-runner / github-issues-bug-workflow for other trackers.
linear-bug-workflow-runner
Author and run Linear bug workflows via the GraphQL API: issue creation, state transitions (workflowState assignment), priority assignment (0 No priority / 1 Urgent / 2 High / 3 Medium / 4 Low), label-based classification, search by team and content. Covers the issueCreate mutation, issueUpdate for state transitions, the workflowStates query for per-team state IDs, and Linear's API-key vs OAuth Bearer auth modes. Use when the target tracker is Linear specifically; for tool-agnostic CI gates name the tracker, and for other trackers use jira-bug-workflow-runner (Jira) or github-issues-bug-workflow (GitHub Issues). Distinct from qa-bug-repro, which is reproduction-focused.
severity-vs-priority-reference
Pure-reference catalog distinguishing defect severity (impact on the system / user) from defect priority (urgency of fix), each on its own axis. Enumerates the canonical 5-point severity scale (Critical / High / Medium / Low / Trivial) and the 5-point priority scale (Immediate / High / Medium / Low / Deferred), explains why they must be tracked separately (a Critical/Deferred legacy bug exists; a Trivial/Immediate spelling bug on the homepage exists), maps to IEEE 1044-2009 severity classes, and ties to bug-lifecycle-reference state transitions. Use when triaging a defect, configuring a tracker's severity/priority fields, or reviewing whether a bug report assigned them consistently.
Agents
bug-report-critic
Adversarial agent that audits a bug report (filed or proposed) against the catalog's quality bar. Verifies: required fields present (title / severity / priority / lifecycle state / reproduction / environment / classification), severity matches the report's described impact (not over- or under-stated), severity vs priority both set and independently justified, defect-taxonomy fields populated (IEEE 1044 type, ISTQB CTAL-TA root cause hypothesis), and the report passes the single-description test. Rejects reports missing reproduction steps, conflating severity with priority, or skipping classification. Use before opening any tracker as part of triage gate.
ci-defect-filer
Action-taking orchestrator that converts a CI test failure artifact (JUnit XML, Allure JSON, pytest --tb=short log, Playwright HTML report) into a deduped, filed bug in the team's active tracker (Jira / Linear / GitHub Issues). Orchestrates three preloaded skills in sequence: bug-report-from-failure builds the structured spec, duplicate-defect-finder searches the tracker, then the matching platform runner creates or comments. Distinct from duplicate-defect-finder (read-only; emits a candidate list) and from bug-report-from-failure (produces a spec without filing). Use when a CI pipeline step fails and the team wants a bug ticket filed automatically, with deduplication, in a single unattended run.
defect-fix-verifier
Confirmation-testing agent that re-runs a defect's reproduction after the fix is claimed merged and issues a VERIFIED / NOT FIXED / BLOCKED verdict with evidence (ISTQB confirmation testing, synonym retesting). Locates the merged fix commit, confirms the build under test contains it, re-executes the linked repro test (or emits a manual re-verification script), then transitions the tracker (Jira / Linear / GitHub Issues / Azure DevOps) to Verified or Reopened with an evidence comment. Distinct from qa-bug-repro/bug-repro-builder (creates the failing repro BEFORE the fix; this agent re-runs it AFTER) and qa-bug-repro/test-failure-debugger (diagnoses why a test fails; this agent confirms a claimed fix resolved a known defect). Use when a developer marks a defect Fixed and the team needs the Fixed -> Verified or Fixed -> Reopened transition backed by re-run evidence.
duplicate-defect-finder
Read-only agent that searches the bug tracker for likely duplicates of a candidate defect before it gets filed. Combines (1) exact title-substring search, (2) test-name search across last 90 days, (3) stack-fingerprint fuzzy match (top-frame normalisation, error-class match), and (4) Allure feature/suite tag overlap. Emits a ranked list of candidates with similarity scores so a triager can choose: file new, attach comment to existing, or mark as duplicate of canonical. Use before filing any bug auto-generated from CI failures or recurring test flakes.