Power moves

Things people miss for months.

Review a diff properly. /hyperpower:review partitions a large diff, runs a reviewer per slice, then has a second agent try to disprove each finding. What reaches you is marked CONFIRMED or PLAUSIBLE, so you are not reading a list of maybes.

Put a decision to a vote. /hyperpower:council "<question>" asks the departments that own a question to answer independently, then synthesises. Use it for something expensive to reverse: a schema shape, a public interface, a dependency you will live with. Skip it for anything a later commit undoes cheaply.

See where the money went. /hyperpower:cost --by stage breaks a run down by stage, agent or model. Cache reads get their own column, because they dominate the token count and cost a tenth of fresh input.

Watch a run from another window. /hyperpower:status reports what the current run has done so far.

Check the setup before blaming the tool. /hyperpower:doctor says which checks can actually run here and which are missing a command or a binary.

Full reference for every command, check and eval field is on the docs page.