Problem Solution Script Builder
Turn a product, pain point, and promise into a clear creator-native script that moves from problem recognition to believable solution and action.
Use this skill when a user wants a short-form ecommerce script built around a classic problem-to-solution structure without sounding stiff or overhyped. It works well for TikTok Shop videos, UGC briefs, affiliate content, PDP video scripts, and direct-response creator content.
Problem it solves
Many ecommerce scripts either jump straight into selling or stay too abstract. They name a benefit but never dramatize the real problem, explain the mechanism, or bridge to a credible CTA. This skill creates a tighter persuasion flow that makes the product feel relevant and timely.
Use when
- You need a script built from a pain point and product angle
- A product solves an obvious everyday frustration
- You want a clear direct-response structure for creator content
- A team needs multiple script variants from the same problem
- You are building content for testing different buyer pains
Do not use when
- The script should be purely story-led rather than problem-led
- The user only needs hooks or CTAs, not a full script flow
- There is no clear user pain or product mechanism to work from
Inputs to ask for
- Product and category
- Target audience
- Primary pain point or frustration
- Desired outcome or transformation
- Product mechanism / why it works
- Proof available: demo, testimonial, creator experience, results, social proof
- Platform and target length
- CTA goal: click, comment, shop now, DM, follow, live join
Workflow
- Clarify the audience, pain, and offer
- Pick the most concrete version of the problem
- Agitate the problem in creator-native language without overselling
- Introduce the product as the mechanism or relief path
- Add proof, specificity, or usage context
- End with a CTA matched to the content and funnel stage
- Optionally produce 2-3 variants for different tones or awareness levels
Output requirements
Return:
- Script in a clear beat-by-beat format
- Hook
- Problem setup
- Agitation / consequence
- Solution introduction
- Proof / demonstration cue
- CTA
- Optional shorter and punchier alternate version
Quality standards
- The problem should feel real, not generic
- The solution should be believable and specific
- The script must feel like creator content, not corporate copy
- Avoid unsupported guarantees or exaggerated claims
- CTA should fit the actual stage of intent
Example prompts
- Build a TikTok Shop script around the problem this product solves
- Turn this pain point and offer into a short problem-solution creator script
- Write 3 variants of a UGC script using problem -> solution -> CTA structure