Help users plan, coordinate, and execute product launches that cut through market noise. This guide covers everything from internal alignment and GACCS briefs to community engagement and viral mechanics.
npx skills add https://github.com/RefoundAI/lenny-skills --skill launch-planning
Build momentum and drive adoption by turning product updates into remarkable market events.
Help the user with product launch planning using insights from 18 guests and posts across Lenny's Podcast and Newsletter.
From "Generating buzz": "Here’s the hard truth: No one cares about your new product. As Marc Andreessen said, “everyone’s time is already allocated.”"
To break through the attention barrier, a launch must be worth making a remark about. Focus on creating something that people feel they must share with others.
From "How to get your marketing team to drive more impact": "The GACCS framework (Goals, Audience, Creative, Channels, Stakeholders) keeps teams from doing busywork, drives cross-team alignment, and helps marketers produce more work that your prospects and customers—and coworkers—love. In short, it helps stop marketing work from being a waste of time."
Use structured GACCS briefs for any project longer than a tweet. Forcing alignment on goals and audiences before execution prevents wasted effort and scope creep.
Claire Butler: "This was a forcing function for us to do our messaging and positioning. And I remember there was more than one day where we locked ourselves in a conference room and I made Dylan and show at the time have this positioning up on the big screen and made them agree on it word for word."
Set hard launch dates to compel final decisions on brand and messaging. This forces stakeholders to resolve internal strategic debates and commit to a core direction.
See references/artifacts.md for the full list with details.
For all 33 sourced insights from 18 guests, see references/guest-insights.md
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take refoundai/launch-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.