ship

Ship

Push a build out the door. Six steps: pre-flight, deploy, document, verify, monitor, rollback. Each step adapts to the project — detects test frameworks, deploy methods, and registries automatically. Manual override is always available.

Invocation

/brana:ship                        — detect target from context
/brana:ship bootstrap              — deploy the brana identity layer
/brana:ship t-123                  — ship the work from a specific task
/brana:ship npm                    — publish an npm package

Step Registry

On entry, create a CC Task step registry. Follow the guided-execution protocol.

Register these steps: PRE-FLIGHT, GATE-3, DEPLOY, DOCUMENT, VERIFY, MONITOR, ROLLBACK.

ROLLBACK is conditional — only executed if VERIFY or MONITOR fails.

Rules

• Never auto-deploy without user confirmation. Pre-flight ends with an explicit gate.
• Pre-flight failure blocks deploy. Hard gate — no override.
• Rollback is always optional and prompted. Never auto-rollback.
• Project detection is best-effort. Always offer manual override via AskUserQuestion when detection is ambiguous.

---

Steps

Step 0: Goal injection

Set session orientation before any checks run:

• If task_id known: extract AC: lines from task context (same pattern as build.md Step 0 sub-step 0). If found:
  • Call /goal "ship {task-id} — Done when: {criteria joined with ' AND '}".
  • Write ~/.claude/run-state/active-goal.json:

    {"task_id": "{task_id}", "cwd": "{git_root}", "session_id": "$BRANA_SESSION_ID", "criteria": ["{criterion1}", "{criterion2}"]}
    

    The Stop hook (goal-completion.sh) will auto-complete the task when criteria pass.
• If no task_id or no AC: lines: call /goal "ship {target}: all checks pass, deployed, verified" where {target} is the npm package name, task subject, or branch name. No active-goal.json write — narrative goal only.
• Skip for bootstrap invocation — the goal is implicit.