| name | delivery-start |
| description | The front door to the Delivery pack: get ready to deliver client work and gate it before it ships. Trigger on "get me ready to deliver this", "help me deliver this client work", "I have client work due", "prep this delivery", "ready this for the client", "is this ready to send to the client", or any open-ended request about doing or shipping client work where the user has not picked a step. You name what you owe a client; the OS reads what it knows, then routes you to the move you need: prep the session, write the update, document the process, build the branded document, or run the ship gate before it goes out. One honest disclaimer, no full onboarding, and it never sends to the client for you. Routes to meeting-prep, client-update, sop-writer, your-deliverable-template, blind-spot-review, pre-send-check, or ship-deliverable depending on the step.
|
| why | A founder who is also the delivery team does the work and ships it with no one to check it. This is the one entry that turns 'I owe a client something' into the right step, and makes sure a second pair of eyes runs before anything leaves the machine. |
| enhance | Set your brand profile (say 'set up my brand profile') so branded documents render in your identity, and keep context/clients.md current so prep and updates read from real history instead of starting blank. |
| summary | Name what you owe a client; the OS readies it and checks it before it ships. |
| allowed-tools | ["Read","Bash"] |
| mcp_requirements | [] |
Delivery Start
Runs on: reasoning - this skill reads what the OS knows about the client and the work, then routes you to the member skill that does the step. It does not produce the deliverable itself and it never sends anything to a client. On a read-only or cloud surface, it explains the same route without claiming a file was written.
This is the front door to delivery. You owe a client something: a session you need to be ready for, a status update, a process to hand off, a document to build, or a finished piece that needs checking before it ships. This skill reads what the OS holds, then points you at the step you actually need, and it makes sure the ship gate runs before anything leaves your machine.
The principle: do more for you than you asked, in the order a careful operator would, and never let weak work ship as if it were checked. A solo founder has no one to catch the blind spot; the OS is that check.
The steps behind one delivery
| You want | What it means | Where it routes |
|---|
| Prep the session | a brief for the client call: what to cover, what to watch for | meeting-prep |
| Write the update | a client-facing status or milestone report in your voice | client-update |
| Hand off a process | a delegation-ready SOP someone else can follow | sop-writer |
| Build the document | a branded proposal, deck, one-pager, or CV in your identity | your-deliverable-template |
| Ship it safely | the final gate before it goes to the client | ship-deliverable (runs blind-spot-review + pre-send-check) |
Not sure which? Say "I have client work due, ready it" and the OS asks the one question that sorts it (are you preparing, producing, or shipping), then routes from your answer.
Read the state before routing
The route is only as good as what it knows. Before choosing, read brain/.snapshot.md. If it is missing, or its date: line is more than 3 days old, run python scripts/brain-snapshot.py --write first and read the fresh one. The open-flags block tells you what is stuck, the must-do block tells you what this week is actually about, and the patterns block tells you what keeps happening - a front door that routes without them is a cold start at the exact moment the user is deciding whether this OS knows them. If Python is unavailable, route from the files you can read and say so.
