Harness Ship
Description
# /harness-ship — build, validate, and bring a planned feature to the ship decision Read `.claude/commands/harness.md` and follow it with **mission: ship**. The differences: - **Precondition, hard:** BRIEF *and* PLAN both `status: approved`. Anything less routes to `/harness-plan` — the orchestrator will refuse anyway (playbook step 1), so catch it here. - **Precondition, mechanical — the worktree must not be behind the default branch.** After step 0b names the worktree and **before any or
Installation
Installs to ~/.claude/commands/mruangutai-harness-harness-ship.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/mruangutai/harness/HEAD/.claude/commands/harness-ship.md -o ~/.claude/commands/mruangutai-harness-harness-ship.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.