trace

Coordinate parallel evidence gathering to diagnose observed results across runtime and architecture problems.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Rheinmir/skills-kit --skill trace-rheinmir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/Rheinmir/skills-kit/tree/main/skills/trace
Command: npx skills add https://github.com/Rheinmir/skills-kit --skill trace-rheinmir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity and evidence-heavy questions about why an observed result occurred require a structured reasoning process. This skill provides an orchestration layer on top of the built-in tracer agent to restate the observation, generate competing explanations, gather evidence in parallel, rank the explanations, and propose the next probe that collapses uncertainty fastest.

Core Features & Use Cases

  • Orchestrates multiple tracer hypotheses in an Antigravity built-in team mode.
  • Restates the observation, extracts a target, and spawns dedicated tracer lanes to gather evidence for and against each hypothesis.
  • Ranks hypotheses by evidence strength and surfaces the current best explanation.
  • Runs a rebuttal round between top explanations and merges findings into a ranked synthesis with a critical unknown and a discriminating probe.
  • Applicable to runtime bugs, performance/latency behavior, architecture decisions, config/orchestration explanations, and experimental result tracing.

Quick Start

Use /trace in Antigravity built-in team mode to restate the observation, generate three competing hypotheses, and collect evidence in parallel.

Frequently Asked Questions about trace

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

FAQPage Schema
What is the best way to debug ambiguous runtime bugs with competing root causes?

Root-cause debugging for ambiguous runtime bugs requires a structured workflow that generates competing hypotheses, gathers evidence in parallel, and ranks explanations by evidence strength to collapse uncertainty.

How do I trace performance latency issues when the cause is unclear?

Tracing performance latency involves restating the observation, spawning dedicated tracer lanes to collect evidence for and against multiple hypotheses, and running a rebuttal round to synthesize a discriminating probe.

Can I use team mode to coordinate evidence gathering across multiple hypotheses?

Yes, team mode orchestrates multiple tracer hypotheses by extracting a target, spawning dedicated lanes for parallel evidence gathering, and merging findings into a ranked synthesis with a critical unknown.

Does structured trace investigation work for architecture decisions and configuration orchestration?

Structured trace investigation applies to architecture decisions and configuration orchestration by enforcing evidence-driven reasoning to diagnose why an observed result occurred across ambiguous causal problems.

How to diagnose experimental results when facing evidence-heavy causal questions?

Diagnosing experimental results requires restating the observation, generating three competing explanations, collecting evidence in parallel, and proposing a final discriminating probe that collapses uncertainty fastest.