brand-storytelling▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Craft compelling brand narratives using frameworks from 30 product leaders and storytelling experts.
- ›Guides users through understanding audience context, identifying core transformations, structuring narratives, and creating memorable moments that stick
- ›Emphasizes positioning the customer as the hero and your brand as the mentor providing tools, not centering the founder's story
- ›Covers nine core principles including leading a movement rather than solving problems, finding the singula
Brand Storytelling
Help the user craft compelling narratives that make their brand memorable using techniques from 30 product leaders and storytelling experts.
How to Help
When the user asks for help with brand storytelling:
- Understand the context - Ask who the audience is (investors, customers, employees) and what action they want to inspire
- Find the core story - Help identify the transformation, movement, or unique insight at the heart of the brand
- Structure the narrative - Apply proven frameworks to organize the story effectively
- Make it memorable - Help craft specific phrases, metaphors, and moments that stick
Core Principles
Lead a movement, don't just solve a problem
Andy Raskin: "This structure is about defining a movement—that's very different from 'I'm going to solve your problem.'" Frame your brand as the leader of a shift toward a new way of winning.
Story before product
Brian Chesky: "One of the first things we do is figure out what the story is. The story often dictates the product. A story is a helpful way to develop a cohesive product." Define the narrative before finalizing features.
Find the five-second moment
Matthew Dicks: "Every story is about a singular moment—I call it five seconds. A moment of transformation or realization. 98% of the story provides context to make that moment clear." Identify the single moment of change.
Start in the middle of the action
Merci Grace: "Every pitch should start in the middle of the action, like Mission Impossible. Tom Cruise is always doing crazy shit before the actual mission. It gets attention." Skip the boring setup—hook them immediately.
Problems beat successes
Jason Feifer: "Success stories aren't interesting. Problem-solving stories are. Frame your story around a specific challenge you faced and the counterintuitive way you solved it."
You're Obi-Wan, not Luke
Mike Maples Jr: "The customer is the hero (Luke Skywalker), the founder is the mentor (Obi-Wan) providing the tools. Position your product as the lightsaber—the tool the hero needs."
Make it repeatable
Lulu Cheng Meservey: "Make it memorable. Make people want to say it of their own volition. Use analogies, colorful mental images, jokes. Replace adjectives with anecdotes people can repeat at dinner."
Paint emotional pictures
Camille Ricketts: "Effective storytelling paints an emotional picture of the vision. Convey the emotional quality of the mission, not just technical details, to enlist hearts and minds."
Hook, message, celebration
Christina Wodtke: "A beginning, middle, and end. Intrigue with a hook—a mystery, secret, or surprise. The middle delivers the message. Always end with success and celebration."
Memify your insights
Yuhki Yamashata: "The goal is 'memification'—synthesize insights so they're catchy enough for execs to cite in meetings. Use metaphors to explain complex concepts."
Questions to Help Users
- "Who is your audience and what do you want them to do after hearing this?"
- "What's the transformation or realization at the heart of your story?"
- "What problem did you face that others can relate to?"
- "Can someone repeat your core message at a dinner party?"
- "Are you the hero of this story, or is your customer?"
Common Mistakes to Flag
- Starting with your company - Start with the audience's problem or the world's change, not "We are..."
- Feature lists instead of stories - Stories are about change; lists are forgettable
- Hero syndrome - Position yourself as the mentor, not the hero
- Vague vision - "Making the world better" isn't a story; be specific
- No stakes - If nothing's at risk, there's no tension
Deep Dive
For all 50 insights from 30 guests, see references/guest-insights.md
Related Skills
- Positioning & Messaging
- Giving Presentations
- Fundraising
- Media Relations
How to use brand-storytelling on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add brand-storytelling
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches brand-storytelling from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate brand-storytelling. Access the skill through slash commands (e.g., /brand-storytelling) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★64 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
We added brand-storytelling from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Harper Abebe· Dec 16, 2024
brand-storytelling has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Harper Lopez· Dec 8, 2024
brand-storytelling fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Chinedu Sethi· Dec 4, 2024
brand-storytelling fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Tariq Farah· Dec 4, 2024
Solid pick for teams standardizing on skills: brand-storytelling is focused, and the summary matches what you get after install.
- ★★★★★Aarav Iyer· Nov 27, 2024
We added brand-storytelling from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chinedu Malhotra· Nov 23, 2024
We added brand-storytelling from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Harper Ndlovu· Nov 23, 2024
brand-storytelling is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yash Thakker· Nov 19, 2024
brand-storytelling fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Zara Gill· Nov 15, 2024
Registry listing for brand-storytelling matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 64