tenth-manlisted
Install: claude install-skill vencx/decimo-hombre
# Tenth man
The tenth-man rule: when nine people agree, the tenth is obliged to look for why they are wrong. Here the tenth is a separate Claude session with a strong advisor that **does not share your context**: it only sees the document and a brief. That isolation is the point; a review in your own session inherits the same blind spots that wrote the plan.
## When to invoke it
Worth it when being wrong is costly to undo (production, money, customer data, migrations, agents that talk to customers on their own) and the document is already written. One per document: requirements and technical plan are two separate reviews.
| Workflow | Moment |
|---|---|
| Compound Engineering | After `/ce-brainstorm` if requirements are large or contentious; **always after `/ce-plan`**, after whatever quick review you already do (a second model, a teammate, `/ce-doc-review`), and before `/ce-work`. Repeat if the plan is heavily rewritten. |
| Superpowers | After `writing-plans` and before `executing-plans` / `subagent-driven-development`; optionally on the design coming out of `brainstorming`. |
| No framework | On the PRD/spec, RFC/ADR, migration plan, an agent's system prompt or a runbook, before work starts. |
Do not use it for: small or reversible changes, bugs (diagnose first), code already written (`code-review`), or as a replacement for a quick review: the isolated auditor finds what shared context hides, not the obvious.
## Modes
| Mode | Where it runs | When |
|---|---|---|
| `clo