EM Summary

What it does

Produces the one-page brief that the human approver reads before authorising merge. The summary condenses the goal, scope, file count, test signal, review signal, risk, and rollback plan into a single concise document addressed directly to the approver.

When to use it

Run after merge-readiness.md carries status: READY-FOR-MERGE. The EM summary is the final pipeline artifact before human approval — it refuses to write if merge-readiness is not yet READY.

Inputs

• ›REQ id
• ›spec.md
• ›tl-analysis.md
• ›TASK-N-dev-report.md files
• ›TASK-N-test-*-report.md files
• ›TASK-N-review-*.md files
• ›merge-readiness.md

Outputs

• ›em-summary.md

Example

/eng-org:em-summary REQ-20260723-d904-01 — writes a one-page em-summary.md with goal, scope, 10/10 green tests, 5/5 APPROVE reviews, risk, and rollback plan for human review and merge decision.