Jars1987

builder

Implement a plan in the host codebase — reusing existing code before writing new, matching local conventions, keeping changes additive and local where possible, and driving typecheck and lint green before review. Use as phase 3 of the gauntlet pipeline, or standalone when asked to implement an agreed plan, a fix, or a refactor.

AI & Automation Listed

connections

Read and validate the host project's gauntlet configuration — CONNECTIONS.md (toolchain commands, version-control and issue-tracker permissions, limits) and the machine-local MODELS.md (which agent CLIs exist here, and which plays author vs reviewer). Use to discover how to run tests/typecheck/lint in this project, to check whether the agent may push or open a PR, to resolve model roles for a phase, or to invoke the cross-model reviewer.

grill

Interrogate a ticket or a plan until every design decision is resolved, in one of two modes — attended (a real user answers each question) or unattended (the agent generates the hard questions and answers them itself from the codebase, then folds the answers back in). Use before planning broad work, to stress-test a plan before implementation, or when asked to grill, interrogate, or pressure-test a design.

learnings

Write and prune the host project's accumulated learnings in .gauntlet/learnings/ — distil one entry per pipeline run from the worklog, and compact the collection by promoting recurring learnings into RULES.md, merging duplicates, expiring stale ones, and rewriting INDEX.md. Use at the end of a run, or when asked to prune, compact, review, or clean up learnings.

AI & Automation Listed

orchestrator

Drive the gauntlet pipeline phase machine — baseline, grill, plan, build, test, final review, deliver — enforcing the severity gate and the cross-model review⇄fix loop at the four gated phases (plan, build, test, final review), and persisting progress so an interrupted run resumes. Use when running the phases of a ticket after gauntlet:runner has resolved it, or when asked to continue, gate, or re-review a phase of an in-flight run.

planner

Turn a ticket into an implementation plan grounded in the actual codebase — locating existing code to reuse, choosing the approach, defining the interface, data, failure handling and test strategy, and recording assumptions and risks. Use as phase 2 of the gauntlet pipeline, or standalone when asked to plan a change, a fix, or a refactor before writing code.

pr

Write a pull-request description from the branch diff, the ticket and the tests, following a fixed template — in unattended mode (write it to a file, no questions, no git) or interactive mode (draft, confirm with the human, then create or edit the PR on an explicit go-ahead). Use as phase 6 of the gauntlet pipeline, for "/pr", or when asked to describe a branch for review.

reviewer

Adversarially review a plan, an implementation, tests, or a whole diff against the ticket, its acceptance criteria and the project's rules — classifying every finding by severity and ending with the machine-parseable SEVERITY line the gauntlet gate reads. Use at any gauntlet phase gate, as the read-only cross-model reviewer, or standalone when asked to review a change before merge.

runner

Lifecycle wrapper for a gauntlet pipeline run — resolves the ticket from text, a file, or a tracker issue; loads or creates run state; enforces idempotency and the attempt cap; invokes the orchestrator; then writes learnings and deletes the state on success. Use when starting or resuming work on a ticket via /gauntlet:pipeline or /gauntlet:pipeline-with-grill, or when asked to run, resume, or restart a ticket end to end.

Testing & QA Listed

tester

Write tests that prove each acceptance criterion — real inputs, deterministic and offline, mocking only what crosses the process boundary — then run the suite and distinguish genuine regressions from pre-existing and flaky failures. Use as phase 4 of the gauntlet pipeline, or standalone when asked to test a change or add coverage.