sp-write-test-plan

Author an integration test plan by collecting implementation evidence and prior bugfix history, then applying ordered adversarial passes to probe cross-component behavior like async retries, idempotency, and partial failures. This structured approach surfaces real fragility before execution.

Adversarial testing targets failures already present in the current implementation by using prior bug history, seam checks, and red-team hypotheses. You need it when planning integration tests for cross-component features with external dependencies, timeouts, or partial failures to expose hidden defects.

No, you must enforce a strict one-task-to-one-plan-to-one-project scope gate. This ensures the plan targets the correct implementation surface for the specific repository before test design begins, preventing misaligned coverage in multi-repo workflows.

Structure the plan using ordered adversarial passes—gamma, beta, and alpha—documented in structured tables. Combine constructive coverage with adversarial discovery using prior bug history, culminating in a final flicknote-ready output for operational use.

Yes, the adversarial integration test plan specifically applies when planning tests for cross-component features involving external dependencies, timeouts, async operations, retries, idempotency, or partial failures, using evidence collection to inform targeted discovery.

Skipping Phase 1 evidence collection from the implementation and prior tasks removes the foundation for adversarial discovery. Without analyzing prior bugfix history and current seams, the test plan cannot meaningfully target failures already present in the multi-component behavior.