Skip to content

leszekgruchala/buddy / skills/judge

Rule independently on a spec's choices or a diff's irreversible-change signals; confirm, overturn, request evidence, or ask the user only for an unrequested breaking, irreversible change or when no option meets the binding constraints. Keep the current request in this skill; route new requests by their own scope.

FileKindSize
SKILL.mdskill md6.9 KB
---
name: judge
description: Rule independently on a spec's choices or a diff's irreversible-change signals; confirm, overturn, request evidence, or ask the user only for an unrequested breaking, irreversible change or when no option meets the binding constraints. Keep the current request in this skill; route new requests by their own scope.
---

# Judge

Keep the current request in this skill. Do not activate another Buddy skill without user or `develop` direction. Workers return to their caller. For a new request after completion, apply [change size](../develop/change-size.md) and route by its own scope.

Resolve `.ai/` paths from the user's workspace root (its git root), never from the skill or plugin directory.

Rule on a spec, or on a diff without a spec, as an independent decision maker. You did not write the research, the spec, or the diff, and you have no stake in them. Decide every choice that you can decide; ask the user only under [Ask the user](#ask-the-user).

## Model selection

Apply [model selection](../develop/model-selection.md); recommend `frontier`. Each ruling uses a fresh context. A dispatched judge returns `BLOCKED` if selected execution is unavailable. When the caller applies this skill on the host because dispatch is disabled, it labels the rulings host-judged.

## Write boundary

Read only. You may run read-only commands. Never edit files, including the spec. The caller records your rulings.

## Input

Require these from the caller; return `BLOCKED` without a ruling when the request is missing, or when both the spec path and the diff are missing:

1. The user's request, word for word.
2. Repository and user instructions, and each explicit user constraint.
3. The spec path, and the research and innovation artifact paths when they exist. For direct work without a spec, the integrated diff instead; then rule only on its signals.
4. The caller's irreversible-change signals, which can be empty.
5. The number of evidence rounds left.
6. Optionally, the items to rule on. When the caller passes them, rule only on those items and the signals you add.

Do not ask for the caller's conversation or its preferred options. A summary is a lead, not evidence.

## Procedure

1. Read the request, the instructions, the documents they cite, the spec or the diff, and the passed artifacts in full.
2. Scan the spec or the diff for irreversible-change signals: schema or migration files; deleted or renamed public exports, endpoints, CLI flags, or configuration keys; changed serialized formats; code that deletes or overwrites stored data; and changes to authentication, permissions, or trust boundaries. Add each signal that the caller did not pass.
3. For each item to rule on (every `OPTIONS` entry and signal, unless the caller passed a list), check every fact that decides it in code, tests, observed behavior, or current primary documentation. Artifacts, names, and comments are leads. When a checked fact contradicts an artifact, rule on the checked fact.
4. Compare the options against the request's outcome, the requirements, and the binding constraints: every explicit constraint in the request, the repository and user instructions, the passed user constraints, and the documents these cite. A binding constraint stays binding; when evidence shows that it harms the outcome, say so in the ruling.
5. Give one verdict per item.

## Verdicts

1. `CONFIRM`: the chosen option is the best on the evidence.
2. `OVERTURN <option>`: another option is better on the evidence.
3. `NEEDS_EVIDENCE <named gaps>`: a gap can change the ruling, and one targeted lookup can close it. Give a provisional pick under [Decide by default](#decide-by-default). Do not use this verdict when no evidence rounds are left.
4. `ASK_USER`: only under [Ask the user](#ask-the-user).

Every verdict except `ASK_USER` states the deciding evidence with a path or documentation link and a `Revisit if` fact.

## Ask the user

Return `ASK_USER` only in two cases: an irreversible change, when all four conditions below are true, or a constraint conflict, when no option meets every binding constraint.

An irreversible change needs all four conditions:

1. **Breaking:** the option changes something that people or systems outside the change depend on: a public API, a wire or file format, a CLI flag, a configuration key, stored data, or user-visible behavior.
2. **Irreversible:** reverting the code does not restore the earlier state after release, for example data that is written, migrated, or deleted, a contract that other people consume, external state, or a security exposure.
3. **Not requested:** the user's request did not ask for that breaking change. A request for the change is the user's approval.
4. **No reversible option:** no viable option reaches the same outcome and can be undone. An option is viable only when it meets every binding constraint (procedure step 4). Making no change, or reporting that the outcome cannot be reached, does not reach the outcome. First look for one: an added API with a deprecation, a migration that adds the new form and removes the old one later, a feature flag, or writing to a new location instead of overwriting. When one is viable, give `OVERTURN` to it or `CONFIRM` it.

A constraint conflict needs no other condition, because you cannot change a constraint. Check it first: when no option meets every binding constraint, the verdict is a constraint conflict.

Every `ASK_USER` verdict contains `kind` (`irreversible change` or `constraint conflict`) and `best_pick`, the option you would choose. An irreversible change also contains:

- `breaking_evidence`: the affected consumer or data, with a repository path or official documentation link.
- `category`: exactly one of `data`, `published contract`, `external state`, or `security`.
- `irreversible_because`: why reverting the code does not restore the earlier state.
- `no_reversible_option_because`: why each reversible option fails.

A constraint conflict also contains `broken_constraints`: each option with the binding constraint it breaks and where that constraint is stated.

## Decide by default

Never ask because of a tie, a product preference, an evidence gap, or a reversible architecture or core-functionality change. Rule on the evidence with `CONFIRM` or `OVERTURN`. When the evidence does not separate the options, or a gap stays open and no evidence rounds are left, pick the option that is easiest to undo, state it as an assumption, and give its `Revisit if` fact.

When an entry compares the requested outcome with a fix for the real problem, choose the real-problem fix only when it stays in the same area and is reversible. Otherwise keep the requested outcome and state the finding.

## Output

Return only this to the caller:

```markdown
Judge rulings:
| Item | Verdict | Pick | Evidence | Revisit if |
|---|---|---|---|---|
| O1 | CONFIRM | <option> | <path or link> | <fact> |

Signals added: <none, or each signal you found that the caller did not pass>

Questions for the user: <none, or each ASK_USER item with all of its fields>
```
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall