contract-diagnostic

Validate L88_DIAGNOSTIC_PAYLOAD handoff contracts between B1 and B2A.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill contract-diagnostic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-diagnostic
Source: https://github.com/gapfDev/workflow/tree/main/c1.5/.claude/skills/contract-diagnostic
Command: npx skills add https://github.com/gapfDev/workflow --skill contract-diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

L88_DIAGNOSTIC_PAYLOAD validation ensures that the handoff contract from B1 (producer) to B2A (consumer) is complete, consistent, and testable, preventing misalignment during data exchange.

Core Features & Use Cases

  • Validation Checklist: ensures ACs, Root Cause/Anchor, Causal Chain, Blast Radius, Sibling DNA, and PENDING grep verification are present.
  • Use Case: validates payload handoffs in B1 → B2A pipelines to prevent data leakage or misinterpretation.
  • Interoperability: integrates with existing contract schemas described in shared/contracts.md.

Quick Start

Run a diagnostic pass against the B1 → B2A handoff using the provided checklist to verify payload integrity.

Frequently Asked Questions about contract-diagnostic

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

FAQPage Schema
How do I validate producer-consumer contract handoffs to prevent data misalignment?

Validate producer-consumer contract handoffs by running a diagnostic pass against the B1 to B2A pipeline, applying a checklist to verify payload integrity and prevent data leakage or misinterpretation during data exchange.

What is a diagnostic payload contract validation checklist for pipeline handoffs?

A diagnostic payload contract validation checklist ensures Acceptance Criteria, Root Cause/Anchor, Causal Chain, Blast Radius, Sibling DNA, and PENDING grep verification are present and consistent across B1 producer and B2A consumer handoffs.

How do I verify acceptance criteria and causal chain integrity during a preload scenario?

Verify acceptance criteria and causal chain integrity during preload scenarios by applying the L88_DIAGNOSTIC_PAYLOAD validation checklist to ensure all required diagnostic fields are present and testable across producer-consumer components.

Does contract diagnostic validation work with existing shared contract schemas?

Contract diagnostic validation integrates with existing contract schemas described in shared/contracts.md, ensuring the L88_DIAGNOSTIC_PAYLOAD handoff interoperates with established B1 to B2A data exchange formats.

What is the best way to check for PENDING grep verification in a B1 to B2A handoff?

The best way to check for PENDING grep verification is running a diagnostic validation pass that explicitly tests for PENDING markers within the L88_DIAGNOSTIC_PAYLOAD to ensure complete contract handoff compliance.

Why does my producer-consumer payload handoff fail data exchange consistency checks?

Payload handoff consistency checks fail when the L88_DIAGNOSTIC_PAYLOAD is missing required fields like Blast Radius, Sibling DNA, or Root Cause/Anchor, causing misalignment between B1 producer and B2A consumer during data exchange.