investigate

Guide evidence-based debugging through a five-phase workflow with root-cause confirmation.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/tcytan/tecton --skill investigate-tcytan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/tcytan/tecton/tree/main/.claude/workflow-skills/investigate
Command: npx skills add https://github.com/tcytan/tecton --skill investigate-tcytan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically investigate an issue and prevents premature fixes by enforcing root-cause confirmation before implementation.

Core Features & Use Cases

  • Iron Law Root Cause Gate: Blocks implementation unless the root cause is clearly identified with high confidence and supporting evidence.
  • 5-Phase Investigation Workflow: Guides you through reproduction, evidence gathering, pattern analysis, hypothesis testing, and final verification.
  • Operational Variables for Traceability: Uses variables like root_cause and confidence to structure findings and decision outcomes.
  • Use Case: When a production bug appears intermittent, run the workflow to narrow the responsible module, validate a hypothesis with a minimal reproduction, and only then implement a fix with regression coverage.

Quick Start

Use the command chain_loader start --chain=ccw-investigate to run the full investigation flow with root cause confirmation enforced.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I find the root cause of an intermittent production bug without jumping to premature fixes?

Root cause analysis isolates confirmed causes before implementation by enforcing an Iron Law gate, requiring high confidence and supporting evidence to block premature fixes.

What is a structured debugging workflow for validating hypotheses during incident response?

A structured debugging workflow guides you through five linear phases: reproduction, evidence gathering, pattern analysis, hypothesis testing, and final verification to validate root causes.

How do I start an evidence-based investigation for a software system incident?

Start an evidence-based investigation by running the chain_loader command to enforce a linear workflow, tracking variables like root_cause and confidence to control execution paths.

Can I implement a code fix before confirming the root cause of an issue?

No, the Iron Law Root Cause Gate blocks implementation unless the root cause is clearly identified with high confidence and supporting evidence gathered during investigation.

What's the best way to document findings and decision outcomes during root cause analysis?

Document findings and decision outcomes during root cause analysis by using operational variables like root_cause and confidence to structure evidence and trace execution paths across phases.

When should I use a guarded investigation workflow instead of immediate incident response patching?

Use a guarded investigation workflow for software and system incidents requiring deep investigation, hypothesis validation, and structured documentation to prevent premature implementation.