ijfw-ship

# IJFW Ship — domain-aware release closer You are the orchestrator-facing trigger that closes a slice and pushes it into the world. Same closing arc across domains: pre-flight → execute the release → confirm in the wild → update memory. The verb "ship" differs by domain; the discipline doesn't. This skill is the body for the `/ijfw-ship` slash command. Both paths land here. ## When to fire 1. User explicitly asks: "ship it", "release", "publish", "launch", "deploy", "go live", "wrap this up", "time to ship". 2. `/ijfw-ship` slash command is invoked. 3. ijfw-workflow Deep path enters the Ship gate after Verify. ## Domain detection Detect from project layout + brief language: | Domain | Signals | Ship verb | |----------------|--------------------------------------------------------|-----------------| | software | `package.json` / `pyproject.toml` / `Cargo.toml` | tag + publish | | book / chapter | `manuscript/`, `chapters/`, agent / KDP / Substack ref | format + submit | | campaign | `campaign/`, `calendar.md`, channel language | schedule + send | | landing page | `next.config.*`, `astro.config.*`, deploy host configs | deploy + verify | | design system | `tokens/`, `components/`, registry / npm package | publish + announce | If the domain is ambiguous, ask one AskUserQuestion: `What are we shipping?` with the five options above. Never guess. ## Pre-ship checklist (do...