Agent skill

QA Phase

QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature.

Apache-2.0Auto-check: notesTesting & QA

Install QA Phase

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qa-phase .claude/skills/qa-phase && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .claude/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qa-phase .agents/skills/qa-phase && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .agents/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qa-phase .cursor/skills/qa-phase && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .cursor/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ww-w-ai/bkit-claude-code.git --path skills/qa-phase

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qa-phase .gemini/skills/qa-phase && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .gemini/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qa-phase .github/skills/qa-phase && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .github/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ww-w-ai/bkit-claude-code qa-phase --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qa-phase .opencode/skills/qa-phase && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "qa-phase" agent skill from https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/qa-phase into .opencode/skills/qa-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-phase", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: qa-phase
GitHub stars: 601
Token cost: ~1.3k tokens
SKILL.md length: 517 words
Files: 1
Skills in repo: 44
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature.

Works in 5 steps: Context: Read design doc and Check phase… → Plan: Generate test plan (L1-L5 items… → Generate: Create test code files → …
Tasks that involve Test strategy
SKILL.md covers Arguments, Workflow, PRE-SCAN: Pre-Release Quality… and Test Levels, plus 2 more sections
Calls bash

What it does

QA Phase is an agent skill from ww-w-ai/bkit-claude-code. QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test strategy. The repository describes itself as: bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Test strategy

Example prompts

“/qa-phase”

Requirements

Node.js
Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, Task, AskUserQuestion

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Context: Read design doc and Check phase analysis
Plan: Generate test plan (L1-L5 items with priorities)
Generate: Create test code files
Execute: Run L1-L5 tests (L3-L5 require Chrome MCP)
Report: Generate QA report to docs/05-qa/{feature}.qa-report.md

What it can do on your machine

Read from SKILL.md and the folder at commit 85b4913. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
- Task
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

QA Phase loads about 1.3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 517 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Task, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ww-w-ai/bkit-claude-code at commit 85b4913, republished under its Apache-2.0 licence (© ww-w-ai). 517 words, ~1,311 tokens.

Download SKILL.mdSave it as .claude/skills/qa-phase/SKILL.md (or your agent's skills folder).

name: qa-phase
description: QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Task, AskUserQuestion
classification: workflow
classification-reason: QA phase automation within PDCA cycle
deprecation-risk: none
effort: high
argument-hint: [feature]
user-invocable: true
agents.lead: bkit:qa-lead
agents.planner: bkit:qa-test-planner
agents.generator: bkit:qa-test-generator
agents.debug: bkit:qa-debug-analyst

QA Phase Skill

Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.

Arguments

Argument	Description	Example
`[feature]`	Target feature to test	`/qa-phase user-auth`

Workflow

Context: Read design doc and Check phase analysis
Plan: Generate test plan (L1-L5 items with priorities)
Generate: Create test code files
Execute: Run L1-L5 tests (L3-L5 require Chrome MCP)
Report: Generate QA report to docs/05-qa/{feature}.qa-report.md

PRE-SCAN: Pre-Release Quality Check

Before running L1 tests, execute the automated quality scanners to catch structural issues early.

Steps

Run bash ${PLUGIN_ROOT}/scripts/qa/pre-release-check.sh via Bash. The path must be absolute: the script ships inside the plugin, not in the user's project, so a relative scripts/qa/... resolves to nothing wherever this skill actually runs. The script scans $CLAUDE_PROJECT_DIR (falling back to the working directory) — pass --root DIR to point it elsewhere.
Parse the output for CRITICAL / WARNING / INFO counts
If CRITICAL issues found:
- Report all CRITICAL issues with file paths and suggested fixes
- Recommend fixing CRITICAL issues before proceeding with L1-L5 tests
- Use AskUserQuestion to ask whether to continue or abort the QA phase (e.g. options: "Fix CRITICAL first" / "Continue anyway" / "Abort QA"). This gate is issued directly here, in the main session context — qa-phase is deliberately not context: fork. AskUserQuestion is stripped at the fork sub-agent boundary (CC #34592 / #54892), so it must run in the main context and must not be delegated to a sub-agent (qa-lead, etc.).
If only WARNING/INFO issues (no CRITICAL):
- Include scanner results in the QA report under "Pre-Release Scan" section
- Continue to L1 test planning

Scanner Coverage

Scanner	Detects	Severity
dead-code	Stale require/import, unused exports	CRITICAL / WARNING
config-audit	Unreferenced config keys, hardcoded values, missing paths	CRITICAL / WARNING / INFO
completeness	Missing agents, long descriptions, missing effort	CRITICAL / WARNING / INFO
shell-escape	Bare $N in awk, unescaped backticks, unsafe heredocs	CRITICAL / WARNING
wiring	Exported but never called functions	WARNING

Show full SKILL.md (203 more words)Show less

QA Report Integration

When scanner results are available, include them in the QA report:

markdown

## Pre-Release Scan Results

- **Scanner**: dead-code — 0 CRITICAL, 1 WARNING, 0 INFO
- **Scanner**: config-audit — 0 CRITICAL, 0 WARNING, 2 INFO
- **Scanner**: completeness — 0 CRITICAL, 0 WARNING, 1 INFO
- **Scanner**: shell-escape — 0 CRITICAL, 0 WARNING, 0 INFO
- **Scanner**: wiring — 0 CRITICAL, 1 WARNING, 0 INFO

**Overall**: PASS (0 CRITICAL issues)

Test Levels

Level	Type	Tool	Chrome Required
L1	Unit Test	Node.js / Jest / Vitest	No
L2	API Test	fetch / curl	No
L3	E2E Test	Chrome MCP	Yes
L4	UX Flow Test	Chrome MCP	Yes
L5	Data Flow Test	Chrome MCP + Bash	Yes

Browser QA Depth (L3-L4)

qa-lead adds three things on top of the scripted L3-L4 scenarios. The full procedure is in agents/qa-lead.md:

Diff-aware scope — changed files are mapped to the pages and endpoints they serve, and those pages are tested first.
Exploratory pass — each priority page is checked for forms, empty/error states, navigation, and console output after every action.
Health Score — a weighted 0-100 summary of the exploratory findings, reported next to the gate metrics. It is informational; the QA gate (qaPassRate, qaCriticalCount, runtimeErrorCount) still decides the verdict.

On QA_FAIL, issues are handed to Act in fix order with reproduction steps. Act fixes one issue at a time, re-verifies it, and adds a regression test. It stops to ask when fixes start spreading to unrelated files or breaking passing tests.

Fallback

Chrome MCP unavailable:

L1 + L2 only
QA report notes "L3-L5 skipped"
QA pass/fail based on L1+L2 results only

Files

Just SKILL.md in skills/qa-phase of ww-w-ai/bkit-claude-code.

Open the folder on GitHubat commit 85b4913

Compare with similar skills

QA Phase next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

QA Phase compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
QA Phase this skillww-w-ai/bkit-claude-code	601	—	~1.3k	Automated safety check: Notes	Apache-2.0	13 days ago
Testing OpenLogi UIAprilNEA/OpenLogi	23k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Testing Hashqlhashintel/hash	1.7k	—	~1.9k	Automated safety check: Pass	AGPL-3.0	today
Dynamo Unit TestingDynamoDS/Dynamo	2k	—	~622	Automated safety check: Pass	Apache-2.0	today
Bmad Testarch Test Designbmad-code-org/bmad-method-test-architecture-enterprise	105	3 repos	~1.4k	Automated safety check: Pass	Custom licence	today
Designing TestsCloudAI-X/opencode-workflow	275	—	~2.9k	Automated safety check: Pass	MIT	9 mo ago

Similar skills

Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
23k GitHub stars~1.1k tokensUpdated today
Testing & QAAuto-check passed
Testing Hashql
hashintel/hash
HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests.
1.7k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed
Dynamo Unit Testing
DynamoDS/Dynamo
Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints.
2k GitHub stars~622 tokensUpdated today
Testing & QAAuto-check passed
Bmad Testarch Test Design
bmad-code-org/bmad-method-test-architecture-enterprise
Create system-level or epic-level test plans. An agent skill from bmad-code-org/bmad-method-test-architecture-enterprise.
105 GitHub starsUsed in 3 repos~1.4k tokens
Testing & QAAuto-check passed
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
275 GitHub stars~2.9k tokensUpdated 9 mo ago
Testing & QAAuto-check passed
Openprd Test Strategy
DavidLam-oss/obsidian-wechat-converter
OpenPrd 测试策略分流 skill：按风险把任务分到单元、集成、端到端、人工、视觉、小程序、性能和安全验证，并要求 evidence-plan。
335 GitHub stars~578 tokensUpdated today
Testing & QAAuto-check passed

Questions about QA Phase

What does QA Phase do?

QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. QA Phase is an agent skill from ww-w-ai/bkit-claude-code. QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature.

When should I use QA Phase?

QA Phase fits situations like: tasks that involve Test strategy.

How do I install QA Phase in Claude Code?

Run `npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a claude-code`. Or copy the skill folder (skills/qa-phase in ww-w-ai/bkit-claude-code) into .claude/skills/qa-phase in your project. Claude Code loads it when a task matches its description.

How do I install QA Phase in Codex?

Run `npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a codex`. Or copy the skill folder (skills/qa-phase in ww-w-ai/bkit-claude-code) into .agents/skills/qa-phase in your project. Codex loads it when a task matches its description.

Can I use QA Phase in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ww-w-ai/bkit-claude-code --skill qa-phase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-phase, .gemini/skills/qa-phase, .github/skills/qa-phase and .opencode/skills/qa-phase in your project.

What does QA Phase need to run?

Going by SKILL.md and its folder, QA Phase needs the command-line tools its instructions call (bash). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, Task, AskUserQuestion.

Does QA Phase access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is QA Phase safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does QA Phase use?

QA Phase is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does QA Phase use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to QA Phase?

Skills that share tags, products or a category with QA Phase: Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Testing Hashql (hashintel/hash, 1.7k stars), Dynamo Unit Testing (DynamoDS/Dynamo, 2k stars) and Bmad Testarch Test Design (bmad-code-org/bmad-method-test-architecture-enterprise, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains QA Phase?

ww-w-ai (a GitHub organization) maintains it in ww-w-ai/bkit-claude-code, which has 601 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on September 27, 2026.

Source: ww-w-ai/bkit-claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install QA Phase

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

QA Phase Skill

Arguments

Workflow

PRE-SCAN: Pre-Release Quality Check

Steps

Scanner Coverage

QA Report Integration

Test Levels

Browser QA Depth (L3-L4)

Fallback

Files

Compare with similar skills

Similar skills

More from ww-w-ai/bkit-claude-code

Related

Questions about QA Phase