When a team member has a Reviewer role (e.g., Tester, Code Reviewer, Lead), they may approve or reject work from other agents. On rejection, the coordinator enforces strict lockout rules to ensure the original author does NOT self-revise. This prevents defensive feedback loops and ensures independent review.
The original author is locked out. They may NOT produce the next version of that artifact. No exceptions.
A different agent MUST own the revision. The Coordinator selects the revision author based on the Reviewer’s recommendation (reassign or escalate).
The Coordinator enforces this mechanically. Before spawning a revision agent, the Coordinator MUST verify that the selected agent is NOT the original author. If the Reviewer names the original author as the fix agent, the Coordinator MUST refuse and ask the Reviewer to name a different agent.
The locked-out author may NOT contribute to the revision in any form — not as a co-author, advisor, or pair. The revision must be independently produced.
Lockout scope: The lockout applies to the specific artifact that was rejected. The original author may still work on other unrelated artifacts.
Lockout duration: The lockout persists for that revision cycle. If the revision is also rejected, the same rule applies again — the revision author is now also locked out, and a third agent must revise.
Deadlock handling: If all eligible agents have been locked out of an artifact, the Coordinator MUST escalate to the user rather than re-admitting a locked-out author.
MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.
Discovery
17 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 6 distinct layouts observed: .copilot/skills/*/SKILL.md, .github/skills/*/SKILL.md, */skill.md, .squad/*/skill.md, skills/*/SKILL.md, */SKILL.md.
Authorship
1 of 17 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.
Duplicates collapsed
3 mirror copies folded into their canonical skill — republished for Squad, Squad Templates. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.
Issue colours
Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
Heading repairs
None needed in this skill: the outline was already valid.
Spec compliance
6 editorial notes across 3 of 17 skills. They are printed in the margin of each skill rather than as errors here.
Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
Signal
Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.
Agent surfaces
The whole issue is available as one markdown document at /microsoft/waza.md, and each skill at its own .md URL.
Publication
Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.