القائمة
Unified QA entry point for planning test documentation, running single-pass scenarios, and orchestrating the multi-agent QA council.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Qqa |
| description | Unified QA entry point for planning test documentation, running single-pass scenarios, and orchestrating the multi-agent QA council. |
| user_invocable | true |
| metadata | {"author":"inho","version":"1.0.0"} |
| invocation_trigger | When the user asks for QA planning, scenario/E2E execution, or the QA council. |
| recommendedModel | sonnet |
Unified QA entry point. It preserves the behavior of the existing QA skills while exposing a single command surface:
Qqa <plan|run|council> [args]
The original skills remain valid and coexist:
Qqa-test-plannerQscenario-testQqa-council| Subcommand | Reference | Summary |
|---|---|---|
plan | reference/plan.md | Generate test plans, manual test cases, regression suites, Figma verification notes, and bug report templates. Use this for QA documentation without executing the target. |
run | reference/run.md | Generate scenario specs from a TASK_REQUEST, code path, URL, or description; execute browser/API/CLI scenarios once; verify and report results. Browser QA loop (Playwright) is live via scripts/lib/browser-driver.mjs (Phase 6): --browser drives Playwright on demand (optional dependency; detectWebProject recommends it; regression specs named qa-regression-<slug>.spec.ts). |
council | reference/council.md | Run the role-separated QA council: Planner -> Explorer -> Generator -> Healer -> Reporter, with bounded agent/tool contracts and optional PR automation. |
Qqa plan [target]Use when the requested output is QA documentation:
Load and follow reference/plan.md. Do not execute the system under test unless
the user switches to Qqa run or Qqa council.
Qqa run [target|--rerun UUID] [--dry] [--browser|--api|--cli]Use when the request is scenario testing, E2E scenario execution, user-flow verification, or
acceptance testing. Load and follow reference/run.md.
This subcommand preserves Qscenario-test behavior: generate SCENARIO_SPEC, generate
SCENARIO_CHECKLIST, execute scenarios once in browser/API/CLI mode, and write a SCENARIO_REPORT.
Qqa council [url] [mode]Use when the request is a role-separated multi-agent QA loop over a live web app, exploratory QA plus
regression codification, or a PR-triggered QA bot. Load and follow
reference/council.md.
The council must preserve bounded roles:
Qqa plan or Qqa run logic as a skill-backed planning step.Eqa-explorer, browser-only, no source.Qplaywright-expert.Eqa-orchestrator.Eqa-orchestrator.Never pass a Q* skill name as an Agent subagent_type; Q* entries are skills, E* entries are
agents.
| User intent | Choose |
|---|---|
| "Create a test plan", "generate test cases", "regression suite", "bug report template" | Qqa plan |
| "Run scenarios", "E2E", "acceptance test", "verify this flow once" | Qqa run |
| "QA council", "AI QA", "exploratory + regression", "PR QA bot" | Qqa council |
Qqa-test-planner, Qscenario-test, or Qqa-council in this phase.Qqa run is single-pass scenario execution. Long-lived browser QA loops belong to the later Phase
6 extension.Use when collecting verified project-local coding guidance into .claude/skills based on the project tech stack, with TTL and user-edit protection.
Shows QE Framework usage overview. With no arg, prints the full catalog. With a skill name arg (e.g., /Qhelp Qcommit), reads that skill's SKILL.md and summarizes it in the user's language. Also supports find/search skills mode via reference/find-skills.md.
QE framework (Query Executor) initial setup. Creates the QE state directory, client-specific instruction/config artifacts, and .gitignore entries in a new project, then auto-analyzes the project. Use when the user wants to initialize a project or set up the framework.
Diagnoses and repairs QE installation health across qe-framework, MCP client config, and the project .qe directory. Use for 'doctor', 'check QE health', dependency verification, corrupted .qe state, or repair guidance. Distinct from Qupdate, which updates installed assets.
Use when executing a TASK_REQUEST/VERIFY_CHECKLIST or when already-changed code needs the test-review-fix quality loop. With no flag it auto-selects sequential or parallel-wave execution; `-verify` runs verification. Use Qautoresearch for iterative code-optimization loops and Qscenario-test for scenario/E2E.
Use when a plan or task needs spec documents: TASK_REQUEST and VERIFY_CHECKLIST. Use Qplan for roadmap/phases; use Qexecute after the spec exists.