Extract, record, and enforce the coding conventions a team actually follows: branch and commit rules, naming, layering, error handling, test layout, review etiquette, and the tooling that enforces each rule. Also drafts the collaboration files the project lacks, `CONTRIBUTING.md`, the pull request template, and `CODEOWNERS`, writing only the ones the team picks. Use when a team has no written convention, when the written one no longer matches the code, or when reviews keep repeating the same comment. Triggers on: "convention", "coding standard", "coding rule", "style guide", "branch strategy", "commit convention", "our team rules", "CONTRIBUTING.md", "CODEOWNERS", "contribution guide", "set up a pull request template", "standards per language", "coding standard for each technology", "/atk:convention".

Execute approved test cases against a deployed DEV or staging environment, through the browser or an app on an Android device: refuse production and the local stack, recon the accounts and data, triage every case as automatable, semi-automatable, manual, or blocked, naming who clears each obstacle, agree the scope with the person before any case runs, run in at most three rounds, and write only the results it observed into a run record the QA lead approves and `atk:qa --bug` reads. Use when a cases file is approved, a non-production environment is deployed, and the team wants an agent to execute the automatable part instead of a tester. Triggers on: "run the test cases", "execute test cases", "run these cases on staging", "automate these test cases on DEV", "run test cases on the mobile app", "/atk:run-cases".