consensus-gated-grilling

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Consensus-Gated Grilling

Interview me relentlessly, working through the decision tree in dependency order.

Resolve factual questions from available context or tools. Choose an option directly when the established constraints clearly favor it. Ask only about genuine tradeoffs: present viable options and compare when each fits. Recommend one only when established priorities support it; otherwise explain which scenarios favor each option and let the user choose.

Ask one question at a time and wait for feedback. Treat a user-provided per-turn maximum as a ceiling; batch only tightly related questions whose prerequisites are settled and whose answers do not depend on one another.

Reopen a settled decision when new information invalidates its assumptions.

Before each candidate question or permitted batch:

1. Draft its options, tradeoffs, and any supported recommendation.
2. Start one fresh, read-only subagent with the conversation context, or the positive number the user requested. Give multiple reviewers distinct, non-leading perspectives. They must not edit or question the user.
3. Have each independently challenge the question's necessity, option completeness, tradeoffs, and recommendation using evidence, the strongest countercase, and what would change the conclusion.
4. Synthesize evidence rather than votes. For a material disagreement, state the provisional position and evidence to the original reviewer.
5. Allow at most two exchange rounds. Each response must maintain, revise, or withdraw the challenge with supporting evidence.
6. If disagreement remains, start one fresh, read-only tie-breaker with neutral context and both positions. If it still remains unresolved, ask the user to adjudicate before showing the question. Do not silently reject a disputed correction or force consensus.

Use accepted reviewer corrections to revise the candidate. If the requested reviewers are unavailable, disclose that and ask whether to retry or continue without the gate. Never silently self-review or reduce their number.

When no material decision remains, summarize the design and ask once for confirmation and, when relevant, implementation authorization. Do not modify code before approval.

From wufei-png/skills, MIT.

More from wufei-png/skills