| name | haipipe-application-deploy |
| description | Deployment specialist for the intervention lifecycle. STUB. Packages reviewed artifacts for delivery through the specified channel (SMS vendor API, dashboard endpoint, email system). Parallel to paper's compile+submit. Trigger: deploy, ship, go live, send, /haipipe-application deploy. |
| argument-hint | [variant-id] [--channel sms|dashboard|email] [intervention-path] |
| allowed-tools | Bash, Read, Write, Edit, Grep, Glob, Skill |
| metadata | {"version":"0.1.1","last_updated":"2026-07-06","summary":"Deployment specialist (STUB) — packages a reviewed artifact for delivery through its channel. History: ./CHANGELOG.md."} |
Skill: haipipe-application-deploy (STUB)
Status: STUB. Will package reviewed artifacts for delivery
through the specified channel.
When implemented:
Step 1: Verify deployment prerequisites: artifact status reviewed, Gate Ledger
rows complete, venue pack deployment notes satisfied.
Step 2: Package artifact for channel (SMS API payload, dashboard
config, email template).
Step 3: Deploy to staging / test environment.
Step 4: Verify delivery (test send, preview render).
Step 5: On approval: deploy to production.
Step 6: Update artifact status: reviewed → deployed.
Step 7: Log deployment in STATUS.md.
Deployment channels (future):
SMS: vendor API integration (Twilio, etc.)
Dashboard: endpoint update via /haipipe-end
Email: template system integration
In-app: UI component deployment
Risk profile
HIGH — deploys to external channels. Must be gated by review +
explicit user approval. Never auto-deploy.
