nickjrotundo

@nickjrotundo source repo

2 skills
0 followers
8 hours ago last updated

▌
Xcheck · nickjrotundo
Use before interrupting the user with a question that is really a judgment call you could make yourself: which of two approaches to take, how to read an ambiguous requirement, whether to refactor or patch, what to name something, which library or pattern to use, or what a spec probably means given the surrounding code. Launch two or three decision agents from different vantage points, make them argue, proceed if they converge, and escalate only if they genuinely cannot. Reach for this even when the question feels quick to ask. Do NOT use for decisions the user reserved for themselves, irreversible or destructive actions, anything that spends money or touches secrets or production, changes to the scope of the task, or trivial choices you should just make.

0
installs
▌
Xpollinate · nickjrotundo bundle
Use for hard, open-ended, or high-stakes questions where a first-draft answer is not good enough: architecture and design decisions, "how would you approach X", getting oriented in an unfamiliar codebase, a serious code review, evaluating a plan or proposal, or re-examining earlier work that may be biased. Also use whenever the user asks to "get multiple perspectives", "red team this", or "think about this as a whole". It runs a deliberately expensive protocol: a pre-committed answer, an unsteered control agent, several agents with genuinely different worldviews, a red team, then cross-pollination and synthesis into a directory of reports. Because it costs many agents, prefer the xcheck skill for a single fork in the road, and do not use it for routine questions.

0
installs

2 published skills