drive-ship

Ships reviewed deliverables through planned distribution channels with human confirmation gates.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill drive-ship-hivgb1-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drive-ship
Source: https://github.com/hivgb1-ai/do-better-workspace-v2/tree/main/.claude/skills/drive-ship
Command: npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill drive-ship-hivgb1-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished work often never reaches its audience because publishing, sending, or launching is irreversible and error-prone. This Skill acts as the final release gate in the Do Better Drive workflow, ensuring reviewed deliverables actually go out through the planned channels—safely and verifiably. ## Core Features & Use Cases - Pre-flight verification: Confirms the review verdict passed, the deliverable exists at its recorded path, and the distribution channel is ready before anything ships. - Sensitive-information screening: Scans outgoing public content for revenue figures, contract amounts, company-plus-price combinations, API keys, and personal data, replacing them with quantitative workarounds. - Human confirmation gate: Pauses before irreversible actions (public publishing, sending, launching, contracts) until the user explicitly approves; reversible actions proceed with a report. - Delegation to existing skills: Hands actual publishing and sending to channel skills (ghost-publish, gmail, slack, naver-commerce, note-publish) instead of reimplementing them, and skips already-sent channels on reruns to prevent duplicate sends. - Use Case: After a newsletter draft passes review, the Skill test-sends it to yourself, checks rendering, asks for your final go-ahead, publishes via the newsletter skill, verifies the live URL displays correctly, and logs the shipment in progress.md. ## Quick Start Tell the assistant "내보내기" or "이제 내보내" after a deliverable has passed the drive-review stage, and it will run the shipping gate end to end.

Frequently Asked Questions about drive-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a reviewed deliverable with drive-ship?▼

Say a trigger phrase like "내보내기" or "이제 내보내" after the review stage passes. The Skill reads progress.md, verifies the deliverable and channel readiness, runs a sensitive-information check, asks for your confirmation, then delegates sending to the appropriate channel skill.

What happens if the review stage did not pass?▼

The Skill refuses to ship and routes the work back to the drive-review stage. If the pass was conditional, it first verifies the agreed minor fixes were actually made before proceeding.

Does drive-ship send emails or publish posts itself?▼

No. It explicitly delegates all publishing and sending to existing channel skills such as ghost-publish, gmail, slack, naver-commerce, and note-publish. It only orchestrates the gate checks, confirmation, and verification.

How does it prevent duplicate sends when rerunning?▼

Before sending to each channel, it checks whether that channel already shipped. Channels already sent are skipped for delivery while still being re-verified and logged, preventing duplicate newsletters or posts.

What sensitive information does it block from public content?▼

It flags revenue figures, contract amounts, quotes, unit prices, company-name-plus-amount combinations, API keys, passwords, and personal data in outgoing public content, replacing them with quantitative workarounds like counts or session numbers.

When is human confirmation required before shipping?▼

Confirmation is required for irreversible actions such as public publishing, sending, launching, and contracts. Reversible actions like saving drafts or private registrations proceed automatically with a report afterward.