gs-qa-scenarios

Installation
SKILL.md

QA scenarios

Write the scenarios a QA engineer follows to check a change by hand in the running application. The reader knows the product and does not read code. Each scenario says what to test, why it matters, and the exact steps and result to expect.

The tester works through the output like a to-do list. A checklist at the top carries one box for each scenario, and each result sits under the step that produces it.

This skill changes no code. In write mode it prints the scenarios in chat. In the two run modes it also drives the app through the project's verification skill and saves the evidence under .verify/. Hunting for defects is the gs-review skill.

Modes

The user picks a mode in prose. With no mode named, use write.

  • write: the default. Write the scenarios in steps 1 to 6 and print them. Launch no app and drive nothing beyond what step 6 allows.
  • write and run: write the scenarios in steps 1 to 6, then run them in step 7 and report a result for each one. Phrases such as "write and run QA scenarios for this branch" or "automate the QA steps" pick this mode.
  • run: run scenarios written earlier in step 7, without writing new ones. Phrases such as "run the QA scenarios in qa.md" or "run the QA scenarios on pull request 482" pick this mode.

Arguments

Installs
3
First Seen
3 days ago