hamza-ali-shahjahan /launch-plan
Usage: /launch-plan <product-slug> [--date=YYYY-MM-DD]
What this does
Runs the Launch-stage agents in sequence:
launch/brand-story-builder— positioning, voice, naminglaunch/landing-page-copywriter— landing copylaunch/seo-strategist+launch/keyword-researcher— content + SEO foundationlaunch/pricing-strategist— initial pricinglaunch/launch-strategist— day-by-day plan with assetslaunch/cold-outreach— first-100 outreach templateslaunch/community-builder— community decision + plan
Outputs go to products/<slug>/launch/.
What you do as the assistant
- Resolve
<product-slug>. Confirm it's at the right stage (launchor post-MVP). - Read all relevant product context (
prd.md,metrics.md, recent interview synthesis). - Run the 7 agents. Some in parallel: brand → (landing + seo + pricing) → launch-strategist → (cold-outreach + community).
- After all done: produce a "launch readiness checklist" — what's done, what's missing, what's blocking.
Pre-flight blockers (must clear before launch)
- ✅ Metrics framework wired (PostHog events live in prod)
- ✅ Sentry catching real errors
- ✅ Stripe test card flow works end-to-end
- ✅ Brand assets locked
- ✅ Landing page tested on mobile + desktop
- ✅ Warm list ≥ 50
If any blocker is unmet, the launch plan ships with a "launch blocked, here's what's missing" header.