trace

Orchestrate evidence-driven tracing to evaluate competing hypotheses for ambiguous results.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill trace-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/trace
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill trace-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace orchestrates evidence-driven reasoning to resolve ambiguous results by organizing competing hypotheses, gathering supporting and conflicting evidence, and ranking explanations to identify the most plausible root cause.

Core Features & Use Cases

  • Restate observations and generate multiple, deliberately different hypotheses.
  • Spawn 3 tracer lanes by default in Claude built-in team mode, each pursuing evidence for and against its lane.
  • Gather and rank evidence strength, identify the critical unknown, and propose the best discriminating probe.
  • Run rebuttal rounds to test leading explanations and surface convergence or separation notes.
  • Apply to runtime bugs, performance regressions, architecture reviews, and experimental results requiring careful inference.

Quick Start

Provide a concrete observation and initiate the team-mode tracing workflow.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I debug ambiguous runtime issues with multiple possible root causes?

Debug ambiguous issues by restating observations and generating multiple competing hypotheses. Evaluate each in parallel tracer lanes, gathering supporting and conflicting evidence, ranking explanations, and running rebuttal rounds to converge on the most plausible root cause.

Can I use team mode for tracing performance regressions and architecture reviews?

Yes, team mode tracing applies to performance regressions, architecture reviews, and experimental results. The workflow evaluates multiple explanations in parallel using three default tracer lanes to weigh evidence for and against each hypothesis.

How do I evaluate competing hypotheses when diagnosing system failures?

Evaluate competing hypotheses by spawning parallel tracer lanes that gather evidence for and against each explanation. Rank evidence strength, identify critical unknowns, propose discriminating probes, and run rebuttal rounds to test leading explanations before synthesis.

What is the best way to weigh multiple explanations for experimental results?

The best way to weigh multiple explanations is evidence-driven reasoning that generates deliberately different hypotheses. Gather evidence for and against each across parallel lanes, rank explanations by evidence strength, and run rebuttals to surface convergence or separation before synthesizing.

Do I need Claude built-in team mode to run evidence tracing workflows?

Yes, evidence tracing workflows require Claude built-in team mode to spawn three default tracer lanes. Each lane independently pursues evidence for and against its assigned hypothesis, enabling parallel evaluation, ranking, and rebuttal rounds before synthesis.

How do I identify the critical unknown when debugging ambiguous results?

Identify the critical unknown by gathering and ranking evidence strength across competing hypotheses. Once evidence is ranked, propose the best discriminating probe that separates leading explanations, then run a rebuttal round to test convergence before final synthesis.