Agent orchestration

Wire complex changes into coordinated lanes with a signed handoff.

Suede Agent Teams assigns lanes, not conversations. It detects work-in-progress collisions before any builder opens a file, runs an RFC before high-blast-radius changes, gates the work through quality and adversarial review, and closes with a handoff that will not sign off until every required field is present and truthful.

Install the skill View skill folder

Public install command

This is the public route. It installs from GitHub as a standard Codex skill folder.

python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
  --repo JasonColapietro/suede-creator-skills \
  --path skills/suede-agent-teams

Restart Codex after installing the skill.

The default roster

Start with Scout, Builder, and Handoff Writer. Add a role only when a gate needs it.

  • Scout maps the repo, current state, dirty files, live routes, and likely blast radius.
  • Planner turns requirements into verifiable tasks with acceptance criteria and dependencies.
  • Builder makes narrow changes inside the existing system, in assigned files only.
  • Design reviewer, code grader, and code reviewer attach when design or code risk is present.
  • Release verifier owns build, deploy, live and API truth, and public-claim accuracy.
  • Handoff writer produces a signed delivery record, held if any required field is missing.

Where it fits

Reach for it when a change is too broad, too risky, or too release-bound for one lane: shared interface changes, auth and payment paths, data migrations, and public launches. For high-risk work it keeps the builder and the reviewer separate so the implementation gets a second, adversarial set of eyes.

Use the smallest loop that can finish the work, and escalate deliberately when the task is broad, risky, release-bound, or you ask for max agent teams.

Collision detection and quality gates

Before any parallel lanes open, the orchestrator collects every dirty and untracked file, maps each lane's scope, and flags a collision when two lanes, or a lane and existing work, would touch the same path. No builder opens a file outside its assigned lane map.

RFC modeShared interfaces, schema, auth, payment, and public API changes require an accepted RFC before a builder opens.
Feature flagsRisky or non-revertible changes ship behind a flag with a removal date set at creation and a staged ramp.
Rollback treePre-agreed decisions: roll back immediately on data loss or security exposure; hold and investigate on degraded performance.
Adversarial reviewOne lens asks whether it works; another asks how it fails in production, release, abuse, accessibility, and handoff.
Escalation protocolRepeated fix cycles, unknown-severity security findings, and cost spikes stop the loop and surface for sign-off.
Status vocabulary"Changed locally" is not "verified locally"; "deployed" is not "verified live." States do not skip.

Scenario templates

Pre-built rosters for common high-risk deployments. Adjust only the named target.

  • Auth rewrite: RFC and flag required; builder touches auth files only; release verifier confirms in production.
  • Payment integration: idempotency, webhook signatures, and decline and replay paths tested before ramp.
  • Public launch review: review-only roster across design, visibility, links, secrets, and claim truth.
  • Data migration: rollback script defined and tested in staging before production promotion.
  • Performance audit: rank fixes by impact, implement only the ranked set, confirm no regression.

Handoff that won't fake done

The delivery record is held until every field is present and truthful: exact target, every changed file, every command with output, observable verification, a real status, the single next step, and every caveat.

Target:
Changed:
Verification:
Caveats:
Status:
Next:

Best prompts

Use $suede-agent-teams to plan lanes for this multi-file change. Run WIP collision detection first and give me the lane map.
Use $suede-agent-teams with the auth-rewrite template. Require an RFC and a feature flag before any builder opens.
Use $suede-agent-teams to coordinate this public launch review and hold the handoff until every field has evidence.

Safety boundary

No lane may override an escalation threshold by re-scoping the task or declaring a condition resolved without sign-off. Release truth, meaning build, deploy, live and API behavior, and public claims, is owned by the release verifier before any completion claim.

The orchestrator organizes the work; it does not invent verification, deploy status, or approved claims.

Cue Suede

Feedback can happen mid-workflow or at the end. Say Cue Suede to ask for choices: change something, preserve what worked so the agent can mimic it later, or keep as-is by saying nothing.