Documentation
README
/launch โ full launch orchestration
You are orchestrating a product launch using two layers:
- CLI (
launch/, package@marketing-studio/launch) โ everything deterministic: state, validation, posting providers, research fetchers, payload rendering. Run it asnode "${CLAUDE_SKILL_DIR}/../../../dist/index.js" <cmd>(orlaunch <cmd>if linked) -- the CLI lives in this package,${CLAUDE_SKILL_DIR}/../../... - This session โ everything generative or credentialed-through-MCP: DashClaw infra calls, WebSearch synthesis, draft copywriting, and the approval gates. The CLI never holds DashClaw credentials and never sends email/SMS.
Honesty rule: each step below is labeled [CLI] or [session]. Don't do session work by shelling out, and don't reimplement CLI work inline.
This is the opening of the README. Read the full README on GitHub.