repo-decide

Codex form of the /repo:decide command. Other commands appear as $repo-<verb> skills. Helper scripts and .claude/ paths below are relative to the repository root and exist when the Claude Code surface is installed alongside this one.

$repo-decide — Ranked Operator Decisions

When work is blocked on a decision that belongs to the operator (cost, an access grant, a policy change, something irreversible, a call about another person's system), don't ask an open question and don't bury the choice in a paragraph. Lay out the options best to worst, mark the one you recommend, and give the reason each option ranks where it does. Then the operator can answer "Q1: 1, Q2: 3" instead of re-deriving the tradeoffs you already worked out.

This command only drafts the questions. It does not decide anything. Presenting the draft in the session needs no confirmation. Posting it anywhere else (a chat room, an issue, a PR) is outward-facing and follows the same confirm-first rule as [[followups]], unless the user's own invocation already said where to post.

Usage

$repo-decide                     # Draft ranked questions for the decisions this session is blocked on
$repo-decide "<topic>"           # Draft for one named decision
$repo-decide --post              # Draft, confirm, then post where this project routes operator questions

Steps

1. Collect only real operator decisions

Go through the session (and the issue or PR at hand) for choices that are genuinely the operator's. Leave out anything you can settle from the code, the docs, or a sensible default. Settle those yourself and say so in one line. A decision belongs to the operator when it involves:

• money or a standing cost;
• granting, widening, or minting a credential or access;
• changing a written policy or making an exception to it;
• an irreversible or outward-facing action (publishing, deleting, migrating);
• a system, account, or budget someone else owns.