Skip to content
UXClaim
Content Design

Story-telling

Auto-generate positioning statements from design docs using the four-blank brand-strategy framework.

What it does

Story-telling automatically extracts core narrative elements from approved product design docs and assembles them into a single, compelling positioning statement. It uses Steven Ebert’s four-blank template to compress scattered research, product decisions, and strategic thinking into one sentence that makes strangers care.

How it works

The skill reads a Verdict-approved design doc and identifies four key components: your target audience (specific person or cohort, never a category), the functional problem they face today, your concrete solution (actual features, not buzzwords), and the measurable outcome they gain. It then structures these into:

For [audience], who [problem], [product name] [solution] that allows them to [benefit].

If any required input is missing, the skill halts and reports rather than produce a weak statement.

Use cases

  • Founders pitching investors: A grounded reference point that replaces vague narratives
  • Hiring messaging: Clear, specific language for recruiting decks and job descriptions
  • Marketing foundations: Single source of truth for website copy, pitch decks, and onboarding
  • Cross-team alignment: Forces product, marketing, and leadership to agree on audience and benefit

Who benefits

Early-stage product teams, founders building brands from scratch, and product managers designing go-to-market strategies who need narrative clarity without marketing workshops.

Frequently asked questions

What is a positioning statement and why do I need one?
A positioning statement is one sentence that tells strangers what your product is, who it's for, and why they should care. Until you have revenue, your story is all you have. Without a clear positioning, investors, future hires, and users waste time guessing about your actual audience and benefits.
How do I run the story-telling skill?
After Verdict approves your idea and Scout saves your design doc to `ideas/{project-name}/design-doc.md`, the skill runs automatically and writes `ideas/{project-name}/positioning.md` next to it. Both files commit together.
What information do I need in my design doc?
Your design doc must contain: a specific audience (named person or cohort, not a category), the functional problem they face today (from Verdict's Status Quo answers), what your product actually does (concrete, not buzzwords), and the measurable outcome users gain. Missing any of these, the skill will halt and ask you to revise.
Can I use 'enterprises' or 'developers' as my audience?
No. The skill enforces specific audiences. Instead of 'developers,' name the person: 'backend engineers at Series A startups building real-time APIs.' Specific audiences make positioning stronger and downstream messaging clearer.
What should I avoid in my positioning statement?
Avoid marketing buzzwords ('platform,' 'AI-powered,' 'seamless,' 'next-generation'), product features framed as benefits, and vague categories as audiences. Positioning must describe what the product actually does and what users actually gain.
What's the difference between a solution and a benefit?
The solution is what your product does ('streamlines their review process'). The benefit is what users gain from that ('reach their next funding milestone faster'). Positioning includes both—they work together.
How long should a positioning statement be?
One sentence is ideal. Two is acceptable if necessary. If you need three or more sentences, you're overstuffing the statement. That signals your design doc may be missing clarity.
What happens in future versions of this skill?
v0.2.0 adds Product Messaging (3-5 sentence functional explanation), v0.3.0 adds Vision/Mission, v0.4.0 adds tailored messaging for customers/hires/investors, and v0.5.0 adds Tone of Voice guidelines. Each expansion is driven by real downstream needs.

Glossary

Positioning statement
A single sentence that identifies your target audience, the problem they face, your solution, and the benefit they gain. The core narrative that guides all downstream marketing and product messaging.
Design doc
A comprehensive document where all hard product questions have been answered, including target audience, problem validation, solution approach, and success criteria. Required input for the skill.
Verdict
An evaluation skill that approves product ideas and confirms that design docs contain sufficient evidence and clarity. The skill only runs after Verdict has approved.

More in Content Design

All →
Content Design

Claude Repurpose

Turn any content into 10+ platform-optimized posts for Twitter, LinkedIn, Instagram, TikTok, newsletters, and more in seconds.

AgriciDaniel
Content Design

Ditto Content Marketing

Generate research-backed blog articles, infographics, and social content from synthetic persona studies at scale—20-40 articles monthly.

Ask-Ditto
Content Design

LinkedIn Content Creator

AI-powered tool to generate, schedule, and post professional LinkedIn content with smart research and batch creation capabilities.

AgriciDaniel
Content Design

Slop Cop

Detect AI-generated writing patterns in your documents to ensure authentic, human-quality prose before publishing.