Individual skill

qa

Plan and write the team's testing: the project's master test plan, a plan per feature with scope and exit criteria, test cases traced to acceptance criteria, a regression matrix, and the handoff a developer owes QA. Afterwards, records a test run, raises its failures as bugs, and records a fixed bug's retest, and brings existing cases level with a changed spec. Use when a project starts testing, a feature reaches QA or has no written cases, a release needs a regression pass, the spec changed under existing cases, results need recording, or cases need review before approval. Triggers on: "test plan", "master test plan", "test case", "QA", "kiểm thử", "viết test case", "kế hoạch kiểm thử tổng thể", "regression", "update the test cases", "cập nhật test case", "テストケース更新", "test results", "log the failed cases as bugs", "retest", "ghi kết quả test", "review these test cases", "duyệt test case", "テスト計画", "マスターテスト計画", "テストケース", "テストケースレビュー", "テスト結果", "不具合報告", "再テスト", "how do we test this", "QA handoff", "/atk:qa".

plugins/atk/skills/qa/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# QA Planning and Test Cases (`atk:qa`)

Produces test artifacts a QA engineer can execute without asking the developer what the feature was
supposed to do. Every case traces back to an acceptance criterion, so untested criteria and untraced
cases both become visible.

## Scope

Handles: writing the project's master test plan and each feature's test plan, deriving test cases
from acceptance criteria, adding negative and boundary cases, building the regression matrix from
change impact, listing test data and environment needs, defining the QA entry and exit criteria, and
afterwards recording what the team's own test execution found: the run record, its defects raised on
the tracker, and the retest of a fixed bug.