research

Runs iterative hypothesis loops producing ledgered insights reports for open-ended questions.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill research-chughtapan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/research
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill research-chughtapan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run an iterative hypothesis loop on an open question with no known answer. Produces a ledger of claim, evidence, experiment, insight, and confidence for every round, closing with a final report of validated insights. Use when the question is open-ended ("how do X systems handle Y?", "why does Z regress under load?"), when literature review is load-bearing, or when the next step depends on answers the team does not have yet. Do NOT use when the question is a yes/no feasibility probe (route to /safer:spike) or when the work is to ship code (route to /safer:spec or /safer:implement-*).

Core Features & Use Cases

  • Iterative hypothesis loop: structure the inquiry into rounds with CLAIM, EVIDENCE, EXPERIMENT, INSIGHT, and CONFIDENCE.
  • Ledgered reasoning: preserves the reasoning trace and culminates in a final validated insights report.
  • Use Case: for open-ended questions like "how do systems handle X?" or "what is the state of the art?" when next steps depend on uncertain results.

Quick Start

Provide a clear open-ended research question and initiate the safer:research workflow to begin the iterative hypothesis loop.

Frequently Asked Questions about research

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

FAQPage Schema
How do I structure an open-ended research inquiry when there is no known answer?

Structure open-ended research inquiry using an iterative hypothesis loop that records claims, evidence, experiments, insights, and confidence levels in a ledger before producing a final validated report.

When should I use an iterative hypothesis loop for literature review instead of a feasibility spike?

Use an iterative hypothesis loop for literature review when facing open-ended questions where next steps depend on uncertain outcomes, and avoid it for yes/no feasibility probes or shipping code.

What is the best way to document reasoning and evidence for exploratory analysis?

Document exploratory analysis reasoning by maintaining a ledger that captures claims, evidence, experiments, insights, and confidence for every iteration, culminating in a final validated insights report.

How do I run a structured inquiry to find the state of the art for a specific system behavior?

Run a structured inquiry by initiating an iterative hypothesis loop that separates roles and enforces open-ended investigation to produce validated insights about specific system behaviors.

Can I use this structured research approach to answer a definitive yes or no question?

No, this structured research approach is designed for open-ended inquiry and should not be used for yes/no feasibility probes or tasks focused on shipping code.

Why does an open-ended question require a ledger of claims and confidence levels?

Open-ended questions require a ledger of claims and confidence levels to preserve the reasoning trace across iterative rounds and ensure final validated insights are grounded in structured evidence.