Stats
Actions
Tags
From plan-consensus
Run plan-consensus skill — Claude↔Codex ping-pong review on a plan file until consensus or impasse
How this command is triggered — by the user, by Claude, or both
Slash command
/plan-consensus:plan-consensusThe summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the `plan-consensus` skill on the plan file specified in the arguments. Arguments: `$ARGUMENTS` (typically a path to a markdown plan file, optionally followed by `max_rounds=N` or `model=...`). If no path was given, ask the user which plan file to review. Then follow the skill's procedure exactly: snapshot the plan, loop Codex review → Claude response → impasse/consensus check, and write all artifacts under `<plan-dir>/plan-consensus/`.
Invoke the plan-consensus skill on the plan file specified in the arguments.
Arguments: $ARGUMENTS (typically a path to a markdown plan file, optionally followed by max_rounds=N or model=...).
If no path was given, ask the user which plan file to review.
Then follow the skill's procedure exactly: snapshot the plan, loop Codex review → Claude response → impasse/consensus check, and write all artifacts under <plan-dir>/plan-consensus/.
npx claudepluginhub senojed/plan-consensus --plugin plan-consensus