GitHub PR Publish

Delivery Readiness

For every implementation PR, read the installed executing-plans skill's references/delivery-gate.md before declaring merge-ready, merging, or reporting Done; nothing here weakens it. In short: acceptance evidence for the full outcome, a PASS from a reviewer in a different lab than every contributor, tied to the current head, and green required CI. Missing evidence stays a visible blocker; a new commit invalidates earlier review and CI. Merge only within existing authorization, bound to the verified head. Done also needs merge and the issue's required deployment evidence.

Authorized Scope

Act only within the user's request and existing approval; loading this skill grants no new authority. Keep report-only requests report-only, honor the caller's target, host, provider, and cost limits, ask before expanding scope, and forward these limits to delegates.