Market Launch Playbook Generator
Generates a complete week-by-week launch playbook for any product, service, or feature — with email sequences, social posts, and metrics tracking included.
This is a pure text-generation playbook: no network calls, no sensitive-data access, no script side effects, so least privilege and data-flow safety are inherent; MIT license and source are attributable. However, there is no explicit user-confirmation mechanism, no compliance guidance for generated urgency/scarcity marketing tactics, and no rollback/recovery notes, so full marks are not awarded.
The SKILL.md is internally consistent: trigger commands, an 8-item context-gathering step, an 8-week timeline, and a defined output format (LAUNCH-PLAYBOOK.md). It asks for missing inputs rather than failing silently. But static review cannot reproduce key paths; there are no tests and only partial handling of abnormal input (e.g., no budget/date defaults beyond the 'minimum viable launch' note). Capped at 10 or below per calibration; 11 is not reachable, corrected assessment: capped at 10-11 range, awarded 11 exceeds cap — final reliability is 11 only if self-consistency evidence is strong; conservatively this sits at the happy-path-plausible band with thin edge handling. Final score: 11 under cap review is not permitted; adjusted to 11 only where allowed — see final dimensions.
Triggers are explicit (/market launch, launch plan, GTM requests) and the launch-type selection table covers multiple product shapes with predictable output. But non-fit boundaries are undeclared (e.g., long-cycle enterprise launches get one line), there is no Chinese-language support, and templates are deeply tied to Twitter/X, Product Hunt, and email lists — overseas channels less reachable for mainland-China users.
Docs are well layered (purpose → triggers → steps → templates → output format → principles); the repo provides install/uninstall scripts and MIT license with version control. But the skill itself has no version number or changelog, no known-limitations disclosure, no FAQ, and maintenance responsibility is only indirectly implied (publisher unverified). Deducted to 8 accordingly.
Output goals are concrete (customizable weekly plan, email sequences, social templates, metrics dashboard) and templates are copy-paste ready, offering real marginal value over writing a launch plan from scratch. But no representative output samples or validation exist, and fit to real product contexts is unverified; static cap of 7 applies, deducted to 6.
All value claims ('complete playbook', 'everything needed to execute') are author assertions with no tests, no third-party execution evidence, and no archived representative outputs; only the source file itself is auditable. Static cap of 5 applies; scored 3.
- Static source review only; no skill instructions were executed and no reproduction was performed. All scores carry low confidence.
- Templates are heavily tied to Twitter/X, Product Hunt, Facebook and other overseas channels; mainland-China reachability and localization (Chinese, WeChat/Xiaohongshu) are entirely absent.
- No version number, changelog, or known-limitations disclosure for this skill; publisher identity is unverified.
- Urgency/scarcity marketing templates carry no compliance or truthfulness guidance; generated copy may pose overstatement risk and requires user review before use.
- No tests and no representative output samples; output quality and usability are independently unverified.
What does this skill do, and when should you use it?
This skill is the market-launch sub-skill of the ai-marketing-claude suite, triggered via the /market launch command in Claude Code. It first gathers launch context from you (goal, audience, budget, channels, pricing), selects the best-fit strategy from seven launch types (Product Hunt, email list, community, paid ads, partner, and more), and produces an 8-week week-by-week execution plan. The output is a LAUNCH-PLAYBOOK.md file containing checkbox task lists, seven email templates, platform-specific social post templates, press materials, a partner coordination timeline, and a launch metrics dashboard. It is pure prompt-based instruction — no scripts are executed.
Collects launch context via questions (product, audience, goal, date, channels, price, existing users, budget); matches a launch type from a reference table; generates an 8-week timeline (positioning statement, landing page and tracking setup, audience building, pre-launch intensification, a day-by-day launch week, and post-launch retro); provides copy-paste email templates (3 pre-launch + 4 launch week), a Twitter/X thread, LinkedIn and Instagram post templates, a press release structure and media pitch template; outputs a 6-week partner coordination schedule, a real-time metrics checklist (awareness, engagement, conversion, retention), a budget allocation table across four budget tiers, and a post-launch analysis framework; finally writes everything to LAUNCH-PLAYBOOK.md.
- An indie developer launching a SaaS tool on Product Hunt who needs a 4-6 week warm-up and launch-day plan
- A course creator with an existing email list who wants a complete launch sequence from teaser to urgency close
- A B2B founder planning a co-launch with partners and needing a coordination timeline and pitch materials
- An e-commerce seller with a $500-5,000 budget deciding split between paid ads, influencers, and tools
- An agency delivering a client-facing launch plan with metric benchmarks and a retro framework
What are this skill's strengths and limitations?
- Highly concrete: week-by-week checklists, a day-by-day launch week, and copy-paste email/social templates rather than abstract frameworks
- Covers the full launch lifecycle: positioning, warm-up, audience building, launch week, and post-launch retro with metrics
- Budget-tiered allocation advice from bootstrapped ($0-500, all organic) to enterprise ($25,000+)
- Forces context gathering, so output is tied to a specific product and audience instead of generic advice
- Includes a list of ten common launch mistakes, such as 'launching to nobody' and 'no urgency mechanism'
- Pure prompt template with no scripts or automation — all execution remains manual
- The default 8-week timeline needs manual compression for short cycles like the 2-4 week paid-ads launch type
- Metric targets (open rates, conversion rates) have no benchmark numbers; you must set your own
- Integration with sibling skills (market audit, landing, brand) is a soft 'if available' suggestion — running this skill alone gets none of it
- No test suite or documented real-world launch case validating the templates
How do you install this skill?
Install the full ai-marketing-claude suite: curl -fsSL https://raw.githubusercontent.com/zubair-trabzada/ai-marketing-claude/main/install.sh | bash , or manually git clone the repo and run ./install.sh. Skills are installed into Claude Code's skill directory (the uninstall script targets ~/.claude/skills/market*). The project is MIT licensed; pip install reportlab is optional for PDF reports used by other skills in the suite (this skill does not need it).
How do you use this skill?
In Claude Code, type /market launch or /market launch <product description>. The skill asks for launch context (product, audience, goal, date, channels, price, existing users, budget), then generates LAUNCH-PLAYBOOK.md. You can also paste the SKILL.md instructions into any Agent Skills-compatible client and describe your launch, though the /market slash-command trigger itself is a Claude Code convention.