qa-cube 플러그인

Test analyst of a /qa test session — writes test cases from the requirements BEFORE the manual run (TMS or files), launched by the QA Manager when `test-cases: upfront`. Never touches the environment, never reads code, never files bugs. Works autonomously, asks the user nothing.

Automation engineer of a /qa test session — writes the autotest from the manual run's evidence, links it to a case (from the analyst or the manual tester, per the profile's `test-cases`), runs it until green, and marks automation on the case. Launched by the QA Manager with an *automator-task*.md br

Manual tester of a /qa test session — checks the feature on the environment per the *manual-task*.md brief; creates the TMS case when `test-cases: inline`, and with `upfront` runs the analyst's ready-made cases. Writes no autotests (that is qa-automator). Works autonomously, asks the user nothing.

Use when the user starts, continues or retests a QA test session — «/qa <link|description>», «test this task», «run a test session», «retest session X», a tracker task handed over for verification; also triggers on the Russian «протестируй задачу», «проведи тест-сессию», «ретест по сессии X».

Use when the user asks what was tested over a day or a week, or how a session on some task ended — «what did I test today», «day digest of test sessions», «QA summary for the week», «how did the session on task X end»; also triggers on the Russian «сводка сессий за день», «что я оттестировал сегодня», «что тестировал за неделю», «чем закончилась сессия по задаче X».

Use when qa-cube needs wiring into a project or its profile needs updating — «/qa-setup», «set up qa for this project», «qa onboarding», or when /qa could not find `.claude/qa-profile.md` or reported that the profile is behind the contract; also triggers on the Russian «настрой qa для проекта», «qa-онбординг».

Skill

파일에 설명이 없습니다.