readiness-gate

Validates a building-block manifest against the worker-composer Phase 1 survival test before build launch.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill readiness-gate-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readiness-gate
Source: https://github.com/lucolucus/mismagent/tree/main/plugins/mismagent/skills/readiness-gate
Command: npx skills add https://github.com/lucolucus/mismagent --skill readiness-gate-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Launching a build on an incomplete feature manifest wastes worker effort and fails late. This Skill runs an optional early pre-flight check that catches missing acceptance criteria, unpinned boundary types, and non-executable gates before the build starts. ## Core Features & Use Cases - Manifest survival test: Verifies every block in building-blocks.yaml has a complete spec with concrete tests_nl or acceptance criteria, and every boundary has pinned types, a contract_test, and a projection. - Cross-deploy contract checks: Confirms declared contracts resolve (openapi operationIds, versioned event schemas) and that the profile gate is executable and discriminating via a red-green proof. - Status triage: Distinguishes PASS, BLOCKED (with precise misalignments and the step to rework), and EXPLICIT PENDING items such as parked bounces, cleanup nodes, and open spikes. - Use Case: Before running /mismagent:worker-composer on a feature, run this pre-flight to confirm the manifest is ready, or skip it and let the worker-composer's own Phase 1 act as the single authoritative gate. ## Quick Start Run the readiness-gate pre-flight on my feature's building-blocks.yaml manifest and tell me whether it is ready to build or exactly what is blocking it.

Frequently Asked Questions about readiness-gate

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

FAQPage Schema
How do I check if a mismAgent feature manifest is ready to build?

Run the readiness-gate pre-flight on the feature's building-blocks.yaml. It applies the worker-composer Phase 1 survival test and reports PASS, BLOCKED with precise misalignments, or EXPLICIT PENDING items like parked bounces and open spikes.

What does the readiness gate check in building-blocks.yaml?

It verifies every block has a complete spec with concrete tests_nl or acceptance criteria, every boundary has pinned Published Language types plus contract_test and projection, and the profile gate is executable and discriminating via a red-green proof.

Is the readiness-gate required before running worker-composer?

No, it is optional. The worker-composer's own Phase 1 is the single authoritative gate and re-runs the same checks; the readiness-gate only runs that test early so you catch an incomplete manifest before launching.

How are cross-deploy boundaries validated?

The declared contract must exist in the form the boundary declares: for openapi every cited operationId must resolve, and for event-schema the versioned schema files must exist. Validation is deferred when the contract is an output of the wave-0 scaffold.

Why does the gate report BLOCKED on a missing gate-proof?

A gate that cannot go red is not a gate, so Phase 1 requires a red-green proof. The proof is a project-level fact, so any features/*/gate-proof/<side>.md file is accepted, not only the current feature's.