Execute custom team commands with full observability
Executes team-defined custom commands with full observability and workflow integration.
/plugin marketplace add 501336north/one-shot-ship-plugin/plugin install oss@one-shot-ship-pluginCommand: /oss:custom
Description: Execute a custom command defined by your team (with team: prefix).
Workflow Position: Can be inserted anywhere in the workflow chain (ideate → plan → CUSTOM → build → ship)
Usage:
/oss:custom <command-name>
Arguments:
| Argument | Required | Description |
|---|---|---|
| command-name | Yes | The custom command name (with or without team: prefix) |
Examples:
# Execute a custom command
/oss:custom team:review-standards
# Without prefix (team: is added automatically)
/oss:custom review-standards
Related Commands:
/oss:build - Execute TDD implementation after custom steps/oss:workflows - View and manage workflow configurationExecute a custom command defined by your team with full observability.
cat ~/.oss/config.json 2>/dev/null | grep apiKey
If no API key found:
No API key found. Run: /oss:login
Register at https://www.oneshotship.com
You MUST initialize logging for supervisor visibility.
~/.oss/hooks/oss-log.sh init custom
Before executing, fetch and review the IRON LAWS:
~/.oss/hooks/fetch-iron-laws.sh
All IRON LAWS must be followed. Self-correct any violations before proceeding.
You MUST update the workflow status before proceeding.
~/.oss/hooks/oss-notify.sh --workflow custom start '{"command": "{COMMAND_NAME}"}'
Replace {COMMAND_NAME} with the actual custom command name (without team: prefix).
~/.oss/hooks/ensure-decrypt-cli.sh || { echo "Failed to install decrypt CLI. Run /oss:login for manual setup."; exit 1; }
This auto-installs the decrypt CLI if missing. Existing installations are unaffected.
Strip the team: prefix if present and fetch the custom command:
# Parse command name (strip team: prefix if present)
COMMAND_NAME="${1#team:}"
# Fetch custom command prompt from API
~/.oss/bin/oss-decrypt --type custom --name "$COMMAND_NAME"
The decrypt CLI fetches the prompt from /api/v1/prompts/custom/{name} and returns the decrypted prompt content.
The endpoint returns:
{
"prompt": "The custom command prompt content...",
"name": "review-standards",
"displayName": "Review Standards",
"isBlocking": true
}
Execute the prompt content returned by the API. The prompt will guide the workflow step.
Handling Blocking Behavior:
isBlocking: true and the command fails, stop the workflow chainisBlocking: false, log the result but continue the workflowYou MUST update the workflow status on completion.
After custom command completes:
~/.oss/hooks/oss-notify.sh --workflow custom complete '{"command": "{COMMAND_NAME}"}'
If custom command fails:
~/.oss/hooks/oss-notify.sh --workflow custom failed '{"command": "{COMMAND_NAME}", "error": "{ERROR_MSG}"}'
Authentication failed. Run: /oss:login
Subscription expired or insufficient permissions.
Upgrade at: https://www.oneshotship.com/pricing
Custom command '{COMMAND_NAME}' not found.
Check your team's custom commands at: https://www.oneshotship.com/dashboard/commands
API temporarily unavailable. Contact support@oneshotship.com
Custom commands integrate with workflow chains:
# Example workflow config with custom command
build:
chains_to:
- team:review-standards # Custom command after build
- ship
The workflow engine detects the team: prefix and executes via this command pattern.
Custom command availability by plan:
| Plan | Custom Commands |
|---|---|
| TRIAL | 0 |
| PRO | 1 |
| TEAM | 10 |
| ENTERPRISE | Unlimited |