loom-ship

loom-ship

Shipping packages already-truthful Loom work for an external handoff.

It does not own closure. The ticket-owned acceptance gate evaluates acceptance, closure readiness, and residual risk; optional commands may invoke that workflow but do not own it.

What This Workflow Coordinates

• PR or merge summary drafting
• release note drafting
• evidence summary
• risk summary
• follow-up list
• external handoff packaging

Use This Skill When

• implementation and evidence are already recorded
• critique and retrospective / promotion disposition need to be summarized
• work needs to be packaged for PR, release, review, or handoff
• external systems need a mirror of Loom truth

Do Not Use This Skill When

• the ticket is not yet truthful
• evidence is missing
• critique is required but unresolved
• the goal is for shipping itself to evaluate acceptance, closure readiness, or residual risk
• the goal is to close the work

Inputs

• ticket or tickets
• plan or initiative, when relevant
• evidence
• critique
• retrospective / promotion disposition, plus wiki-specific disposition when wiki was one selected promotion path
• known follow-ups
• external refs, when present

Outputs

• PR summary
• test or evidence summary
• risk summary
• follow-up list
• release note draft when useful
• handoff option summary for merge, PR, keep, or abandon decisions when relevant

Guardrail

Shipping may summarize and package already-truthful ticket, evidence, critique, wiki, risk, and follow-up disposition. Ticket-owned acceptance disposition owns closure.

Before packaging, confirm the ship-owned preconditions are true for the handoff: ticket truth is current, evidence and critique dispositions are sufficient for the handoff claim, scope and safety limits are respected, Git/worktree state is known when files are being packaged, and external summaries will mirror Loom truth. If ship is being invoked from loom-drive, satisfy drive's hard preflight gates in the drive-owned checkpoint before packaging.

Done Means

• the package cites Loom records rather than relying on conversation context
• risks and unresolved follow-ups are visible
• external summaries remain summaries; ticket acceptance still decides closure
• unresolved handoff actions and ticket-owned acceptance gaps are explicit

Read In This Order

Read immediately for shipping/package work:

1. skills/loom-tickets/SKILL.md when reading ticket state, acceptance, and live execution truth.
2. skills/loom-evidence/SKILL.md when checking evidence artifacts or evidence summaries.
3. skills/loom-records/SKILL.md when checking links, external refs, or claim coverage grammar.

Then read conditionally:

4. references/handoff-options.md when a branch, worktree, PR, or external handoff needs an explicit merge / PR / keep / abandon decision.
5. skills/loom-git/SKILL.md when the handoff involves branch, worktree, diff, merge, PR, cleanup, or abandon operations.
6. skills/loom-critique/SKILL.md when unresolved risk or review disposition affects packaging.
7. skills/loom-wiki/SKILL.md when accepted explanation or release notes need wiki-backed wording.