How do I install the QA Phase skill?

Run npx skillmds@latest add popup-studio-ai/qa-phase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is QA Phase safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Phase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is QA Phase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published QA Phase?

popup-studio-ai (@popup-studio-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA Phase by popup-studio-ai — Agent Skill

Name: QA Phase
Author: popup-studio-ai

QA Phase

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

File contents

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

QA Report Integration

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

## 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

Fallback

Chrome MCP unavailable:

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

---name: qa-phasedescription: 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---# 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` |## Workflow1. **Context**: Read design doc and Check phase analysis2. **Plan**: Generate test plan (L1-L5 items with priorities)3. **Generate**: Create test code files4. **Execute**: Run L1-L5 tests (L3-L5 require Chrome MCP)5. **Report**: Generate QA report to `docs/05-qa/{feature}.qa-report.md`## PRE-SCAN: Pre-Release Quality CheckBefore running L1 tests, execute the automated quality scanners to catch structural issues early.### Steps1. 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.2. Parse the output for CRITICAL / WARNING / INFO counts3. **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.).4. **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 |### QA Report IntegrationWhen 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 |## FallbackChrome MCP unavailable:- L1 + L2 only- QA report notes "L3-L5 skipped"- QA pass/fail based on L1+L2 results only

Frequently asked questions