research-decide

Runs a research, adversarial verification, decision, delegation, and documentation loop for high-stakes tasks.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill research-decide-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-decide
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/research-decide
Command: npx skills add https://github.com/gmolike/Claude-Template --skill research-decide-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? High-stakes or uncertain engineering work often fails because agents trust memory on fast-moving APIs, guess decisions that belong to the user, implement inline instead of delegating, or declare done on green tests alone. This Skill enforces a disciplined operating loop that prevents those failure modes. ## Core Features & Use Cases - Ground-truth research: Verifies uncertain claims against primary sources (official docs, actual source code) using parallel read-only agents instead of relying on recall. - Adversarial verification: A second independent pass tries to refute every load-bearing finding, defaulting to the pessimistic reading unless docs are explicit. - Structured decision surfacing: Presents genuine user decisions one at a time, each with a recommended option and stated trade-off. - Delegated implementation with verification: Splits work into disjoint slices for parallel writers, then runs the real gate (build, full tests, actual behavior) before documenting and shipping. - Use Case: When upgrading a fast-moving library or changing shared config with real blast radius, invoke this loop to verify the API against live docs, surface migration choices to the user, delegate the code changes, and confirm behavior before release. ## Quick Start Ask the agent to run the research-decide loop on your task, for example by invoking /research-decide migrate the API client to the new library version.

Frequently Asked Questions about research-decide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a fast-moving library API before implementing changes?

Verify against primary sources such as official documentation and the actual source code rather than memory. Fan out read-only agents over disjoint questions, then run an adversarial second pass that tries to refute each load-bearing finding before acting on it.

When should I use a research and decision workflow instead of just coding?

Use it when the surface is uncertain or fast-moving, a genuine decision only the user can make exists, or the change has real blast radius such as shared config, releases, or many files. Skip it for small, fully specified, reversible single-file work.

How should AI agents handle decisions that belong to the user?

Surface one decision per round as an explicit question with a recommended option and the trade-off stated plainly. Do not guess values you cannot infer, and do not re-ask what is already settled.

Why are green tests not enough to call a change done?

Tests passing does not prove actual behavior. Run the real gate: the build, the full test suite, and the actual behavior by driving the flow or grep-proving the claim, then fix what verification surfaces before documenting and shipping.

What are the limitations of an orchestrated research loop?

The loop adds ceremony and latency, so it is wasteful for trivial, fully specified, reversible tasks. It also depends on access to primary sources; without live docs or source code, verification quality degrades.