메뉴
Master skill coordinating all QA skills through pipeline modes (full-cycle, docs-only, testcases-only, write-tests, report), formalized handoff chains, scheduler rules, and framework/language selection based on project context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | qa-orchestrator |
| description | Master skill coordinating all QA skills through pipeline modes (full-cycle, docs-only, testcases-only, write-tests, report), formalized handoff chains, scheduler rules, and framework/language selection based on project context. |
| dependencies | {"recommended":["qa-diagram-generator","qa-discovery-interview"]} |
Master coordinator for all QA skills in the ecosystem. Routes work through pipeline modes, formalized handoff chains, and scheduler rules. Selects frameworks and languages based on project context. Uses Memory MCP for cross-session persistence.
| Mode | Flow | When to Use |
|---|---|---|
| full-cycle | docs → test cases → tests → execution → reports | New feature, full validation |
| docs-only | requirements → spec → diagram | Documentation phase |
| testcases-only | docs/spec → test cases | Test design phase |
| write-tests | test cases → tests | Automation phase |
| report | results → report | Post-execution reporting |
See references/pipeline-modes.md for detailed configurations.
discovery-interview → requirements-generator → spec-writer → diagram-generator → testcase-from-docs → playwright-ts-writer → test-healer (if fail) → test-reviewer → test-reporter → project-memory:update
requirements-generator → spec-writer → diagram-generator → testcase-from-docs → playwright-ts-writer → test-healer (if fail) → test-reviewer → test-reporter → project-memory:update
browser-data-collector → testcase-from-ui → playwright-ts-writer → test-healer → coverage-analyzer → task-creator (for gaps) → project-memory:update
api-contract-curator → testcase-from-docs → supertest-writer / httpx-writer → pact-writer → test-reporter → project-memory:update
flaky-detector → test-healer → test-reviewer → changelog-analyzer → regression scope → project-memory:update
See references/handoff-chains.md for input/output contracts per step.
| Trigger | Actions |
|---|---|
| After merge | Smoke/regression → report → bug if fail |
| Before release | Completion report + risk analysis |
| After requirement change | Impact analysis → update RTM |
See references/scheduler-rules.md for automation patterns.
| Project Signal | Ecosystem | Writers |
|---|---|---|
tsconfig.json present | TypeScript | playwright-ts-writer, jest-writer, vitest-writer, supertest-writer, cypress-writer |
setup.py / pyproject.toml | Python | playwright-py-writer, pytest-writer, httpx-writer, selenium-py-writer |
pom.xml / build.gradle | Java | selenium-java-writer, junit5-writer, rest-assured-writer, spring-test-writer |
Selection is automatic based on project root detection. User can override.
Uses Memory MCP for cross-session persistence:
docs/qa-memory/ via qa-project-memory (final chain step)Can do (autonomous):
Cannot do (requires confirmation):
Will not do (out of scope):
| Symptom | Likely Cause | Fix |
|---|---|---|
| Wrong chain selected | Ambiguous project type | Ask: E2E, UI-first, or API-first? |
| Missing handoff | Skill output format mismatch | Check references/handoff-chains.md contracts |
| Framework not detected | Non-standard project layout | User override: specify ts/py/java |
| Scheduler not firing | Trigger not matched | Verify "after merge" / "before release" phrasing |
| State lost between sessions | Memory MCP not configured | Ensure MCP server enabled and connected |
QA project memory with auto-update. Structured log of bugs, decisions, tests, regressions, environments. Automatically updated after every QA task. Archive system with searchable index for large projects. Trigger phrases (EN): "initialize memory", "init qa memory", "find known bug", "search memory", "show what was done", "check regressions", "memory status", "archive memory", "log a bug", "add decision", "memory summary", "what bugs do we know", "update memory", "show test log". Trigger phrases (UA): "ініціалізувати пам'ять", "знайти відомий баг", "пошук у пам'яті", "показати що було зроблено", "перевірити регресії", "статус пам'яті", "архівувати пам'ять", "залогувати баг", "додати рішення", "зведення пам'яті", "які баги відомі", "оновити пам'ять", "показати лог тестів", "що ми вирішили про", "які тестові середовища є".
Analyze OpenAPI/Swagger spec (JSON or YAML) against existing test files and generate an HTML coverage report with QA automation tasks. Use when user provides an OpenAPI spec file and wants to know test coverage status.
Generate accessibility tests for WCAG 2.2 compliance using axe-core, Pa11y, and Lighthouse with automated checks for ARIA patterns, keyboard navigation, color contrast, and screen reader support.
Manage and formalize API contracts from existing endpoints, swagger/JSON, network traffic, or developer interviews into OpenAPI specifications.
Autonomously explore live web applications using Playwright MCP to collect page structure, form fields, validation rules, API endpoints, and user flows for test case generation.
Generate structured bug reports from test failures with expected/actual results, reproduction steps, evidence, severity/priority, and auto-create GitHub Issues via GitHub MCP with duplicate detection.