Product narrative
Skill Dragoon0x/product-skills/skills/communication/product-narrative
Tell the product story in a way that sticks. Structures origin stories, problem narratives, and transformation arcs. Use when building about pages, launch announcements, or pitch decks.From its SKILL.md
npx -y skills add Dragoon0x/product-skills --skill product-narrativeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 326 tokens by cl100k_base, as published. Nobody here has run it
Product 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.