agent-teamwork-kit v4.2.1

Instructions with enforcement where it counts.

Six skills tell coding agents how to work. Two guards check the parts that should not depend on judgment.

// the agent that builds a thing never approves it

Two layers

Instruction Layer

Six skills shape the work

They cover reasoning, role separation, planning, implementation, test evidence, and maximum-assurance review. The plugin installs this layer only.

Enforcement Layer

Two guards check mechanical boundaries

The Destructive Guardian runs before shell execution. The Change Guardian checks final repository state. Each guard is installed and wired separately.

Not every skill needs a guard. Use enforcement when a rule has a mechanical answer and a miss can cause real damage.

The governed loop

  1. OperatorOwns the outcome and publication.
  2. OrchestratorScopes the work and dispatches it.
  3. Pressure-TesterAttacks the plan before building starts.
  4. BuilderImplements the fixed outcome. Never approves it.
  5. ReviewerChecks the final state in a separate session.

A seat is a role for one session. It is not a person or a vendor. Solo work starts with fewer seats and adds independent review as the stakes rise.

When to load each skill

Any nontrivial task beginsThinking
Work touches a repository, record, or another agentTeamwork
Outcome, scope, authority, and evidence are fixedBetter Coding
The work needs a planPlans
Tests are written or judgedTest the Test
The operator explicitly asks for maximum assuranceShip or Fix

The governance dial

G0

Ordinary work

Use proportional self-checks.

G1

Real changes

Use one Builder and one independent Reviewer. Publication stays with the operator.

G2

Maximum assurance

Freeze the acceptance oracle first. Independent judges run it. G2 loads only when the operator says so.

Enforcement Layer guards

Python, pre-execution

Destructive Guardian

Denies a narrow set of catastrophic shell commands before an agent runs them. This candidate has one sterile Codex receipt. Older maintainer records separately cover Claude Code and Antigravity.

Read the Destructive Guardian documentation
Rust, final state

Change Guardian

Seals allowed change classes, then rejects unclassified repository changes and stale receipts. Version 4 is source only. Live hook dispatch is not claimed.

Read the Change Guardian documentation

Live guard proof

The same harmless command ran in two sterile Codex profiles. Without the Enforcement Layer, the marker printed before the missing sentinel failed. With the Enforcement Layer, the hook denied the command before execution and the marker was absent.

This proves one Codex 0.154.0 sterile-profile run. It does not prove that the guard is installed in your profile or that it covers general Bash.

Install boundaries

The plugin installs only the six Instruction Layer skills. It does not install, wire, or activate either guard.

Install each Enforcement Layer guard from its own README. The Rust guard has no prebuilt binary or supported native target in version 4.

Read the complete installation guide