Merge Readiness

What it does

Composites all signals from tests and reviews into a single merge-readiness verdict. The TL reads every dev-report, test report, and review report, applies all nine guardrails, and produces merge-readiness.md with a READY-FOR-MERGE, BLOCKED, or NEEDS-CHANGES status.

When to use it

Run after all reviewer verdicts are in and any BLOCK findings have been resolved through fix iterations. This command is the final automated gate before the EM summary and human approval.

Inputs

• ›REQ id
• ›TASK-N-dev-report.md files
• ›TASK-N-test-*-report.md files
• ›TASK-N-review-*.md files
• ›gr-review.md

Outputs

• ›merge-readiness.md

Example

/eng-org:merge-readiness REQ-20260723-d904-01 — TL aggregates all signals, applies guardrails G-1 through G-9, and writes merge-readiness.md with status: READY-FOR-MERGE when all gates pass.