Startup Launch
Launch planning workflow: positioning, messaging hierarchy, channel selection, content cadence, and launch-day checklist.
About
Workflow that turns a product brief into a launch plan with positioning statement, messaging hierarchy, primary channels, content cadence, and a launch-day checklist. Output is a markdown brief plus a one-page Mermaid timeline. Does not execute any launch actions itself.
Native install
For environments with file or shell access (Codex, Claude Code, Gemini CLI, Cursor, local CLI). v0.1: the apai CLI is a scaffold; real install behavior lands in Phase 1.
The apai CLI is a TypeScript scaffold at v0.1. See /honest-status for the full shipped vs stubbed list.
Prompt install
Hosted chat apps (ChatGPT, Claude, Gemini, Grok) cannot silently install software. Paste the snippet below into the chat to load the package protocol for the current conversation only.
Paste this into any LLM that does not have shell access to your machine - chatgpt.com, claude.ai, gemini.google.com, grok.com - and the model will load the Capability Passport and apply the package protocol. If you are using Claude Code, Codex, Cursor, Gemini CLI, or another tool-enabled agent, use apai install instead - it produces a durable install receipt.
Install https://apai.run/packages/startup-launch for this chat. Given a product brief, produce a launch plan with positioning, messaging, channels, cadence, and a checklist. Surface assumptions. Do not post to any channel.
Install card source: https://apai.run/packages/startup-launch/llms.txt
Capability Passport
Reads
- ·Operator-supplied product brief
Writes
- ·Launch plan markdown + Mermaid timeline
Accesses
- ·No network access required
Spends
- ·No spend
Exposes
- ·Launch plan is local unless explicitly shared
Approvals required
- ·Approval required to post any content externally
Rollback
Delete generated launch plan files.
Scanner
heuristic-stub-v0 means the v0.1 scanner (13 suspicious-pattern regex checks + Unicode format-character detection) found nothing. It does NOT mean the package is certified safe. Real prompt-injection, OAuth-scope, and dependency scanning lands in Phase 5. See honest status.