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/incident-and-rfc-templates.md
View on GitHub# RFC and Post-Mortem Templates
The stationery for the two documents this skill occasionally asks a lane to write.
The rules that decide *whether* to write one (the RFC-required list, the
`accepted`-before-any-builder gate, the P0-P3 severity definitions, and the
required/optional/skip rule for post-mortems) stay in the `suede-agent-teams`
SKILL.md next to their triggers. Read this file when you are about to author one of
the two documents, and fill every section.
## RFC template
```
RFC: [Title]
Date: [date]
Status: draft | accepted | superseded | withdrawn
Deciders: [who has final say]
## Problem Statement
One paragraph: what is broken, missing, or suboptimal? Include the user or system impact.
## Proposed Solution
What we will build or change. Be specific about interfaces, data shapes, and behavioral contracts.
## Alternatives Considered
2–3 alternatives with the reason each was not chosen.
## Risks
What could go wrong with the proposed solution? How is each risk mitigated?
## Success Criteria
How will we know this worked? Observable, measurable signals.
## Decision Record
[filled in after consensus] Accept / Modify / Reject + reason.
```
## Post-mortem template
Keep it blameless: focus on systems, not individuals.
```
Post-Mortem: [Brief title]
Date of incident:
Duration:
Severity: P0 (total outage) / P1 (primary path broken) / P2 (degraded) / P3 (cosmetic)
Author(s):
## Timeline
[time]: [event]
[time]: [detection]
[time]: [first response]
[time]: [resolution]
## Impact
Users affected:
Revenue impact (if known):
Data integrity: affected / not affected
## Root Cause
One sentence: the direct technical cause.
## Contributing Factors
The systemic conditions that made this possible. (What allowed the root cause to reach production?)
## What Went Well
Things that helped detect or contain the incident faster.
## Action Items
| Action | Owner | Due |
|---|---|---|
| ... | ... | ... |
Status: open / closed
```
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 |