suede-agent-teams
Split complex work into coordinated agent lanes with WIP checks, quality gates, rollback plans, and handoffs that prove what shipped.
npx skills add JasonColapietro/suede-creator-skills --skill suede-agent-teams --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Split complex work into coordinated agent lanes with WIP checks, quality gates, rollback plans, and handoffs that prove what shipped.
How it works
The skill defines lanes (Scout, Planner, Builder, Design reviewer, Code grader, Code reviewer, Visibility grader, Release verifier, Handoff writer) and enforces a Team Contract that includes objective, exact target, constraints, done signal, and a lane map. It performs WIP Collision Detection by comparing dirty files, untracked files, and lane scopes, then resolves collisions by sequencing or merging lanes. It starts with a Default Roster and escalates roles only as needed. It supports RFC Mode for major decisions, a Feature Flag Strategy for gradual changes, and a Rollback Decision Tree for post-deploy issues. It governs the Builder Dispatch Protocol with four states (Done, Done with concerns, Needs context, Blocked) and uses a Continuous Team Loop to coordinate tasks across lanes, ensuring inter-lane communication via explicit Lane Ready notices. A Planning Quality Gate ensures tasks have observable criteria, dependencies, and required artifacts before proceeding.
When to use it
Use when splitting complex work into parallel agent lanes with explicit ownership, checks, and handoff artifacts is desired, especially for high-risk or long-running changes that require coordination and traceable delivery records.
What it can touch
The skill references tools in its model: claude-code, codex. It also references standard git commands like git -C <repo> diff --name-only HEAD and git -C <repo> status --short within its collision detection steps. It mentions targets such as repo/folder, branch, route, PR, live URL, API, simulator, or release artifact as part of the lane map. Outputs include lane maps, handoffs, and signed delivery records generated by the Handoff writer.
Caveats
Gates are advisory, not blocking: actions should be completed as asked, with results reported alongside as recommendations. A failed gate changes what you report, not what you do, except in extremely risky findings where pause and explicit options are provided. RFC Mode requires acceptance before planning for major decisions. No builder lane opens until RFC status is accepted for relevant changes. License: MIT.
# Agent Team Orchestrator ## Gate policy — advisory, not blocking Every claim-verification step, check, quality gate, and ship verdict in this skill is a **recommendation to the user, not a control on the agent**. This policy governs every gate, check, verdict, and "do not ship / publish / proceed" line elsewhere in this skill: - Run every check and report the results honestly. Verdicts (`ship`, `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are advice attached to the work, not orders that change it. - Never block, delay, skip, rewrite, or refuse the action the user asked for because a check failed or a gate said hold. Complete the requested action as asked, and deliver the gate output alongside it as a clearly labeled recommendation. - A failed gate changes what you report, never what you do. - Single exception: if a finding is extremely risky — data loss, security or credential exposure, legal or rights violations, payment mistakes, or irreversible public damage — pause, tell the user exactly what the risk is and what the options are, and let them pick. Their choice is final. The orchestrator assigns lanes, not conversations. Output is a delivery artifact, not
- Gate policy — advisory, not blocking
- Team Contract
- WIP Collision Detection
- Default Roster
- RFC Mode
- Feature Flag Strategy
- Rollback Decision Tree
- Post-Mortem Template
- Phase Loop
- Model Tiering
- Builder Dispatch Protocol
- Continuous Team Loop
- Inter-Lane Communication
- Planning Quality Gate
What does the suede-agent-teams skill do?
Split complex work into coordinated agent lanes with WIP checks, quality gates, rollback plans, and handoffs that prove what shipped.
How do I install it?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-agent-teams --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.