JasonColapietro/suede-creator-skills / skills/suede-agent-teams
suede-agent-teams
VerifiedSuede Agent Teams Skills. Use when asked to "split this work across agents" or run coordinated shared changes in lanes with exclusive file ownership, collision checks, worktrees, rollback plans and evidence handoffs; also supports bounded contribution programs. NOT FOR: one bundled code DAG (suede-graph-flo-xr), diff review (suede-code), CI wiring (suede-ci-gate), or choosing one skill (suede-workflow-skills).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.5 KB |
| SKILL.md | skill md | 18.4 KB |
| agents/openai.yaml | config | 735 B |
| references/execution-loop.md | markdown | 4.7 KB |
| references/incident-and-rfc-templates.md | markdown | 1.9 KB |
| references/public-contribution-program.md | markdown | 13.6 KB |
| references/scenario-templates.md | markdown | 8.1 KB |
| references/worked-contract.md | markdown | 2.0 KB |
| scripts/contribution-ledger.mjsexecutable | script | 51.1 KB |
references/worked-contract.md
View on GitHub# Worked delivery contract
This synthetic scenario demonstrates the expected artifact shape; its numbers and outcomes are example inputs, not measured customer results.
## Input
Two changes are requested: API validation in src/api.ts and UI empty states in src/view.tsx. Both need src/types.ts. The goal is a draft PR, not deployment.
## Expected output
Return a Team Contract and ownership table. Assign src/types.ts to a serialized interface lane first; record its exported type and test before dispatching API and UI builders. Give each builder exclusive paths, acceptance criteria, dependencies, branch/worktree and done evidence. Name a reviewer and rollback point. Record draft-PR authority separately from merge/deploy authority.
## Failure case
A UI builder requests a change to src/api.ts while the API lane is active. Mark the dependency, route the request to its owner and sequence any transfer. Do not allow both lanes to edit the same file to meet a deadline.
## Validation
Compare actual changed paths with the ownership table, inspect the interface contract consumed by both lanes, and run the integrated tests at the final commit. A worker summary is not proof that the combined branch passes.
## Coverage and routing
Suede agent-team orchestrator, the method behind multi-agent automation: split complex work into coordinated lanes with explicit file ownership, WIP collision detection, quality gates, escalation thresholds, rollback plans, and handoffs that prove what shipped. Use when one shared change needs safe parallel ownership across builders and reviewers, when a lane map must be resolved before anyone opens a file, or when running a repeatable public-repository contribution program with issue scoring, atomic task leases, isolated worktrees, and explicit publication authority. NOT FOR: one repo change a bundled DAG can run end to end (use suede-graph-flo-xr); reviewing or grading a diff (use suede-code); CI, branch protection, or merge-gate wiring (use suede-ci-gate); picking which single skill fits a request (use suede-workflow-skills).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |