Builds the complete asset manifest for a software launch - every artifact the launch type demands (Product Hunt, app store, demo day, press), each with its spec, its producing skill, and its deadline class - including the T-minus-7 minimum manifest a 1-3 founder team can produce in a week - and serializes one story spine into native dialects per channel so nothing is cross-pasted. Use when someone asks "what assets do we need for our launch", "write the spec sheet for everything we have to produce before launch", "turn our launch story into versions for Product Hunt, X, LinkedIn, and Hacker News", "which launch assets are we missing", or a launch is planned and no artifact inventory exists. Do NOT use for the dated launch calendar and owners - use launch-plan-sequencer instead - or for running launch day in real time - use launch-day-runbook instead.
---
name: launch-asset-orchestrator
description: Builds the complete asset manifest for a software launch - every artifact the launch type demands (Product Hunt, app store, demo day, press), each with its spec, its producing skill, and its deadline class - including the T-minus-7 minimum manifest a 1-3 founder team can produce in a week - and serializes one story spine into native dialects per channel so nothing is cross-pasted. Use when someone asks "what assets do we need for our launch", "write the spec sheet for everything we have to produce before launch", "turn our launch story into versions for Product Hunt, X, LinkedIn, and Hacker News", "which launch assets are we missing", or a launch is planned and no artifact inventory exists. Do NOT use for the dated launch calendar and owners - use launch-plan-sequencer instead - or for running launch day in real time - use launch-day-runbook instead.
---
# launch-asset-orchestrator
Launches die of missing artifacts and cloned copy, not missing strategy. The team discovers at T-minus-12h that the gallery is unrendered, and worse, pastes the same announcement into five channels - and the identical cross-post is the single strongest automation tell, read as such by audiences and by feed ranking alike. This skill makes the inventory and the serialization one deliverable, so neither failure can happen: every artifact gets a row before the deadline, and one story becomes five native dialects instead of one pasted press release.
## Operating procedure
Run the steps in order, because each output feeds the next: the charter and launch type determine which manifest applies, the manifest determines what the spine must serialize into, and the readiness gate comes last because it reads the filled manifest.
### Step 1: Gather the launch inputs
Elicit exactly these seven inputs before building anything.
1. **Brand charter.** Paste the charter block if one exists. If the client has a charter but the foundations pack is not installed, elicit the needed values directly and label them provisional. If no charter exists at all, halt and route to premium-design-foundations - never substitute worked-example values.
2. **Launch type**: Product Hunt, app store, demo day, conference, or press-led. Default: Product Hunt for a consumer or dev-tool web product; app store for a mobile-first product.
3. **Story spine** in five lines - problem, insight, demo, proof, ask. Flag any line the team cannot fill; a missing proof line blocks the press and Product Hunt renditions until a real number exists.
4. **Channels in play.** Default set: Product Hunt, X, LinkedIn, Hacker News, email.
5. **Team size and runway** to launch day - this picks the full manifest or the T-minus-7 minimum in Step 2.
6. **Waitlist size and Product Hunt Coming Soon follower count** - these feed the Step 5 play fork.
7. **Existing visual assets** - what is already rendered, what is not.