shipper design
shipper design
Section titled “shipper design”Usage: shipper design [options] [issue]
Run technical design review on an issue
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| [issue] | no | issue number or URL | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —mode | - | default | execution mode: headless, interactive, or default | headless, interactive, default | |
| —agent | - | - | agent to use: claude, codex, copilot, or opencode | claude, codex, copilot, opencode | |
| —model | - | - | model to use for the agent CLI | - | |
| —disable-mcp | - | - | - | disable MCP server loading for this run | - |
| —enable-mcp | - | - | - | enable MCP server loading for this run | - |
Examples
Section titled “Examples”Run technical design for issue 42.
shipper design 42Exit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The stage completes successfully or returns a reject verdict. |
| 1 | Preflight, validation, GitHub, agent, or fail verdict handling fails. |
Constraints
Section titled “Constraints”- —disable-mcp and —enable-mcp are mutually exclusive