---
name: bosskuai-integration-testing
description: Use this for integration test design, contract testing (CDC/Pact), test double strategy, fixture management, and validating behavior at module and service boundaries.
---

# BosskuAI Integration Testing

Use this for integration test design, contract testing (CDC/Pact), test double strategy, fixture management, and validating behavior at module and service boundaries.

## Fast Path

1. Confirm the requested outcome and constraints.
2. Use the smallest checklist needed; do not load the full playbook by default.
3. Produce the artifact, review, or decision in the user-requested format.
4. State verification performed and any remaining risk.

## When To Open The Playbook

Open `../../references/playbooks/bosskuai-integration-testing-playbook.md` only when the task needs detailed framework choices, longer checklists, examples, or implementation depth.

## Default Output

- Start with the answer or changed recommendation.
- Use concise bullets for tradeoffs.
- Avoid generic AI/SaaS phrasing.
- For implementation work, include exact files, commands, tests, or review notes.

## Verification

Before finalizing, check:

- Did the output solve the actual request?
- Are assumptions and risks visible?
- Is there a concrete next action?
- Did we avoid loading unnecessary specialist context?