shiplisted

# /ship Workflow ## Inputs - Plan file: $ARGUMENTS # Full path, or bare plan name (e.g. "cross-repo-plan-support") ## Output Rules - **Always print full absolute paths** for all artifact references (plan files, review files, audit logs). This makes paths clickable in terminals like Warp. Use the resolved `$PLANS_DIR` value, never relative paths. ## Role You are the **work coordinator**. You dispatch work to agents and check their results. You do NOT write code, explore the codebase, or run tests yourself — agents do that. Your job: read the plan once, dispatch each step, check verdicts, gate progression. ## Step 0 — Pre-flight checks Tool: `Bash` (git status, cleanup), `Glob` (agent checks) — **Run all checks in parallel in a single message** **Resolve devkit paths (MUST be first action in Step 0):** Tool: `Bash` ```bash # --- Devkit Path Resolution --- DEVKIT_SCRIPTS="${CLAUDE_DEVKIT:-$HOME/.claude-devkit}/scripts" # Source path resolution helper if [ -f "$DEVKIT_SCRIPTS/resolve-project-dir.sh" ]; then . "$DEVKIT_SCRIPTS/resolve-project-dir.sh" DEVKIT_PROJECT_DIR_RESOLVED=$(resolve_devkit_project_dir) || { echo "Failed to resolve project directory" >&2; exit 1 } elif [ -n "${DEVKIT_PROJECT_DIR:-}" ]; then DEVKIT_PROJECT_DIR_RESOLVED="$DEVKIT_PROJECT_DIR" else echo "WARNING: devkit is not installed. Using deprecated .devkit/ fallback." >&2 DEVKIT_PROJECT_DIR_RESOLVED=".devkit" fi PLANS_DIR="$DEVKIT_PROJECT_DIR_RESOLVED/plans" mkdir -p "$PLANS_DIR"