Lessons promoted to the organisation. Every workspace's agent retrieves from this shared brain when it drafts a spec — capture once, reuse everywhere.
Any real-time/websocket delivery feature must include an explicit offline → deliver-on-reconnect acceptance scenario, or it regresses under deploys.
External webhook integrations re-deliver; always add a duplicate-delivery scenario and an idempotency decision.
When users can change delivery preferences, add a scenario asserting changes are recorded and respected immediately.
Limit features should scope quotas per tenant and add a noisy-neighbour scenario.
Delivery / latency outcomes must carry a time bound (within N s) or the QA agent can't assert them.
Scenarios describe behaviour, not mechanism — tech names couple the spec to today's design.
Multiple Thens hide multiple tests; split so each can pass or fail on its own.
The failure modes are where the real spec lives.