product-narrative
npx machina-cli add skill Dragoon0x/Product-Skills/product-narrative --openclawProduct Narrative
Tell the product story in a way that sticks.
How to use
/product-narrativeApply narrative constraints to this conversation./product-narrative <context>Generate a narrative framework for the described product.
Constraints
Story Structure
- The world before (the problem everyone accepts as normal)
- The breaking point (what made someone say "enough")
- The insight (the non-obvious realization that led to this product)
- The solution (what was built and why it works)
- The evidence (proof that it delivers on the promise)
- The future (what becomes possible for the user)
Rules
- MUST lead with a problem the audience recognizes in their own life
- MUST make the reader the hero, not the company
- SHOULD include one specific, concrete detail that makes the story feel real
- NEVER start with "We founded this company because..."
- NEVER use the narrative to list features. Features support the story, they're not the story.
Tone
- Confidence without arrogance
- Specificity without jargon
- Ambition without hyperbole
- SHOULD read like a conversation, not a press release
- MUST sound like it was written by a person who cares, not a committee
Anti-Patterns
- Starting with the team or the technology instead of the problem
- Making the company the protagonist instead of the user
- Generic origin stories ("We were frustrated by...")
- Narratives that work on the about page but nowhere else
- Stories without stakes or tension
Source
git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/communication/product-narrative/SKILL.mdView on GitHub Overview
Product narrative helps you craft compelling stories for About pages, launch announcements, and pitch decks by structuring the product's origin, problem, and transformation. It centers the reader as the hero and uses concrete details to make the narrative feel real. This skill translates complex features into a relatable journey that resonates with stakeholders and customers.
How This Skill Works
Use the six-story framework (world before, breaking point, insight, solution, evidence, future) to anchor your narrative. Start with a problem your audience recognizes, then guide the reader through the turning point and the product's impact, avoiding a company-centric origin. Apply the built-in commands: /product-narrative to apply narrative constraints, or /product-narrative <context> to generate a tailored narrative framework.
When to Use It
- Creating an About page that centers the user's journey
- Sending a launch announcement that reframes the product as the solution
- Building a pitch deck that makes the user the hero
- Updating investors with a transformation narrative and evidence
- Writing a customer case study or product narrative blog
Quick Start
- Step 1: Define the everyday problem your audience recognizes and the stakes involved.
- Step 2: Map the six-story arc (world before, breaking point, insight, solution, evidence, future) and weave the user as hero.
- Step 3: Write in a human, specific voice and test with a real user or teammate for realism.
Best Practices
- Lead with a problem your audience recognizes and the impact on their life
- Make the reader the hero; keep the company in a supporting role
- Include one concrete, verifiable detail that grounds the story
- Follow the six-story steps: world before, breaking point, insight, solution, evidence, future
- Write in a conversational, specific tone without product jargon
Example Use Cases
- About page: World before (fragmented tools), Breaking point (missed insights from scattered data), Insight (single source of truth helps decisions), Solution (unified analytics platform), Evidence (clients cut decision time by 40%), Future (teams collaborate in real time).
- Launch email: Problem the audience feels today, turning point, the product as the solution, measurable impact, and a glimpse of what is possible for users.
- Pitch deck slide: User is the hero—describe the problem they face, how the product changes their day, and the tangible outcomes with a data-backed metric.
- Investor update: Short narrative arc showing how problem -> solution -> traction translates into user value and growth trajectory.
- Case study teaser: A real user story that starts with pain, introduces a concrete transformation, and ends with measurable results.