second-opinion
Installation
SKILL.md
Second Opinion
Protocol
1 — Brief the subagent
If there's no concrete anchor (specific edit, chosen option, phrasing under review), stop and tell the user this skill needs a candidate to critique.
Otherwise, spawn one subagent — or more if the user explicitly asks for multi-reviewer (R0/R1/R2) — with a briefing containing exactly:
- Context — file path(s), surrounding code/prose, constraints.
- Problem statement — what the proposal is trying to solve and why this approach.
- The proposed fix — verbatim.
- What's already ruled out — alternatives the user has considered and rejected, with the reason.
- The 3-part ask.