← ClaudeAtlas

team-agreementslisted

Produces the written working agreement between the QA engineer and the product team — ticket flow, artefact review responsibilities, defect handling, communication cadence — and the half-page document that gets signed off. Use this skill during onboarding onto a new project, before the first pipeline run delivers artefacts to anyone else, whenever the user asks how to set expectations with a team, or when friction appears over who reviews what. Also use it to revise agreements after the pilot period.
YevheniiaQA/qa-agent-toolkit · ★ 0 · AI & Automation · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Team Agreements The most underrated setup step. A perfectly configured agent delivering artefacts into a team with no agreed process creates more chaos than value — fifty scenarios land in someone's review queue unannounced, nobody knows who owns the defect triage, and by week three the team has quietly stopped reading them. This is an organisational skill, not a technical one. Its output is a half-page document sent to the team lead. ## Why this working format needs explaining A QA engineer operating with an agent works differently from an embedded tester, and the team will notice. Say it up front rather than letting them discover it: - Attends key testing-related sessions, not every standup and planning - Does not investigate root causes — finds and documents defects; the team diagnoses and fixes - Does not deep-dive each microservice — works from the global context and documentation - Covers several projects simultaneously, which is only possible because of the above Framing matters here. This is not a lighter version of QA; it is a different distribution of work, and the team gets more test coverage in exchange for handling their own root-cause analysis. ## What to agree **1. Ticket flow and entry criteria** ``` Analyst writes requirements in Jira → ticket reaches "Ready for QA" → QA runs the pipeline → scenarios + automated tests → review → PR into the test repository ``` Agree the exact status that signals readiness. Agree that incomplet