CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/coding-policy

General-purpose coding policy for Baruch's AI agents

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

agent-team-operation.mdrules/

alwaysApply:
Yes
description:
Standalone versus Herdr team round — the mode test, and where the team-round contract lives

Agent Team Operation

Two Modes

  • Standalone — one agent working a task on its own, with no Herdr session around it. HERDR_ENV is unset
  • Herdr team round — a nonworking foreman dispatching work across separate Herdr worker panes. HERDR_ENV is set
  • Read HERDR_ENV to tell the modes apart
  • Never infer the mode from how large or careful the task is
  • Every section of skills/herdr-foreman/references/team-operation.md governs a Herdr team round only
  • In standalone mode none of it applies — no roles, no rotation, no briefs, no report files, no worktree-per-writer, no judge seat
  • A standalone agent does the task directly
  • A standalone agent never simulates the roles, the briefs, or the reports
  • Standalone work is still governed by every other rule in this plugin

Foreman Role

  • This section governs a Herdr team round only
  • The foreman is a nonworking foreman
  • It assigns the work
  • It supervises the crew
  • It accepts or rejects what the crew delivers
  • In a team round the foreman dispatches the task work and never executes it itself
  • The foreman's own execution covers reading the shared checkout, this plugin's owner scripts, and the foreman-owned records those scripts write
  • Foreman-owned records are the task ledger, retrospective notes, attention items, and working memory
  • A request whose answer is a task deliverable is dispatched, whatever its size, and whether or not the foreman already knows the answer
  • A task deliverable is a written artifact, a recommendation, an assessment, or a repository edit, other than a foreman-owned record
  • A request the foreman could answer only after a lookup, a file inspection, or research is dispatched
  • A bounded question routes to a specialist consultation under Team Composition
  • A review of code already pushed for the task routes to the reviewer responsibility under Review Before PR
  • A review of any other existing code routes to a read-only consultation under Specialist Consultations
  • A repository edit routes to the developer responsibility under Writers and Checkouts
  • A shortfall of eligible workers is a staffing decision to record under Team Composition, never authorization for the foreman to execute

Team Round Contract

  • A Herdr team round follows skills/herdr-foreman/references/team-operation.md in full
  • That file is a must-read before any team-round action
  • Its sections bind a team round as rule content
  • The foreman loads it through skills/herdr-foreman/SKILL.md
  • Every worker brief names it as a required read
  • A section this rule names without a path (Team Composition, Review Before PR, Specialist Consultations, Writers and Checkouts) lives in that file

README.md

tile.json