skills.rest
atmigtnca
atmigtncaCOMMUNITY
Explore all skills by this author →
GitHub

trace

Orchestrate competing tracer hypotheses to explain observed runtime results.

1|Updated Mar 22, 2026
Search Tags:#debugging#trace#evidence#tracing#hypotheses#causal-analysis#team-mode
One-click install
npx skills add https://github.com/atmigtnca/sidep-ops --skill trace-atmigtnca
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/atmigtnca/sidep-ops/tree/main/skills/trace
Command: npx skills add https://github.com/atmigtnca/sidep-ops --skill trace-atmigtnca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explains why observed results happened by orchestrating competing tracer hypotheses in Claude built-in team mode.

Core Features & Use Cases

  • Restate the observation, generate competing hypotheses, gather evidence in parallel, rank the explanations, and propose the next discriminating probe.
  • Team-mode orchestration with three tracer lanes by default for robust hypothesis testing.
  • Enforces a structured evidence hierarchy, cross-check lenses, and a formal worker and leader synthesis contract.
  • Use cases include runtime bugs, performance anomalies, architecture postmortems, and config/orchestration behavior explanations.

Quick Start

Restate the observed result, generate three competing hypotheses, and run parallel tracer lanes to reveal the strongest explanation.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I debug runtime bugs using competing hypotheses?▼

Debug runtime bugs by restating the observed result, generating three competing hypotheses, and running parallel tracer lanes to gather evidence and reveal the strongest causal explanation.

What is the best way to find the root cause of a performance anomaly?▼

Trace performance anomalies by orchestrating evidence-driven testing across competing hypotheses, ranking the explanations, and proposing a discriminating probe to identify the root cause.

How does causal analysis work for architecture postmortems?▼

Causal analysis for architecture postmortems works by applying a structured evidence hierarchy and cross-check lenses across parallel tracer lanes to synthesize why observed results happened.

Can I use team mode to investigate config or orchestration behavior explanations?▼

Yes, you can investigate config or orchestration behavior explanations by enforcing a team-based workflow with three default tracer lanes to test competing hypotheses in parallel.

When should I use evidence-driven tracing instead of standard debugging?▼

Use evidence-driven tracing for ambiguous, causal, evidence-heavy questions like runtime bugs and performance anomalies, where standard debugging struggles to explain why observed results happened.

Related Skills

Explore More Software Engineering Skills→
Pryma-TechPryma-Tech

trace

Orchestrate competing tracer hypotheses to explain observed Claude team-mode results.

Community
Advanced
RobinNorbergRobinNorberg
5

trace

Orchestrate competing tracer hypotheses in Claude team mode to explain observed results.

Community
Advanced
OliverOuyangOliverOuyang
1

trace

Orchestrate parallel hypothesis tracing and evidence collection for causal failure analysis.

Community
Advanced
INNERJOINTINNERJOINT

trace

Trace causal observations to rank competing explanations for system behavior.

Community
Advanced