メニュー
[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | qa-defect |
| description | [QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics. |
| argument-hint | triage VCST-XXXX | verify VCST-XXXX | classify | workflow | metrics |
| disable-model-invocation | true |
Manages the full defect lifecycle from detection through triage, classification, fix verification, and closure. Provides the JIRA Bug Workflow (16 statuses), triage routing, report validation, verification protocol, and defect process health metrics.
/qa-defect # Full lifecycle overview + JIRA workflow map
/qa-defect triage VCST-1234 # Triage a bug: validate report, check duplicates, classify, assign
/qa-defect verify VCST-1234 # Verify a fix: re-run STR, check regression, transition JIRA
/qa-defect classify # Show defect type taxonomy + root cause categories
/qa-defect workflow # Show JIRA Bug Workflow (16 statuses, all transitions)
/qa-defect metrics # Defect process health: aging, MTTR, reopen rate, escape rate
defect-lifecycle-workflow.md from this skill folder.triage VCST-XXXX → triage workflowverify VCST-XXXX → fix verification protocolclassify → defect type taxonomy + root cause categoriesworkflow → JIRA Bug Workflow diagram + transition tablemetrics → defect process health indicatorsgetJiraIssue / ado.mjs get-workitem, per profile) → validate report completeness (12-item checklist) → check for duplicates (tracker-ops §2 Search — Jira JQL summary ~ "keyword" AND status != Cancelled, Azure WIQL equivalent) → classify defect type + root cause → assess severity + priority (reference /qa-risk) → route to owner via triage matrix → set fields + recommend the destination role (§0 role table), transitioned via tracker-ops.tested then done; any fail → transition role reopen with new evidence. All transitions resolve the live workflow via tracker-ops (§0 roles), honoring tracker.azure.transitionPolicy.defect-lifecycle-workflow.md section 6. Suggest classification for the given bug based on symptoms.defect-lifecycle-workflow.md sections 1-3 as the Jira reference example. Highlight QA-owned transitions.defect-report-templates.md from this skill folder (frontend + backend templates).| Direction | Skill | Relationship |
|---|---|---|
| Upstream | /qa-investigate | Bug investigation produces the defect that enters this lifecycle |
| Upstream | /qa-evidence | Evidence capture standards used in report validation |
| Upstream | /qa-risk | Severity/Priority classification (independent dimensions) |
| Upstream | /qa-bug (command) | Bug filing creates the ticket this skill manages |
| Downstream | /qa-fix (command) | A ready, routable ticket is picked up for autonomous fix |
[Testing] Review test cases for quality, determinism, completeness, data validity, coverage gaps, duplication, live environment verification, and behavioral triangulation against docs + live + source. Delegates browser verification to qa-testing-expert; triangulation to ba-system-analyzer.
[Testing] Postman MCP collections — create, configure, verify, and export collections with proper variables, auth, and endpoints
[Testing] Autonomous test coverage gap analysis and generation — identifies missing test cases, generates enriched CSV test cases, validates P0 cases via browser, and reports improvements. Single-agent counterpart to /qa-coverage-generation.
Repo/tracker routing library for the vc-fix plugin — decides which external product repo owns a bug (client vs platform), whether the fix delivers as a direct PR, a fork-PR, or an upstream issue, and which VCS/tracker host to talk to. Used by /qa-fix and /project-init. Self-contained — no dependency on the ci/ directory.
Build, launch, smoke-test, and health-check the vc-mcp-testing-module agentic QA tooling repo. Use when asked to run, start, verify, smoke-test, or sanity-check this repo's tooling — env:check, @td() resolution, suite manifest sync, critical-UI-scope, seed dry-run, GraphQL fixture validation — or before running regression.
[QA Methodology] Triage a completed regression run's failures: collect each FAIL + its evidence (trace, screenshots, console, network) + failing CSV row, dedup + flag flaky, classify each into real-product-bug vs test-defect (bad steps / bad assertion / stale test data / stale test) vs flaky/env/known, live-verify the real ones, then route test-defects to /qa-review-tests --fix and draft bug reports. Detect-classify-verify-report only — never files a tracker ticket, never triggers /qa-fix.