# QA.army agentic setup prompt

This prompt states the requested setup and requires an honest capability check.
GitHub comment commands, diff-derived Tests, GitHub-only signup, and complete
cross-Workspace coverage are still delivery targets. Do not report them as
configured unless the live product supports and verifies them.

```text
Set up QA.army (https://qa.army) for this application and the GitHub repositories I authorize. Handle the setup yourself; ask me only for missing information or a required human authentication step.

1. Read https://qa.army/auth.md and https://api.qa.army/v1/openapi.json. Reuse an authorized agent identity or open one short-lived claim link and wait for my one-time user code. Keep credentials out of code, comments, logs, and chat. Use the native OS credential store and memory-only Bearer access tokens. Re-exchange on 401; follow the response on 403.
2. Discover this repository, its deployed application URL, and the Workspaces I can access. Ask when the intended Workspace or application URL is ambiguous. Create or reuse the Project within the correct Workspace. Preserve User ↔ Workspace → Project → Test Group → Test → Run.
3. Follow https://qa.army/skill.md. Create or reuse a Test Group and plain-language regression Tests for the critical customer journeys. Use only supported live API operations; do not guess endpoints, CLI flags, or comment commands.
4. Connect the authorized GitHub repositories through QA.army's supported connection flow. Configure selected Test Groups against the corresponding deployed PR revision. If supported, derive additional Tests from the PR diff and use GitHub comments as the primary conversation for plans, live Run links, and evidence. Report any unsupported capability or missing permission explicitly.
5. This prompt authorizes one initial Run of the critical journey for this application. Share its live Test Run URL immediately, wait for its terminal result, and report PASSED, FAILED, ERROR, or CANCELLED with the same URL. Do not retry an ambiguous or mutating action automatically.
6. Enable and verify the QA.army required check for each authorized repository only after its PR trigger and preview target work. Preserve existing branch protections and bind the check to the QA.army GitHub App. Verify that the current PR commit is blocked when results are missing, failed, cancelled, or inconclusive, and clears only after passing evidence.
7. Return a coverage table: Workspace, Project, repository, application URL, Test Groups, latest Run, required-check state, and missing coverage. Claim completion only for behavior verified in the live product. Stop before a release if any required journey or guard remains unverified.
```