popup-studio-ai/qa-phase
skills/qa-phase/SKILL.md
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 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.
$ install --global
skillsauthnpx skillsauth add popup-studio-ai/bkit-claude-code qa-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 6:29 AM179.2s1 file scanned
SKILL.md
- name:
- qa-phase
- context:
- fork
- classification:
- workflow
- classification-reason:
- QA phase automation within PDCA cycle
- deprecation-risk:
- none
- effort:
- high
- description:
- |
- Triggers:
- qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.
- argument-hint:
- [feature]
- user-invocable:
- true
- lead:
- bkit:qa-lead
- planner:
- bkit:qa-test-planner
- generator:
- bkit:qa-test-generator
- debug:
- bkit:qa-debug-analyst
- monitor:
- bkit:qa-monitor
- default:
- bkit:qa-lead
- next-skill:
- pdca
- pdca-phase:
- qa
- task-template:
- [QA] {feature}
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
scripts/qa/pre-release-check.shvia Bash - 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
- Ask user whether to continue or abort QA phase
- 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 |
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
**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
Related Skills
popup-studio-ai/sprint
testing
VerifiedTrustedCommunity
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
548SKILL.mdUpdated May 13, 2026
popup-studio-ai/cc-version-analysis
tools
VerifiedTrustedCommunity
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
545SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/rollback
testing
VerifiedTrustedCommunity
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
539SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/pm-discovery
data-ai
VerifiedTrustedCommunity
PM Agent Team — automated product discovery, strategy, and PRD generation with 4 PM agents (for a single feature). For multi-feature initiatives with shared scope/budget/timeline, use /sprint master-plan which generates a sprint-level PRD via sprint-master-planner agent (v2.1.13). Triggers: pm, PRD, product discovery, PM 분석, 제품 기획, PM analysis.
539SKILL.mdUpdated Apr 18, 2026