documenting-qa

To generate an adversarial QA plan, provide the PR title, body, and diff. The skill constructs failure scenarios across five dimensions and outputs the plan artifact to qa/test-plans/QA-plan-{ID}.md.

Adversarial testing targets failure modes across five dimensions: inputs, state transitions, environment, dependency failure, and cross-cutting concerns. It surfaces edge cases engineers overlook by analyzing actual code diffs rather than requirements docs.

Yes, you can generate a QA plan from a requirement ID and user story when no PR exists. The skill operates from the requirements user story in the absence of a PR summary.

Yes, jq is a required dependency. The skill uses jq to process inputs and ensures the generated QA plan artifact includes proper frontmatter and passes stop-hook validation.

The best way is organizing scenarios by adversarial dimensions: inputs, state transitions, environment, dependency failure, and cross-cutting concerns. This structure surfaces failure modes missed by standard requirement-based testing.

Building a QA plan from code diffs surfaces failure modes engineers might overlook. It reflects actual implementation behavior rather than intended requirements, revealing hidden state transitions and dependency failures.