me-2b

Score architecture payloads across M, D, R, and C dimensions for B2B exit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates objective B2B exit scoring for architecture payloads, providing consistent evaluation before handoff.

Core Features & Use Cases

  • Formula-based scoring across M (Mapping), D (Dependency), R (Risk), and C (Coherence) to quantify design readiness.
  • Validation of file mappings, build order, risk mitigations, and data-flow coherence prior to transition to B3.
  • Use Case: When finalizing an architecture payload for handoff, run ME-2B to produce a verifiable score and a mapping trace.

Quick Start

Provide a B2B exit evaluation for an architecture payload by scoring M, D, R, and C and applying the HB Validation Gate.

Frequently Asked Questions about me-2b

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

FAQPage Schema
How do I score architecture readiness for B2B exit validation?▼

Score architecture readiness by evaluating M (Mapping), D (Dependency), R (Risk), and C (Coherence) dimensions, then applying the formula (M + D + R + C) / 4 to produce a verifiable exit score.

What is B2B exit scoring for architecture payloads?▼

B2B exit scoring is an automated evaluation process that validates file mappings, build sequences, risk mitigations, and data-flow coherence before an approved architecture design transitions to B3.

How do I check dependency risks before architecture handoff?▼

Check dependency risks by mapping approved designs, validating build order, verifying risk mitigations, and tracing data-flow coherence through the HB Validation Gate prior to handoff.

Can I use objective scoring for build sequence validation?▼

Yes, objective scoring validates build sequences by applying calibration anchors and traceability checks across data flows, ensuring approved designs are correctly mapped before passing to B3.

When do I need architecture handoff validation?▼

You need architecture handoff validation when finalizing an architecture payload, ensuring file mappings, build order, risk mitigations, and data-flow coherence are verified before transitioning downstream.

Why does architecture payload scoring require traceability checks?▼

Architecture payload scoring requires traceability checks to verify that file mappings, build sequences, and data flows are coherently traced and risk-mitigated before passing the HB Validation Gate.