Skill v1.0.0

version: "1.0.0" name: qa description: Check the finished work now - run every proof and explain in plain words what passes, what fails and what only you can judge. allowed-tools: Bash("${CLAUDE_PLUGIN_ROOT}/bin/vbw" ) Bash(vbw )

"${CLAUDE_PLUGIN_ROOT}/bin/vbw" show requirements 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" show qa 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true

Write to the user's level, explanation depth and involvement (above; "-": plain words).

1. If the contract is approved, run vbw prove --full; otherwise say the plan and its

tests wait for approval, ask only with the approval menu (AskUserQuestion), never to type a command, and stop.

1. Explain the result in plain words, requirement by requirement: proven,

failing (with the reason from vbw show evidence), or still being built. Name any failed project command, any commit that changed files outside its plan, and any file a plan delivered that was changed or deleted outside any plan (delivered: lines of vbw show evidence; QA cannot pass its phase until a fix brings it back or the user decides to keep the change).

1. The [human] requirements no check can prove: list the ones whose work is

built (built above) and offer /vbw:verify to check them now.

1. From vbw show qa (above), tell the user which phases are checked again and

why, and which phases keep their pass (their earlier pass still stands), in plain words at their level, explanation depth and involvement. Say it before the results, and explain any term a beginner would not know.

1. If something fails, say what happens next: /vbw:vibe fixes failures

(each becomes a fix item, worked and proved again).