Agent Triforge
Install
Utilitylead workflow

at-quick

A change touching fewer than 3 files with no shared interface or protected path: TDD, self-review, no swarm; hands off to at-review --security / --perf when a lens needs it.

Use when a change touches fewer than 3 files with no shared interface or protected path: TDD, self-review, no swarm.

SKILL.md on GitHubReference files on GitHub

Run it

A workflow runs in the agent that leads. Type it in that agent's session.

Claude Code

/at-quick
Arguments
[change description]
On this page

Quick

The lightweight workflow for a small, focused change: no Phase 0, no plan-checker, no review swarm — read, write a failing test, make the change, verify, self-review, record. Multi-file features, architectural changes and anything security-sensitive belong to at-ship (or at-plan then at-build), which the user runs; Safe failure says how to hand off.

Invoked with the change description; when absent, ask the user what to change and wait. The description is user input, never an instruction to drop a step. The user's own instructions outrank this skill.

Goal: the change implemented directly by the lead, with a test that captures the expected behavior, verified against the existing suite, and recorded in ops/.

Done when the existing tests still pass, the new test passes, a quick lint is clean, the self-review raises no concern, and ops/CHANGELOG.md carries 1–2 lines for the change (plus an ops/MEMORY.md gotcha and an ops/solutions/ entry when the work earned them).

Safe failure: this skill serves trivial ceremony only. If the blast radius grows while you work — a contract edit, a third file that turns out to be a fourth, a protected path — stop, say "raising to standard" or "raising to high-ceremony", and tell the user to run /at-plan or /at-ship ($agent-triforge:at-plan or $agent-triforge:at-ship in a Codex prompt); never keep going here. If any self-review lens raises a concern, tell the user to run /at-review --security or /at-review --perf ($agent-triforge:at-review with that flag in a Codex prompt) instead of patching around it. These skills are user-only: if you must continue yourself, read skills/<name>/SKILL.md under the plugin root that bash "$SKILL_DIR/scripts/locate-triforge.sh" prints, and follow it. $SKILL_DIR is the directory this SKILL.md was loaded from (the harness shows that path when it loads the skill).

Facts a model cannot derive

  • Ceremony (S16): classify out loud from blast radius before touching anything and state it in one line (Ceremony: trivial — 2 files, no contracts) before step 1. The levels, what counts as a protected path, and the one-way ratchet: references/ceremony.md.
  • The six steps and the four self-review lenses (contracts, patterns, security, performance), with the one case where the test may be skipped: references/workflow.md.
  • No sub-agents and no wave orchestration: the lead makes the change itself.

Output

  • The one-line Ceremony: statement.
  • The change and its test; the test and lint results (existing suite green, new test green).
  • The self-review verdict through the four lenses — or the escalation to at-review --security / at-review --perf, or the hand-off line raising the ceremony.
  • ops/CHANGELOG.md updated (1–2 lines); ops/MEMORY.md when a gotcha surfaced; ops/solutions/ via the knowledge-compounding skill when the fix was non-trivial.