groupworklisted

# groupwork A second agent on the work. The patterns are the product; the CLI underneath is swappable. The reason this is not a wrapper around `codex exec` is the **withholding rule**. A second opinion that has already been told your conclusion is not a second opinion, it is agreement with extra steps. So every pattern refuses to carry your view at all, and the refusal is enforced in code. ## Pick the pattern first | Pattern | Use it when | It is not told | |---|---|---| | `red-team` | You want the idea killed if it deserves killing | Your evidence, and by default the repository itself | | `second-opinion` | You have a view and want one reached without it | Your conclusion, draft or findings | | `verify` | Work is finished and about to ship | Whether anyone thinks it passes | | `panel` | A hard call where the trade-off is the answer | Your view, and each other's answers | Two that look alike and are not: `red-team` is handed a claim and told to break it, deliberately starved of the material so its attack cannot inherit your blind spots. `second-opinion` is handed the material and asked to reach its own judgement. Use `red-team` on an idea, `second-opinion` on a document. For thinking out loud with a peer who sees your view, use a persistent advisor session instead. Every pattern here withholds your view, because that is what makes its answer worth citing. Do not burn a run on something cheap. Naming, style, "what does this code do" - read it yourself. These calls are s