By name: ome-ship version: 1.0.0 description: Run final readiness checks and prepare user-facing handoff or commit notes. author: oh-my-engine tags: [ome, ship, workflow]
ome-ship
Workflow Session Start (MANDATORY)
Before reading source files, planning, editing, or running verification for this workflow, you MUST start the OME workflow session by running:
ome ship $ARGUMENTS
This creates .ome/.session so the final ome finish command can record the execution into .ome/memory/executions/.
If a Windows PowerShell policy blocks the ome shim, run the same step through the cross-shell fallback: cmd.exe /c ome.cmd ship $ARGUMENTS. Do not hardcode this fallback on non-Windows platforms.
Claude Code fast path (other agents: ignore the leading ! and run the bare command via your shell tool):
!ome ship $ARGUMENTS
Purpose
Run final readiness checks and prepare a clean handoff or commit note for the finished change.
When to Use
- Use when the change is implemented and ready for final checks.
- Use when you need to package the work for handoff or commit.
- Do not use when the task is still being planned or built.
Inputs
- The completed change and any outstanding risks.
- Relevant verification output or test results.
- Any release, handoff, or commit constraints.
Process
- Confirm the change is complete and scoped as expected.
- Run the final verification that proves readiness.
- Check for missing documentation, notes, or follow-up items.
- Summarize the implementation and verification cleanly.
- Call out any residual risk or known gap explicitly.
- Prepare the final handoff or commit-oriented summary.
- Do not reopen the implementation unless a real defect appears.
Red Flags
- The change still has unresolved correctness issues.
- Final verification has not been run or is inconclusive.
- Important risks are hidden in a vague summary.
- The handoff introduces new scope instead of closing the current one.
Common Rationalizations
- "The obvious fix is good enough without a closer read of the rules."
- "I can skip verification because the change is small."
- "I should broaden the patch while I am here."
- "A vague summary is enough for handoff."
Verification
- Run the final relevant checks.
- Confirm the output matches the changed behavior.
- State what could not be verified and why.
- Confirm the summary is ready for the next owner.
Output Contract
Final response must include:
- Completion summary
- Verification evidence
- Remaining risks
- Handoff or commit notes
Workflow Completion (SUBSTANTIVE WORK ONLY)
Run ome finish only after a substantive workflow loop is complete, and only after you have reported results to the user.
Substantive work means at least one of these is true:
- You changed files or wrote new code/docs.
- You ran verification and the result matters to the task outcome.
- You made a durable technical decision, diagnosis, or reusable learning that should be available later.
Do NOT run ome finish for ordinary conversation, quick explanations, brainstorming with no conclusion, or read-only exploration that produced no reusable outcome.
When the work is substantive, run this as the final shell command:
ome finish
This records the execution into .ome/memory/executions/; the engine policy decides whether it is valuable enough to persist or later evolve.
Claude Code fast path (other agents: ignore the leading ! and run the bare command via your shell tool):
!ome finish