contract-architecture

Validate B2B→B3 payloads against the L88_ARCHITECTURE_PAYLOAD schema.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates B2B to B3 payload handoffs against the L88_ARCHITECTURE_PAYLOAD schema, ensuring contracts preload correctly in producer and consumer contexts, and prevents misaligned handoffs.

Core Features & Use Cases

  • Schema validation of B2B→B3 payloads against the shared contract schema.
  • Preload management ensures producers load the required data before handoff and consumers initialize correctly.
  • Compliance checks verify required sections (S1, S3, S5, S6, S9) and that the migration path adheres to the protocol.

Quick Start

Validate a sample payload against the L88_ARCHITECTURE_PAYLOAD schema and preload producer/consumer contracts.

Frequently Asked Questions about contract-architecture

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

FAQPage Schema
How do I validate B2B to B3 payload handoffs against a contract schema?

Validate B2B to B3 payload handoffs by checking payloads against the L88_ARCHITECTURE_PAYLOAD schema, ensuring producers preload required data and consumers initialize contracts correctly to prevent misaligned handoffs.

What is payload contract verification for producer and consumer contexts?

Payload contract verification ensures producers correctly preload required data before handoff and consumers initialize properly upon receiving B2B to B3 payloads validated against the shared architecture schema.

How do I ensure my architecture payload meets Approved Profile and Sibling DNA compliance?

Ensure architecture payload compliance by validating required sections (S1, S3, S5, S6, S9) against the L88_ARCHITECTURE_PAYLOAD schema, verifying functional requirements for an Approved Profile and Sibling DNA patterns.

Does B2B to B3 handoff validation check for ordered Build Sequence and Files Touched table?

B2B to B3 handoff validation checks for an ordered Build Sequence containing at least one file and a Files Touched table, ensuring both are present per the required validation checklist for payload compliance.

Why does my B2B to B3 payload handoff fail migration path compliance checks?

B2B to B3 payload handoffs fail compliance checks when required sections (S1, S3, S5, S6, S9) are missing, or when the migration path deviates from the protocol defined by the L88_ARCHITECTURE_PAYLOAD schema.