diagnostic

Triage degraded orchestration environments with flight recording and spawn restrictions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dylan-conlin/orch-go --skill diagnostic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostic
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/meta/diagnostic
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loadable stabilization layer for degraded orchestration environments, providing a flight recorder, spawn restrictions, and a triage playbook to preserve system integrity.

Core Features & Use Cases

  • Flight Recorder: auto-logs state changes to HANDOFF.md to survive crashes.
  • Spawn Restrictions: one-at-a-time spawning to prevent cascading failures.
  • Triage Playbook: guided, prioritized steps to restore stability and data safety.
  • Use Case: When orchestrator health is poor, load diagnostic to stabilize, triage issues, and document actions for post-mortems.

Quick Start

Load this skill during degraded orchestration and follow the entry protocol to stabilize the system.

Frequently Asked Questions about diagnostic

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

FAQPage Schema
How do I stabilize a degraded orchestration environment during cascading failures?

To stabilize a degraded orchestration environment, load a diagnostic layer that prioritizes system stability over feature work. It enforces spawn restrictions, guided triage, and flight recording to preserve integrity during cascading failures.

What is a flight recorder for orchestrator crashes and how does it work?

A flight recorder for orchestrator crashes automatically logs state changes to HANDOFF.md, ensuring critical system data survives unexpected failures. This provides documented actions and state history for post-mortem analysis and recovery.

How do I prevent cascading failures when spawning new processes in an unhealthy orchestrator?

Prevent cascading failures during unhealthy orchestrator states by enforcing strict spawn restrictions. The diagnostic skill limits spawning to one process at a time, mitigating resource exhaustion and halting failure propagation.

When should I load a diagnostic stabilization layer over continuing feature work?

Load a diagnostic stabilization layer when the orchestrator health is poor, such as during system crashes or unhealthy states. It enforces an entry protocol to immediately pause feature work and prioritize system stability and data safety.

How do I triage system stability issues and document actions for post-mortems?

Triage system stability issues by following a guided, prioritized playbook that restores stability and ensures data safety. The process automatically documents triage actions and state changes for accurate post-mortem reporting.

Does this diagnostic stabilization approach work without an existing orchestrator skill?

No, this diagnostic approach requires a dependency on an existing orchestrator skill. It functions as a loadable stabilization layer that integrates with orchestration workflows to manage triage, flight recording, and controlled spawning.