tribune

Convert bug symptom reports into evidence-backed diagnosis packets.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill tribune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tribune
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/tribune
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill tribune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague bug symptoms into verifiable findings with an evidence-backed diagnosis, reducing guesswork and surfacing the root cause for an actionable fix.

Core Features & Use Cases

  • Guided eight-phase workflow (Phase 0 through Phase 8) that transitions from symptom to verified findings with traceable rationale.
  • Live known-gap rechecks, chain-of-evidence requirements, and structured packet generation for auditability.
  • Audit-friendly case-files and verification planning that support cross-session collaboration and escalation when needed.

Quick Start

Just start a diagnosis session against a bug report to run through the eight-phase workflow and produce a diagnosis packet.

Frequently Asked Questions about tribune

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

FAQPage Schema
How do I diagnose a software bug from a vague symptom report?

It guides you through an eight-phase workflow that transforms a vague bug symptom report into an evidence-backed diagnosis, reducing guesswork and surfacing the root cause for an actionable fix.

What is evidence-based software debugging for bug reports?

Evidence-based software debugging is a structured approach that requires a chain-of-evidence for every finding. It enforces live known-gap rechecks and phase-based gating to ensure your bug report diagnosis is fully verifiable and auditable.

How do I structure a diagnosis packet for a flaky test failure?

You generate a formal 14-field diagnosis packet by running the bug report through an eight-phase workflow. This packet satisfies requirements for phase-based gating, live known-gap rechecks, and cross-repo verification planning.

Can I use this structured debugging workflow for cross-repo regressions?

Yes, you can diagnose cross-repo regressions using the built-in cross-repo verification planning. The workflow produces audit-friendly case-files that support cross-session collaboration and escalation when needed.

What is the best way to verify a software defect reproduction?

The best way to verify a software defect reproduction is using a structured workflow with live known-gap rechecks. It ensures your reproduction steps are backed by a formal chain-of-evidence before generating a diagnosis packet.