mismagent-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 mismagent-readiness-gate-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mismagent-readiness-gate
Source: https://github.com/lucolucus/mismagent/tree/main/codex/skills/mismagent-readiness-gate
Command: npx skills add https://github.com/lucolucus/mismagent --skill mismagent-readiness-gate-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Launching a build on an incomplete manifest wastes worker effort and fails late. This Skill runs the worker-composer's Phase 1 survival test early, catching missing acceptance criteria, unpinned boundary types, or non-discriminating gates before the build starts. ## Core Features & Use Cases - Manifest survival test: Checks every block in building-blocks.yaml for complete specs and concrete tests_nl/ACs, and every boundary for pinned types, contract_test, and projection. - Cross-deploy contract verification: Confirms declared contracts exist (openapi operationIds resolve, event-schema files present) and that the profile gate is executable and discriminating via red-green proof. - Three-way verdict: Reports PASS (launch the worker-composer), BLOCKED (precise misalignments and which step to rework), or EXPLICIT PENDING (parked bounces, open spikes, unsatisfied cleanup nodes). - Use Case: Before running the build on a feature, ask for a readiness check to discover that a high-value block lacks tests_nl, fix it in the model step, and only then launch the worker-composer. ## Quick Start Ask the agent to run the readiness gate on your feature's building-blocks.yaml manifest before launching the worker-composer build.

Frequently Asked Questions about mismagent-readiness-gate

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

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

Run the readiness gate on the feature's building-blocks.yaml before launching the worker-composer. It applies the same Phase 1 survival test the worker-composer runs, reporting PASS, BLOCKED with precise misalignments, or EXPLICIT PENDING items.

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 with red-green proof.

Does the readiness gate replace the worker-composer Phase 1?

No, it is an optional early run of the same Phase 1 test. The worker-composer remains the single authoritative gate and re-runs Phase 1 on launch; this skill only catches incomplete manifests sooner and persists no verdict.

Why does the readiness gate report BLOCKED on a cross-deploy boundary?

A cross-deploy boundary is blocked when its declared contract is missing: openapi boundaries need every cited operationId to resolve, and event-schema boundaries need the versioned schema files. Contracts deferred to a wave-0 scaffold output are accepted.

What does EXPLICIT PENDING mean in the readiness verdict?

EXPLICIT PENDING lists items that are neither actionable nor errors: cleanup nodes with unsatisfied ready_when, parked bounces awaiting user answers, open spike nodes, and stale spikes already answered by an ADR. They are reported separately, never silently passed.