ship-itlisted

Delivery-stage skill in the Agentic Engineering pipeline. Checks milestone PR readiness once a milestone genuinely has zero open issues remaining and prepares/creates the milestone PR through authorized human approval; investigates and explains delivery/CI failures on an already-open milestone PR, handing any human-authorized correction to `implement-it`; and, once the human confirms the PR merged and authorizes the post-merge progression, closes the milestone and prepares, publishes, and validates the release. Each entry point checks GitHub's actual current state rather than requiring proof of a prior `implement-it` session. Use when checking whether a milestone is ready for a PR, creating that PR, investigating a delivery/CI failure, checking whether a milestone is ready to close, or releasing a version. Does not implement code, decide what work should exist, or approve/merge the PR — the human retains both.
elieandraos/agentic-engineering · ★ 0 · AI & Automation · score 70

Install: claude install-skill elieandraos/agentic-engineering

# ship-it ## What this skill is `ship-it` is the delivery stage of the Agentic Engineering pipeline. It checks and acts on a milestone's or PR's actual current state — PR readiness and creation, investigation and continuation on an already-open milestone PR, and post-merge closure and release — rather than requiring proof that a particular `implement-it` session produced that state. ## Pipeline position `lab-it → plan-it → implement-it → ship-it` This skill never decides what work should exist and never implements code — `implement-it` is what closes a milestone's issues, but this skill checks the milestone's and PR's current state directly against GitHub rather than requiring evidence that a specific `implement-it` session produced it. Its entry points have different prerequisites, not one shared precondition: - **Milestone PR readiness and creation** require the milestone to genuinely have zero open issues remaining, re-checked fresh — not merely an empty dependency-ready set, since open issues can all be blocked without the milestone being done. - **Investigating or continuing on an already-open milestone PR** (a CI failure, a follow-up push) starts from the PR's own existence and state — it does not re-require zero open issues, since the milestone already passed that gate once to reach PR creation. - **Post-merge closure and release** start from the human's confirmation that the PR merged and explicit authorization to proceed — independent of any `implemen