harness-ship

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Harness Ship

Use this skill as the Codex equivalent of Claude Code `/harness-ship`.

## Source of Truth

- Read `../../commands/harness-ship.md` before acting.
- Follow that command contract, plus `AGENTS.md` task protocol and the active task docs.
- Ship updates documents only. Do not create a PR/MR, do not push, and do not run task completion —
  it is a separate step the user drives.
- Ship has no CLI subcommand of its own — it is an agent judgement pass over the task documents.
  Use the shared CLI only for what it already owns (for example the task context card check), and
  never invent a ship subcommand for it.
- Translate Claude-only references for Codex:
  - `${CLAUDE_PLUGIN_ROOT}` means this installed plugin root or this repository root.
  - `AskUserQuestion` means ask one concise opt-in question; if this session cannot ask, skip the
    diagram step rather than guessing, and record that it was skipped.
  - A diagram skill such as `diagram-design` is not owned by this harness: it is a separate
    plugin installed per machine, so it may or may not be reachable from this session. Probe for
    it, and when it is missing record the step as not run in the artifact and continue — never
    fail the pass over it, and never assert an install command that may not exist.
- The diagram output belongs at the active task directory and defaults to a self-contained
  inline-SVG HTML file: task documents are often read in viewers that strip script tags (Obsidian,
  for one), where a mermaid JS runtime never renders.
- Before reporting, run `harness-team pr-check` (the one check the harness enforces, D11) after the
  document updates are committed; if it exits 1, do not declare the PR ready. Its diagram notice
  is advisory and does not block.
- Finish by reporting PR/MR readiness: branch and base, changed files, verification output, pr-check result, which
  documents were updated, diagram status, and remaining risks. Then stop.

From bd-makers/team-harness, MIT.

More from bd-makers/team-harness