diagnose

Build a deterministic six-phase feedback loop to diagnose AFK pipeline bugs.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ValescoAgency/flightplan --skill diagnose-valescoagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/ValescoAgency/flightplan/tree/main/diagnose
Command: npx skills add https://github.com/ValescoAgency/flightplan --skill diagnose-valescoagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds a deterministic, six-phase diagnostic workflow that yields testable signals for verification and downstream contract drafting.

Core Features & Use Cases

  • Deterministic feedback loop: Generates measurable pass/fail signals for debugging.
  • Phase-driven discipline: Emphasizes Phase 1 as the foundation to drive hypothesis, instrumentation, and regression tests.
  • HITL-friendly workflow: Supports post-triage debugging and guidance for HITL handoffs. Use Case: After triage identifies a bug with unclear reproduction, diagnose produces a verifiable signal to seed the next steps in contract drafting.

Quick Start

Launch Phase 1 by building a deterministic feedback loop that captures a reproducible bug signal.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I build a deterministic feedback loop to diagnose a hard bug?

To build a deterministic feedback loop for debugging, you need a reproducible failure signal, instrumentation hooks, and a clear phase plan to map signals to hypotheses, instrumentation, and regression tests.

What is structured bug diagnosis and when do I need it in my workflow?

Structured bug diagnosis is a six-phase workflow that generates measurable pass/fail signals for verification. You need it after triage identifies a bug with unclear reproduction steps or during human-in-the-loop debugging handoffs.

How do I fix a bug when I have reproduction steps but no verifiable signal?

Fixing a bug with reproduction steps but no signal requires mapping those steps to a deterministic feedback loop, capturing a measurable pass/fail result to seed regression tests and downstream contract drafting.

What prerequisites do I need before starting a structured debugging workflow?

Before starting a structured debugging workflow, you need a reproducible failure signal, available instrumentation hooks, and a clear phase plan to drive hypothesis mapping and regression test generation.

Can I use a deterministic feedback loop for seeding verifiable contracts after triage?

Yes, a deterministic feedback loop produces verifiable signals during post-triage debugging that directly seed downstream verifiable contract drafting and regression test generation.