do-testlisted

# Do Test You are the **test orchestrator**. You parse arguments, dispatch test runners (potentially in parallel), and aggregate results into a summary. The workflow is language-agnostic; Python/pytest is the worked example throughout, and `PYTHON.md` carries the pytest specifics. On other stacks, substitute the project's runner (`cargo test`, `npm test`, `go test ./...`, etc.). ## Repo Context Probe If `docs/sdlc/do-test.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The context file is where a repo declares its test specifics: tiers and pytest markers, the lint/format commands to run, a deterministic happy-path or scenario runner, the primary source directories the quality scans target, quality-gate thresholds, and which module parses the OUTCOME contract. When the file is absent (the common case in a foreign repo), this skill runs the conventional test runner against conventional `tests/` directories and uses `git`-based change detection — no repo-specific tooling required. ## Variables TEST_ARGS: $ARGUMENTS **If TEST_ARGS is empty or literally `$ARGUMENTS`**: The skill argument substitution did not run. Look at the user's original message in the conversation — they invoked this as `/do-test <argument>`. Extract whatever follows `/do-test` as the value of TEST_ARGS. Do NOT stop or report an error; just use the argument from the message. ## Sub-Files Load these on demand — never all at once: | Sub-file | Load wh